PDCA Skill

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

Arguments

Action Details

plan (Plan Phase)

1. Check if docs/01-plan/features/{feature}.plan.md exists
2. If not, create based on plan.template.md
3. If exists, display content and suggest modifications
4. Create Task: [Plan] {feature}
5. Update .bkit-memory.json: phase = "plan"

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

design (Design Phase)

1. Verify Plan document exists (required - suggest running plan first if missing)
2. Create docs/02-design/features/{feature}.design.md
3. Use design.template.md structure + reference Plan content
4. Create Task: [Design] {feature} (blockedBy: Plan task)
5. Update .bkit-memory.json: phase = "design"

Output Path: docs/02-design/features/{feature}.design.md

do (Do Phase)

1. Verify Design document exists (required)
2. Provide implementation guide based on do.template.md
3. Reference implementation order from Design document
4. Create Task: [Do] {feature} (blockedBy: Design task)
5. Update .bkit-memory.json: phase = "do"

Guide Provided:

• Implementation order checklist
• Key files/components list
• Dependency installation commands

analyze (Check Phase)

1. Verify Do completion status (implementation code exists)
2. Call gap-detector Agent
3. Compare Design document vs implementation code
4. Calculate Match Rate and generate Gap list
5. Create Task: [Check] {feature} (blockedBy: Do task)
6. Update .bkit-memory.json: phase = "check", matchRate

Output Path: docs/03-analysis/{feature}.analysis.md

iterate (Act Phase)

1. Check results (when matchRate < 90%)
2. Call pdca-iterator Agent
3. Auto-fix code based on Gap list
4. Auto re-run Check after fixes
5. Create Task: [Act-N] {feature} (N = iteration count)
6. Stop when >= 90% reached or max iterations (5) hit

Iteration Rules:

• Max iterations: 5 (adjustable via bkit.config.json)
• Stop conditions: matchRate >= 90% or maxIterations reached

report (Completion Report)

1. Verify Check >= 90% (warn if below)
2. Call report-generator Agent
3. Integrated report of Plan, Design, Implementation, Analysis
4. Create Task: [Report] {feature}
5. Update .bkit-memory.json: phase = "completed"

Output Path: docs/04-report/{feature}.report.md

archive (Archive Phase)

1. Verify Report completion status (phase = "completed" or matchRate >= 90%)
2. Verify PDCA documents exist (plan, design, analysis, report)
3. Create docs/archive/YYYY-MM/{feature}/ folder
4. Move documents (delete from original location)
5. Update Archive Index (docs/archive/YYYY-MM/_INDEX.md)
6. Update .pdca-status.json: phase = "archived", record archivedTo path
7. Remove feature from status (or preserve summary with --summary option)

Arguments:

Output Path: docs/archive/YYYY-MM/{feature}/

Documents to Archive:

• docs/01-plan/features/{feature}.plan.md
• docs/02-design/features/{feature}.design.md
• docs/03-analysis/{feature}.analysis.md
• docs/04-report/features/{feature}.report.md

FR-04: Summary Preservation Option (v1.4.8):

When using --summary (or --preserve-summary, -s), the feature data in .pdca-status.json is converted to a lightweight summary instead of being deleted:

// Summary format (70% size reduction)
{
  "my-feature": {
    "phase": "archived",
    "matchRate": 100,
    "iterationCount": 2,
    "startedAt": "2026-01-15T10:00:00Z",
    "archivedAt": "2026-01-20T15:30:00Z",
    "archivedTo": "docs/archive/2026-01/my-feature/"
  }
}

Use --summary when you need:

• Historical statistics and metrics
• Project duration tracking
• PDCA efficiency analysis

Important Notes:

• Cannot archive before Report completion
• Documents are deleted from original location after move (irreversible)
• Feature name must match exactly
• Default behavior: complete deletion from status
• Use --summary to preserve metrics for future reference

cleanup (Cleanup Phase) - v1.4.8

Clean up archived features from .pdca-status.json to reduce file size.

1. Read archived features from .pdca-status.json
2. Display list with timestamps and archive paths
3. Ask user for confirmation via AskUserQuestion (FR-06)
4. Delete selected features from status using cleanupArchivedFeatures()
5. Report cleanup results

Arguments:

Output Example:

🧹 PDCA Cleanup
─────────────────────────────
Archived features found: 3

1. feature-a (archived: 2026-01-15)
2. feature-b (archived: 2026-01-20)
3. feature-c (archived: 2026-01-25)

Select features to cleanup:
[ ] All archived features
[ ] Select specific features
[ ] Cancel

Related Functions (lib/pdca/status.js):

• getArchivedFeatures() - Get list of archived features
• cleanupArchivedFeatures(features?) - Cleanup specific or all archived
• deleteFeatureFromStatus(feature) - Delete single feature
• enforceFeatureLimit(max=50) - Auto cleanup when limit exceeded

Notes:

• Only archived/completed features can be deleted
• Active features are protected from deletion
• Archive documents remain in docs/archive/ (only status is cleaned)

status (Status Check)

1. Read .bkit-memory.json
2. Display current feature, PDCA phase, Task status
3. Visualize progress

Output Example:

📊 PDCA Status
─────────────────────────────
Feature: user-authentication
Phase: Check (Gap Analysis)
Match Rate: 85%
Iteration: 2/5
─────────────────────────────
[Plan] ✅ → [Design] ✅ → [Do] ✅ → [Check] 🔄 → [Act] ⏳

next (Next Phase)

1. Check current PDCA phase
2. Suggest next phase guide and commands
3. Confirm with user via AskUserQuestion

Phase Guide:

Template References

Templates loaded from imports are used when executing each action:

Task Integration

Each PDCA phase automatically integrates with Task System:

Task Creation Pattern:
┌────────────────────────────────────────┐
│ [Plan] {feature}                       │
│   ↓ (blockedBy)                        │
│ [Design] {feature}                     │
│   ↓ (blockedBy)                        │
│ [Do] {feature}                         │
│   ↓ (blockedBy)                        │
│ [Check] {feature}                      │
│   ↓ (blockedBy, Check < 90%)           │
│ [Act-1] {feature}                      │
│   ↓ (on iteration)                     │
│ [Act-N] {feature}                      │
│   ↓ (Check >= 90%)                     │
│ [Report] {feature}                     │
│   ↓ (after Report completion)          │
│ [Archive] {feature}                    │
└────────────────────────────────────────┘

Agent Integration

Usage Examples

# Start new feature
/pdca plan user-authentication

# Create design document
/pdca design user-authentication

# Implementation guide
/pdca do user-authentication

# Gap analysis after implementation
/pdca analyze user-authentication

# Auto improvement (if needed)
/pdca iterate user-authentication

# Completion report
/pdca report user-authentication

# Check current status
/pdca status

# Guide to next phase
/pdca next

Legacy Commands Mapping

Auto Triggers

Auto-suggest related action when detecting these keywords: