/pdca

name: pdca
classification: workflow
classification-reason: PDCA process automation independent of model capability evolution
deprecation-risk: none
effort: medium
description: |
  Unified PDCA cycle management — plan, design, do, analyze, iterate, report. PDCA runs per-feature (9-phase: pm→plan→design→do→check→act→qa→report→archive); for multi-feature scope/budget grouping use /sprint (v2.1.13, 8-phase container that may host PDCA cycles inside).
  Triggers: pdca, plan, design, analyze, report, status, next, iterate
argument-hint: "[action] [feature]"
user-invocable: true
agents:
  analyze: bkit:gap-detector
  iterate: bkit:pdca-iterator
  report: bkit:report-generator
  qa: bkit:qa-lead
  team: null
  pm: null
  default: null
allowed-tools:
  - Read
  - Write
  - Edit
  - Glob
  - Grep
  - Bash
  - Task
  - TaskCreate
  - TaskUpdate
  - TaskList
  - AskUserQuestion
imports:
  - ${PLUGIN_ROOT}/templates/plan.template.md
  - ${PLUGIN_ROOT}/templates/design.template.md
  - ${PLUGIN_ROOT}/templates/do.template.md
  - ${PLUGIN_ROOT}/templates/analysis.template.md
  - ${PLUGIN_ROOT}/templates/qa-report.template.md
  - ${PLUGIN_ROOT}/templates/qa-test-plan.template.md
  - ${PLUGIN_ROOT}/templates/report.template.md
  - ${PLUGIN_ROOT}/templates/iteration-report.template.md
next-skill: null
pdca-phase: null
task-template: "[PDCA] {feature}"

PDCA Skill

> Unified Skill for managing PDCA cycle. Supports the entire Plan → Design → Do → Check → Act flow.

Arguments

| Argument | Description | Example | |----------|-------------|---------| | `pm [feature]` | Run PM Agent Team analysis (pre-Plan) | `/pdca pm user-auth` | | `plan [feature]` | Create Plan document | `/pdca plan user-auth` | | `design [feature]` | Create Design document | `/pdca design user-auth` | | `do [feature]` | Do phase guide (start implementation) | `/pdca do user-auth` | | `analyze [feature]` | Run Gap analysis (Check phase) | `/pdca analyze user-auth` | | `iterate [feature]` | Auto improvement iteration (Act phase) | `/pdca iterate user-auth` | | `qa [feature]` | Run QA phase (L1-L5 tests) | `/pdca qa user-auth` | | `report [feature]` | Generate completion report | `/pdca report user-auth` | | `archive [feature]` | Archive completed PDCA documents | `/pdca archive user-auth` | | `cleanup [feature]` | Cleanup archived features from status | `/pdca cleanup` | | `team [feature]` | Start PDCA Team Mode (requires Agent Teams) | `/pdca team user-auth` | | `team status` | Show Team status | `/pdca team status` | | `team cleanup` | Cleanup Team resources | `/pdca team cleanup` | | `status` | Show current PDCA status | `/pdca status` | | `next` | Guide to next phase | `/pdca next` |

Action Details

pm (PM Analysis Phase)

Run PM Agent Team for product discovery and strategy analysis before Plan phase.

1. **Call pm-lead Agent** (orchestrates 4 sub-agents) 2. pm-lead runs Phase 1: Context Collection (project info, git history) 3. pm-lead runs Phase 2: Parallel Analysis (3 agents simultaneously)

• pm-discovery: Opportunity Solution Tree (Teresa Torres)
• pm-strategy: Value Proposition (JTBD 6-Part) + Lean Canvas
• pm-research: 3 Personas + 5 Competitors + TAM/SAM/SOM

4. pm-lead runs Phase 3: PRD Synthesis via pm-prd agent

• Beachhead Segment (Geoffrey Moore) + GTM Strategy
• 8-section PRD generation

5. Output PRD to `docs/00-pm/{feature}.prd.md` 6. Create Task: `[PM] {feature}` 7. Update `.bkit/state/pdca-status.json`: phase = "pm" 8. Guide user to next step: `/pdca plan {feature}`

**Output Path**: `docs/00-pm/{feature}.prd.md`

**Requirements**:

• Agent Teams enabled: `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`
• Project level: Dynamic or Enterprise (Starter not supported)

plan (Plan Phase)

0. **Template Loading**: Read `templates/plan.template.md` to understand the required Plan document structure and sections. Use this template's sections as your document outline. This is MANDATORY — do not generate Plan documents from memory or assumptions. 1. **PRD Auto-Reference**: Check if `docs/00-pm/{feature}.prd.md` exists

• If found: Read PRD and use as context for Plan document (improves quality significantly)
• If not found: Proceed normally (tip: run `/pdca pm {feature}` first for better results)

2. Check if `docs/01-plan/features/{feature}.plan.md` exists 3. If not, create based on `plan.template.md` 4. If exists, display content and suggest modifications 5. **Checkpoint 1 — Requirements Confirmation**: Present understanding of the feature (problem, scope, constraints) and use AskUserQuestion: "요구사항 이해가 맞나요? 빠진 건 없나요?" Wait for user confirmation before proceeding. 6. **Checkpoint 2 — Clarifying Questions**: Identify underspecified elements (edge cases, error handling, integration points, compatibility). Present organized question list. Wait for answers before generating the document. 7. Generate Plan document with user-confirmed requirements 8. **Complete predecessor Task first**: If a `[PM] {feature}` Task exists and is still `in_progress`, use TaskList to find it and TaskUpdate it to `status: "completed"` before creating the Plan Task (see [Phase Transition Rule](#task-integration)). Then Create Task: `[Plan] {feature}` 9. Update `.bkit/state/pdca-status.json`: phase = "plan" 10. Write `## Executive Summary` at document top with 4-perspective table (Problem/Solution/Function UX Effect/Core Value), each 1-2 sentences 11. **Context Anchor Generation**: After generating Plan document, extract Context Anchor (WHY/WHO/RISK/SUCCESS/SCOPE) from Executive Summary, Requirements, and Risk sections. Write as `## Context Anchor` table between Executive Summary and Section 1. This anchor propagates to Design/Do documents for cross-session context continuity. 12. **MANDATORY**: After completing the document, also output the Executive Summary table in your response so the user sees it immediately without opening the file

**Output Path**: `docs/01-plan/features/{feature}.plan.md`

> **Tip**: For features wit