- Add .claude/ configuration (agents, commands, hooks, get-shit-done workflows) - Add prompts/ directory with development planning documents - Add scripts/setup-tenants/ with tenant configuration - Add docs/screenshots/ - Remove obsolete phase2.2-corrections-report.md - Update pnpm-lock.yaml - Update detect-secrets.sh to ignore setup.sh (env var usage, not secrets) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.7 KiB
Milestone Archive Template
This template is used by the complete-milestone workflow to create archive files in .planning/milestones/.
File Template
Milestone v{{VERSION}}: {{MILESTONE_NAME}}
Status: ✅ SHIPPED {{DATE}} Phases: {{PHASE_START}}-{{PHASE_END}} Total Plans: {{TOTAL_PLANS}}
Overview
{{MILESTONE_DESCRIPTION}}
Phases
{{PHASES_SECTION}}
[For each phase in this milestone, include:]
Phase {{PHASE_NUM}}: {{PHASE_NAME}}
Goal: {{PHASE_GOAL}} Depends on: {{DEPENDS_ON}} Plans: {{PLAN_COUNT}} plans
Plans:
- {{PHASE}}-01: {{PLAN_DESCRIPTION}}
- {{PHASE}}-02: {{PLAN_DESCRIPTION}} [... all plans ...]
Details: {{PHASE_DETAILS_FROM_ROADMAP}}
For decimal phases, include (INSERTED) marker:
Phase 2.1: Critical Security Patch (INSERTED)
Goal: Fix authentication bypass vulnerability Depends on: Phase 2 Plans: 1 plan
Plans:
- 02.1-01: Patch auth vulnerability
Details: {{PHASE_DETAILS_FROM_ROADMAP}}
Milestone Summary
Decimal Phases:
- Phase 2.1: Critical Security Patch (inserted after Phase 2 for urgent fix)
- Phase 5.1: Performance Hotfix (inserted after Phase 5 for production issue)
Key Decisions: {{DECISIONS_FROM_PROJECT_STATE}} [Example:]
- Decision: Use ROADMAP.md split (Rationale: Constant context cost)
- Decision: Decimal phase numbering (Rationale: Clear insertion semantics)
Issues Resolved: {{ISSUES_RESOLVED_DURING_MILESTONE}} [Example:]
- Fixed context overflow at 100+ phases
- Resolved phase insertion confusion
Issues Deferred: {{ISSUES_DEFERRED_TO_LATER}} [Example:]
- PROJECT-STATE.md tiering (deferred until decisions > 300)
Technical Debt Incurred: {{SHORTCUTS_NEEDING_FUTURE_WORK}} [Example:]
- Some workflows still have hardcoded paths (fix in Phase 5)
For current project status, see .planning/ROADMAP.md
Usage Guidelines
**When to create milestone archives:** - After completing all phases in a milestone (v1.0, v1.1, v2.0, etc.) - Triggered by complete-milestone workflow - Before planning next milestone workHow to fill template:
- Replace {{PLACEHOLDERS}} with actual values
- Extract phase details from ROADMAP.md
- Document decimal phases with (INSERTED) marker
- Include key decisions from PROJECT-STATE.md or SUMMARY files
- List issues resolved vs deferred
- Capture technical debt for future reference
Archive location:
- Save to
.planning/milestones/v{VERSION}-{NAME}.md - Example:
.planning/milestones/v1.0-mvp.md
After archiving:
- Update ROADMAP.md to collapse completed milestone in
<details>tag - Update PROJECT.md to brownfield format with Current State section
- Continue phase numbering in next milestone (never restart at 01)