Files
msd-core/get-shit-done/templates/roadmap.md
Lex Christopherson 9ec422accd fix: consistent zero-padding for decimal phase numbers
Decimal phases now use printf "%02d" formatting to match integer phases.
Before: 6.1-01-PLAN.md vs 06-04-PLAN.md (inconsistent)
After: 06.1-01-PLAN.md vs 06-04-PLAN.md (consistent)

Closes #51

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-11 10:38:31 -06:00

5.2 KiB

Roadmap Template

Template for .planning/ROADMAP.md.

Initial Roadmap (v1.0 Greenfield)

# Roadmap: [Project Name]

## Overview

[One paragraph describing the journey from start to finish]

## Domain Expertise

[Paths to domain skills that inform planning. These SKILL.md files serve as indexes - during phase planning, read them to find relevant references for each phase type.]

- ~/.claude/skills/expertise/[domain]/SKILL.md
[Add additional domains if project spans multiple (e.g., ISF shaders + macOS app)]

Or: None

## Phases

**Phase Numbering:**
- Integer phases (1, 2, 3): Planned milestone work
- Decimal phases (2.1, 2.2): Urgent insertions (marked with INSERTED)

Decimal phases appear between their surrounding integers in numeric order.

- [ ] **Phase 1: [Name]** - [One-line description]
- [ ] **Phase 2: [Name]** - [One-line description]
- [ ] **Phase 3: [Name]** - [One-line description]
- [ ] **Phase 4: [Name]** - [One-line description]

## Phase Details

### Phase 1: [Name]
**Goal**: [What this phase delivers]
**Depends on**: Nothing (first phase)
**Research**: Unlikely (established patterns)
**Plans**: [Number of plans, e.g., "3 plans" or "TBD"]

Plans:
- [ ] 01-01: [Brief description of first plan]
- [ ] 01-02: [Brief description of second plan]
- [ ] 01-03: [Brief description of third plan]

### Phase 2: [Name]
**Goal**: [What this phase delivers]
**Depends on**: Phase 1
**Research**: Likely (new integration)
**Research topics**: [What needs investigating]
**Plans**: [Number of plans]

Plans:
- [ ] 02-01: [Brief description]
- [ ] 02-02: [Brief description]

### Phase 2.1: Critical Fix (INSERTED)
**Goal**: [Urgent work inserted between phases]
**Depends on**: Phase 2
**Plans**: 1 plan

Plans:
- [ ] 02.1-01: [Description]

### Phase 3: [Name]
**Goal**: [What this phase delivers]
**Depends on**: Phase 2
**Research**: Likely (external API)
**Research topics**: [What needs investigating]
**Plans**: [Number of plans]

Plans:
- [ ] 03-01: [Brief description]
- [ ] 03-02: [Brief description]

### Phase 4: [Name]
**Goal**: [What this phase delivers]
**Depends on**: Phase 3
**Research**: Unlikely (internal patterns)
**Plans**: [Number of plans]

Plans:
- [ ] 04-01: [Brief description]

## Progress

**Execution Order:**
Phases execute in numeric order: 2 → 2.1 → 2.2 → 3 → 3.1 → 4

| Phase | Plans Complete | Status | Completed |
|-------|----------------|--------|-----------|
| 1. [Name] | 0/3 | Not started | - |
| 2. [Name] | 0/2 | Not started | - |
| 3. [Name] | 0/2 | Not started | - |
| 4. [Name] | 0/1 | Not started | - |
**Initial planning (v1.0):** - Phase count depends on depth setting (quick: 3-5, standard: 5-8, comprehensive: 8-12) - Each phase delivers something coherent - Phases can have 1+ plans (split if >3 tasks or multiple subsystems) - Plans use naming: {phase}-{plan}-PLAN.md (e.g., 01-02-PLAN.md) - No time estimates (this isn't enterprise PM) - Progress table updated by execute workflow - Plan count can be "TBD" initially, refined during planning

Research flags:

  • Research: Likely - External APIs, new libraries, architectural decisions
  • Research: Unlikely - Internal patterns, CRUD operations, established conventions
  • Include Research topics: when Likely
  • Flags are hints, not mandates - validate at planning time

After milestones ship:

  • Collapse completed milestones in <details> tags
  • Add new milestone sections for upcoming work
  • Keep continuous phase numbering (never restart at 01)

<status_values>

  • Not started - Haven't begun
  • In progress - Currently working
  • Complete - Done (add completion date)
  • Deferred - Pushed to later (with reason) </status_values>

Milestone-Grouped Roadmap (After v1.0 Ships)

After completing first milestone, reorganize with milestone groupings:

# Roadmap: [Project Name]

## Milestones

- ✅ **v1.0 MVP** - Phases 1-4 (shipped YYYY-MM-DD)
- 🚧 **v1.1 [Name]** - Phases 5-6 (in progress)
- 📋 **v2.0 [Name]** - Phases 7-10 (planned)

## Phases

<details>
<summary>✅ v1.0 MVP (Phases 1-4) - SHIPPED YYYY-MM-DD</summary>

### Phase 1: [Name]
**Goal**: [What this phase delivers]
**Plans**: 3 plans

Plans:
- [x] 01-01: [Brief description]
- [x] 01-02: [Brief description]
- [x] 01-03: [Brief description]

[... remaining v1.0 phases ...]

</details>

### 🚧 v1.1 [Name] (In Progress)

**Milestone Goal:** [What v1.1 delivers]

#### Phase 5: [Name]
**Goal**: [What this phase delivers]
**Depends on**: Phase 4
**Plans**: 2 plans

Plans:
- [ ] 05-01: [Brief description]
- [ ] 05-02: [Brief description]

[... remaining v1.1 phases ...]

### 📋 v2.0 [Name] (Planned)

**Milestone Goal:** [What v2.0 delivers]

[... v2.0 phases ...]

## Progress

| Phase | Milestone | Plans Complete | Status | Completed |
|-------|-----------|----------------|--------|-----------|
| 1. Foundation | v1.0 | 3/3 | Complete | YYYY-MM-DD |
| 2. Features | v1.0 | 2/2 | Complete | YYYY-MM-DD |
| 5. Security | v1.1 | 0/2 | Not started | - |

Notes:

  • Milestone emoji: ✅ shipped, 🚧 in progress, 📋 planned
  • Completed milestones collapsed in <details> for readability
  • Current/future milestones expanded
  • Continuous phase numbering (01-99)
  • Progress table includes milestone column