Pm

Project Plan Structure

docs/03-project-plan/
├── sprint-backlog.md              # Active sprint (current iteration)
├── product-backlog.md             # All pending work with estimates
├── epics.md                       # Epic breakdown with dependencies
├── lessons-learned.md             # Project learnings and insights
├── technical-debt-register.md     # Debt tracking
├── iterations/                    # PDCA iteration folders
│   └── YYYY-MM-DD-name/
│       ├── 01-plan.md
│       ├── 02-do.md
│       ├── 03-check.md
│       └── 04-act.md
└── sprints/                       # Historical sprint archive

Commands

/pm status - Show Current Status

Display the current iteration status including:

• Active sprint/iteration name and dates
• Stories in scope with status
• Success criteria progress
• Current blockers or issues

Action: Read docs/03-project-plan/sprint-backlog.md and summarize the active iteration.

/pm next - Find Next Task

Identify the next task to work on based on:

1. Current iteration stories (from sprint-backlog.md)
2. Product backlog priorities (from product-backlog.md)
3. Dependencies and readiness

Action: Search both backlogs, check dependencies, and recommend the highest-priority ready task.

/pm update [work-summary] - Update Plan After Work

Update the project plan to reflect completed work:

1. Update story status in backlogs
2. Mark success criteria as complete
3. Add technical debt items if needed
4. Update iteration records

Arguments: work-summary should describe what was completed (e.g., "completed E06-U05 merge functionality")

Action: Edit relevant plan files to record the work done.

/pm backlog - Show Product Backlog

Display all pending work organized by priority:

• Critical items with dependencies resolved
• High priority items ready for iteration
• Medium and low priority items
• Items blocked by dependencies

Action: Read product-backlog.md and summarize pending work grouped by readiness.

/pm iterate [name] - Start New Iteration

Create a new PDCA iteration folder:

1. Create iterations/YYYY-MM-DD-[name]/ folder
2. Copy PDCA templates from docs/04-pdca-prompts/
3. Update sprint-backlog.md with new iteration

Arguments: name is the iteration name (e.g., "merge-branch-logic")

Action: Create iteration folder with PDCA structure.

/pm debt - Show Technical Debt

Display technical debt status:

• Open debt items by severity
• Debt accumulated in recent iterations
• Total effort estimate
• Paydown recommendations

Action: Read technical-debt-register.md and summarize.

/pm lessons - Show Lessons Learned

Display project learnings and insights:

• Key learnings from completed iterations
• Patterns and practices to follow
• Pitfalls and anti-patterns to avoid
• Process improvements

Action: Read lessons-learned.md and summarize.

/pm doc-review - Documentation Review

Perform documentation review and record it:

1. Scan docs/ for documents with stale dates (>90 days old)
2. Check for broken internal links
3. Verify consistency with codebase (spot check)
4. Update the Review History table in docs/00-meta/DOCUMENTATION_OWNERSHIP.md

Options:

• --quarterly - Focus on ADRs and architecture docs only

Action: Audit documentation and add entry to Review History table:

| YYYY-MM-DD | Full audit / Quarterly | AI Agent | [Summary of findings] |

Workflow Guidelines

When Starting Work

1. Use /pm status to understand current iteration
2. Use /pm next to identify the next task
3. Check dependencies in product-backlog.md

When Completing Work

1. Use /pm update [work-summary] to record progress
2. Update story status from "🔄 In Progress" to "✅ Complete"
3. Mark success criteria as done [x]
4. Add any new technical debt to technical-debt-register.md

When Starting New Iteration

1. Review product-backlog.md for ready items
2. Select stories for the iteration
3. Use /pm iterate [name] to create iteration folder
4. Update sprint-backlog.md with selected stories
5. Create PLAN phase document with analysis

Key Principles

1. Single Source of Truth: The sprint backlog is always the current iteration status
2. PDCA Discipline: Every iteration follows Plan → Do → Check → Act structure
3. Evidence-Based Updates: Only update plan files based on actual work completed
4. Dependency Awareness: Always check dependencies before starting work
5. Debt Tracking: Record technical debt immediately when identified