Plan explicitly authorized read-only production observations and trace evidence-backed causes into preventive regression coverage without external effects.
日本語の概要は準備中です。原文の説明を表示しています。
1,235 件 ・ 関連度順
概要と使いどころ
Plan explicitly authorized read-only production observations and trace evidence-backed causes into preventive regression coverage without external effects.
日本語の概要は準備中です。原文の説明を表示しています。
Design bounded performance profiles with explicit load authorization, contextual samples, percentiles, and agreed thresholds.
日本語の概要は準備中です。原文の説明を表示しています。
Triage defects with independent severity and priority, reproducible evidence, preserved attempt history, and explicit resolution retesting.
日本語の概要は準備中です。原文の説明を表示しています。
Design traceable data checks for reconciliation, integrity, transactions, and atomicity with separate observable oracles.
日本語の概要は準備中です。原文の説明を表示しています。
Design deterministic CI quality gates that read the normalized manifest verdict independently from report-export process status.
日本語の概要は準備中です。原文の説明を表示しています。
Design isolated repeatable automation, distinguish interactive browser exploration, and handle flaky results through evidence and reproduction.
日本語の概要は準備中です。原文の説明を表示しています。
Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Design platform-specific Android and iOS checks with explicit SDK, driver, device, lifecycle, and evidence prerequisites.
日本語の概要は準備中です。原文の説明を表示しています。
Export one validated QA manifest as matching HTML and PDF without executing tests or evidence commands.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an approved PRD must become an executable roadmap — 'gerar roadmap do PRD', 'quebrar o PRD em épicos e features', 'cadeia de dependências', 'roadmap with dependencies' — Phase/Epic/Feature/Task with explicit dependencies, waves and critical path, validated by a deterministic checker, with an approval gate. Do NOT use for a PRD that is not approved (prd- create/prd-refine first).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to change an existing PRD — 'refinar o PRD', 'adicionar requisito', 'atualizar escopo do PRD', 'update the PRD' — through targeted questions, bumping the version and re-opening approval. Do NOT use to create a PRD (prd-create).
日本語の概要は準備中です。原文の説明を表示しています。
Use when an approved PRD roadmap must go to GitHub — 'publicar o roadmap no GitHub', 'criar o project e as issues do PRD', 'publish PRD roadmap' — handing over to pwdev-github (Project from a template, issues, sub-issues, blocked-by). Do NOT use for a single issue with the whole PRD (prd-export).
日本語の概要は準備中です。原文の説明を表示しています。
Use when about to claim work is complete, fixed, or passing, and when a finished feature needs adversarial verification before integration
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting feature work that needs isolation from the current workspace, or before executing an implementation plan
日本語の概要は準備中です。原文の説明を表示しています。
Design traceable functional test conditions across positive, negative, boundary, and error behavior with observable expectations.
日本語の概要は準備中です。原文の説明を表示しています。
Produce a traceable risk-based QA strategy without executing tests or expanding authorization.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to set up pwdev-prd in a project — 'inicializar o pwdev-prd', 'init prd', 'configurar PRDs' — creating the .planning/prds/ workspace and choosing language and the optional SQLite audit trail. Do NOT use to write a PRD (prd-create).
日本語の概要は準備中です。原文の説明を表示しています。
Initialize or inspect project-local PWDEV QA context without overwriting existing state or installing tools.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to evolve the features of a PRD roadmap with user stories — 'refinar as histórias da feature', 'escrever histórias de usuário', 'critérios de aceite', 'regras de negócio da feature', 'deixar a feature pronta', 'user stories for FT01' — one feature at a time, interviewing the human until each story meets the Definition of Ready: persona, value, INVEST, CA (Gherkin, happy and error paths) and RN from the PRD. Do NOT use to create the roadmap (prd-roadmap) or to change requirements without stories (prd-refine).
日本語の概要は準備中です。原文の説明を表示しています。
Monta carrossel completo — estrutura de slides, hierarquia por slide e construção no Figma como componente com variantes. Use quando o usuário disser "carrossel", "slides", "carrossel do LinkedIn", "carrossel do Instagram", "post em sequência", "documento do LinkedIn". Recebe a copy slide a slide e entrega frames montados e revisados.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a PRD exported — 'exportar o PRD', 'gerar o prd.json', 'criar issue com o PRD', 'export PRD to GitHub' — as canonical JSON or as a single GitHub issue. Do NOT use to publish a roadmap with many issues (prd-publish).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a new Product Requirements Document — 'criar um PRD', 'escrever os requisitos de', 'new PRD for', 'documento de requisitos' — through a 12-step interview, one question at a time, ending with an approval gate. Do NOT use to change an existing PRD (prd- refine) or to plan implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Extrai o brand kit do Figma — tokens de cor, tipografia, grid, logo e componentes — e grava na seção 3 do contexto. Use quando o usuário disser "extrair a marca", "pegar os tokens", "quais as cores", "design system", "importar do Figma", "montar brand kit", ou quando a seção 3 estiver vazia. Lê do Figma; não inventa paleta.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting any conversation in a repository that uses PWDEV Power - establishes how to find and apply Power skills before any response, including clarifying questions
日本語の概要は準備中です。原文の説明を表示しています。