Phase Planning

Workflow

1. User describes issue: "Section 4.2 repeats section 4.8"
2. Skill analyzes: Reads both sections, identifies overlap
3. Skill proposes: Exact consolidation strategy with specific edits
4. Result: Cleaner, more maintainable documentation

Key Principles

• Clarity over brevity: Prefer explicit over implicit
• DRY principle: One place for each decision
• Forward reference: Explain why deferred work is deferred
• Traceability: Cross-reference related sections
• Testability: Completion checklists use verifiable criteria

Common Tasks

Document Structure

Phases typically follow:

1. Goals: Why this phase? What does it enable?
2. Dependencies: What earlier phases does it need?
3. Design: Architecture and approach
4. Implementation: Tasks, workflows, file structure
5. Proof Concept: First feature showing system works
6. Deferred: Future work with justification
7. Completion Checklist: Specific, testable items

Related Documentation

• Full roadmap: docs/migration-plan/README.md
• Individual phases: docs/migration-plan/phase-NN-*.md
• Quick reference: See .github/AGENTS.md for planning agents