1,235 件 ・ 関連度順
概要と使いどころ
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).
日本語の概要は準備中です。原文の説明を表示しています。
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 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).
日本語の概要は準備中です。原文の説明を表示しています。
Initialize or inspect project-local PWDEV QA context without overwriting existing state or installing tools.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
Design platform-specific Android and iOS checks with explicit SDK, driver, device, lifecycle, and evidence prerequisites.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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
日本語の概要は準備中です。原文の説明を表示しています。
Execute an explicitly authorized exploratory charter and record notes, findings, evidence, and follow-up without claiming false coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks about the pwdev-prd audit trail — 'auditoria do prd', 'eventos', 'decisões registradas', 'audit report', 'exportar relatório de auditoria' — querying the shared SQLite database read-only (summary, events, decisions, artifacts, stats, export, query).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks which PRDs exist — 'listar PRDs', 'quais PRDs temos', 'list PRDs' — with status, version, roadmap state and GitHub Project. Read-only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when approved phases should run in parallel — visually in a cmux panel or unattended — when fleet status is requested, or when a fleet member must be stopped or merged
日本語の概要は準備中です。原文の説明を表示しています。
Use quando o usuário quiser configurar o pwdev-github — 'configurar github', 'setup do github project', 'init github' — verificando gh, autenticação e o scope project e gravando repo e Project padrão em .planning/github.json. Não use para criar um Project (github-project).
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementation is complete, tests pass, and the work needs integrating - merging, opening a pull request, or being left in place
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a completed phase diff for high-confidence behavior-preserving simplifications and apply only explicitly approved proposals. Use after execution and before review to reduce duplication, dead code, needless complexity, or avoidable inefficiency.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an approved plan needs executing task by task in this session, with a fresh implementer per task and review between tasks
日本語の概要は準備中です。原文の説明を表示しています。
Decompose an approved PWDEV Flow specification into dependency-aware waves and atomic executable tasks. Use when design is approved and the user needs exact file scope, test-first actions, verification commands, and an execution gate.
日本語の概要は準備中です。原文の説明を表示しています。
Inventory, archive, and summarize PWDEV Flow project history safely. Use when the user asks to find stale artifacts, archive completed work, clean the Flow workspace without deletion, or generate a changelog from verified history.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize, inspect, resume, or migrate portable PWDEV Flow project state. Use when the user asks to set up PWDEV Flow, adopt an existing repository or legacy PWDEV Code workspace, resume its workflow, or diagnose its current state.
日本語の概要は準備中です。原文の説明を表示しています。
Launch, inspect, and tear down autonomous phase fleets in isolated Git worktrees, on the Codex or the Claude runtime. Use when approved Flow phase slugs should run in parallel, when fleet status is requested, or when a fleet member must be stopped or explicitly merged.
日本語の概要は準備中です。原文の説明を表示しています。
Use before any creative work - creating a feature, building a component, adding functionality, or changing behavior - to explore intent and design before implementation
日本語の概要は準備中です。原文の説明を表示しています。
Design an approval-gated feature specification from approved requirements. Use when PWDEV Flow discovery is complete and the user needs architecture decisions, component boundaries, quality constraints, and a definition of done.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a design or set of requirements exists and work needs decomposing into tasks, before touching any code
日本語の概要は準備中です。原文の説明を表示しています。