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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute approved PWDEV Flow plans one atomic task at a time with test-first implementation, fresh verification, blocker handling, and durable evidence. Use after the plan gate is approved or for approved Flow correction tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose repository and PWDEV Flow health without changing the project. Use when the user asks for a health check, workspace consistency check, dependency assessment, readiness report, or evidence-based scorecard.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tickets, triagem, followups, solução, usuários, grupos, ativos, projetos e base de conhecimento no GLPI via MCP glpi.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a product requirement, PRD, or executable roadmap is requested, or when an approved requirement needs decomposing into phases, epics, features and tasks
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when work needs reviewing before it is merged, and when review feedback has arrived and needs acting on
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adversarially verify an implementation against its objective, acceptance criteria, definition of done, and prohibitions using fresh evidence. Use for completion gates, release readiness, or independent verification after implementation and review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 a repository has no PWDEV Power workspace yet, when resuming one, when the codebase map needs refreshing, or when the setup should be checked
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enable, record, query, summarize, or verify the opt-in PWDEV Flow semantic audit trail. Use when the user asks what Flow actions occurred, wants audit integrity checked, or needs a portable JSONL record of workflow gates and artifacts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when encountering any bug, test failure, or unexpected behavior, before proposing any fix
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to execute an existing pwdev-feat action plan — 'executar o plano user-crud', 'exec latest', 'rodar o plano', 'retomar a execução'. Dispatches the executor (subagent when the runtime has one, inline otherwise) in IMPLEMENT or REPORT mode, handles NEEDS_ADVICE with the advisor, and supports --resume. Do NOT use to create plans (feat-feature, feat-backend, feat-frontend, feat-test, feat-review) or for tasks without a plan (feat-quick).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants a full feature action plan (backend + frontend + tests) with the PWDEVIA 7-question method before any code is written — 'planejar a feature X', 'criar plano de feature', 'plan the user CRUD'. Interviews the human (max 2 rounds) and writes .planning/feat/features/{slug}/plan.md. Do NOT use to write code (feat-exec), for small 1–3 file changes (feat-quick), backend-only or UI-only scope (feat-backend / feat-frontend), tests for existing code (feat-test) or code review (feat-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to set up pwdev-feat in a project — 'inicializar o pwdev-feat', 'configurar o feat', 'init feat workspace' — choosing language, model profile and the optional audit trail, and creating the .planning/feat/ workspace. Do NOT use to analyze the codebase (feat-map), to write the project instructions file (feat-setup) or to create plans.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user hands over a GitHub issue to be delivered end to end — 'resolver a issue #42', 'loop na issue 42', 'deliver issue https://github.com/o/r/issues/42' — or when an Orca worker preamble dispatches `feat-loop #N`. Turns the issue into a plan, executes it, reviews the result and runs at most 2 fix cycles until APPROVED, then opens a pull request that closes the issue. Never merges. Do NOT use without an issue (feat-feature / feat-quick), to only plan (feat-feature), to only review (feat-review) or to execute an existing plan (feat-exec).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants a small, well-bounded change done now without a plan file — a bugfix, config change, rename, doc update or simple refactor touching 1–5 files — 'corrigir rapidinho', 'quick fix no X', 'renomear Y'. Presents a mini-plan, implements after approval, verifies and commits. Do NOT use for more than 5 files, architectural decisions, migrations or new UI flows (use feat-feature / feat-backend / feat-frontend).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants a code review of an explicit range or set of files — correctness, security, performance, conventions, tests — with stable findings (CR-nnn, BLOCKER..INFO) and rule citations — 'revisar os últimos commits', 'code review da feature X', 'review base..HEAD'. Plans a REPORT-mode review (no code changes, no commit). Do NOT use to fix code (feat-feature / feat-quick), to write tests (feat-test) or for UI/UX design critique.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route supported legacy PWDEV Code command intent to canonical PWDEV Flow skills. Use when the user mentions old /pwdev-code:* commands, asks for PWDEV Code compatibility, or wants to adopt an existing .planning workspace without losing history.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Delegate a bounded repository task to an allowlisted external coding CLI through the guarded Flow runner. Use for automatic provider selection or explicit Codex, OpenCode, Kimi, Gemini, or Kiro delegation that requires timeout handling and independent local review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discover and approve feature requirements through focused interviewing and repository research. Use when the user has a feature idea, unclear scope, conflicting requirements, or needs Flow context artifacts before design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Curate durable PWDEV Flow project decisions, lessons, and conventions. Use when the user asks to capture, list, show, link, supersede, or select project memory, or when an approved workflow decision should persist across phases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.