* feat(gsd-tools): add history-digest, atomic state operations, and summary variants Adds new performance-focused commands to gsd-tools and introduces specialized summary templates to reduce context tax: - history-digest: Compiles phase summaries into structured JSON for JIT loading - state get/patch: Enables atomic STATE.md operations instead of full rewrites - template select: Automatically chooses optimal summary template based on plan complexity - Adds minimal, standard, and complex summary templates Part of the "Hydra" architecture for GSD context optimization. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * chore: add project config * docs: define v1 requirements * docs: create roadmap (6 phases) * feat(history-digest): fix nested YAML parsing and add tests - Fix extractFrontmatter() to handle nested YAML structures like dependency-graph.provides, tech-stack.added using stack-based parsing - Add test infrastructure with Node test runner (npm test) - Update gsd-planner to use digest fields directly instead of reading full SUMMARY.md files - Add 6 schema validation tests covering nested fields, merging, malformed files, and backward compatibility Closes: HIST-01, HIST-02, HIST-03, HIST-04 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(planner): use digest for selection, full SUMMARY for understanding The previous commit went too far by eliminating full SUMMARY reads. The digest is an index for smart selection, not a replacement for understanding what actually happened. Two-step approach: 1. Digest to score/select relevant phases (2-4 typically) 2. Full SUMMARY read for selected phases (implementation details) 3. Digest-level context retained for unselected phases Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(gsd-tools): add phases, roadmap, and phase commands TDD implementation of three new commands to replace repetitive bash: phases list [--type plans|summaries] [--phase N] - Lists phase directories sorted numerically (handles decimals) - Filter by file type or specific phase - Replaces: ls -d .planning/phases/*/ | sort -V (22 occurrences) roadmap get-phase <N> - Extracts phase section from ROADMAP.md - Returns name, goal, full section content - Replaces: grep -A20 "Phase X:" ROADMAP.md (19 occurrences) phase next-decimal <N> - Calculates next decimal phase (06 → 06.1, 06.2 → 06.3) - Handles gaps, normalizes input - Replaces: complex bash math in insert-phase (3 occurrences) 16 new tests, all passing. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * refactor: migrate agents/workflows to use gsd-tools commands Replace inline bash patterns with centralized gsd-tools commands: phases list: - audit-milestone.md: ls -d .planning/phases/*/ | sort -V - plan-milestone-gaps.md: ls -d ... | sort -V | tail -1 roadmap get-phase: - plan-phase.md: grep -A5 "Phase X:" ROADMAP.md (2 occurrences) - research-phase.md: grep patterns (2 occurrences) - verify-phase.md: grep -A5 pattern - gsd-verifier.md: grep -A5 pattern - gsd-plan-checker.md: grep -A10 pattern - commands/gsd/research-phase.md: grep patterns (2 occurrences) phase next-decimal: - insert-phase.md: complex bash decimal calculation - decimal-phase-calculation.md: reference doc rewritten phase-argument-parsing.md: updated to reference gsd-tools Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
257 lines
5.9 KiB
Markdown
257 lines
5.9 KiB
Markdown
<purpose>
|
|
Create all phases necessary to close gaps identified by `/gsd:audit-milestone`. Reads MILESTONE-AUDIT.md, groups gaps into logical phases, creates phase entries in ROADMAP.md, and offers to plan each phase. One command creates all fix phases — no manual `/gsd:add-phase` per gap.
|
|
</purpose>
|
|
|
|
<required_reading>
|
|
Read all files referenced by the invoking prompt's execution_context before starting.
|
|
</required_reading>
|
|
|
|
<process>
|
|
|
|
## 1. Load Audit Results
|
|
|
|
```bash
|
|
# Find the most recent audit file
|
|
ls -t .planning/v*-MILESTONE-AUDIT.md 2>/dev/null | head -1
|
|
```
|
|
|
|
Parse YAML frontmatter to extract structured gaps:
|
|
- `gaps.requirements` — unsatisfied requirements
|
|
- `gaps.integration` — missing cross-phase connections
|
|
- `gaps.flows` — broken E2E flows
|
|
|
|
If no audit file exists or has no gaps, error:
|
|
```
|
|
No audit gaps found. Run `/gsd:audit-milestone` first.
|
|
```
|
|
|
|
## 2. Prioritize Gaps
|
|
|
|
Group gaps by priority from REQUIREMENTS.md:
|
|
|
|
| Priority | Action |
|
|
|----------|--------|
|
|
| `must` | Create phase, blocks milestone |
|
|
| `should` | Create phase, recommended |
|
|
| `nice` | Ask user: include or defer? |
|
|
|
|
For integration/flow gaps, infer priority from affected requirements.
|
|
|
|
## 3. Group Gaps into Phases
|
|
|
|
Cluster related gaps into logical phases:
|
|
|
|
**Grouping rules:**
|
|
- Same affected phase → combine into one fix phase
|
|
- Same subsystem (auth, API, UI) → combine
|
|
- Dependency order (fix stubs before wiring)
|
|
- Keep phases focused: 2-4 tasks each
|
|
|
|
**Example grouping:**
|
|
```
|
|
Gap: DASH-01 unsatisfied (Dashboard doesn't fetch)
|
|
Gap: Integration Phase 1→3 (Auth not passed to API calls)
|
|
Gap: Flow "View dashboard" broken at data fetch
|
|
|
|
→ Phase 6: "Wire Dashboard to API"
|
|
- Add fetch to Dashboard.tsx
|
|
- Include auth header in fetch
|
|
- Handle response, update state
|
|
- Render user data
|
|
```
|
|
|
|
## 4. Determine Phase Numbers
|
|
|
|
Find highest existing phase:
|
|
```bash
|
|
# Get sorted phase list, extract last one
|
|
PHASES=$(node ~/.claude/get-shit-done/bin/gsd-tools.js phases list)
|
|
HIGHEST=$(echo "$PHASES" | jq -r '.directories[-1]')
|
|
```
|
|
|
|
New phases continue from there:
|
|
- If Phase 5 is highest, gaps become Phase 6, 7, 8...
|
|
|
|
## 5. Present Gap Closure Plan
|
|
|
|
```markdown
|
|
## Gap Closure Plan
|
|
|
|
**Milestone:** {version}
|
|
**Gaps to close:** {N} requirements, {M} integration, {K} flows
|
|
|
|
### Proposed Phases
|
|
|
|
**Phase {N}: {Name}**
|
|
Closes:
|
|
- {REQ-ID}: {description}
|
|
- Integration: {from} → {to}
|
|
Tasks: {count}
|
|
|
|
**Phase {N+1}: {Name}**
|
|
Closes:
|
|
- {REQ-ID}: {description}
|
|
- Flow: {flow name}
|
|
Tasks: {count}
|
|
|
|
{If nice-to-have gaps exist:}
|
|
|
|
### Deferred (nice-to-have)
|
|
|
|
These gaps are optional. Include them?
|
|
- {gap description}
|
|
- {gap description}
|
|
|
|
---
|
|
|
|
Create these {X} phases? (yes / adjust / defer all optional)
|
|
```
|
|
|
|
Wait for user confirmation.
|
|
|
|
## 6. Update ROADMAP.md
|
|
|
|
Add new phases to current milestone:
|
|
|
|
```markdown
|
|
### Phase {N}: {Name}
|
|
**Goal:** {derived from gaps being closed}
|
|
**Requirements:** {REQ-IDs being satisfied}
|
|
**Gap Closure:** Closes gaps from audit
|
|
|
|
### Phase {N+1}: {Name}
|
|
...
|
|
```
|
|
|
|
## 7. Create Phase Directories
|
|
|
|
```bash
|
|
mkdir -p ".planning/phases/{NN}-{name}"
|
|
```
|
|
|
|
## 8. Commit Roadmap Update
|
|
|
|
```bash
|
|
node ~/.claude/get-shit-done/bin/gsd-tools.js commit "docs(roadmap): add gap closure phases {N}-{M}" --files .planning/ROADMAP.md
|
|
```
|
|
|
|
## 9. Offer Next Steps
|
|
|
|
```markdown
|
|
## ✓ Gap Closure Phases Created
|
|
|
|
**Phases added:** {N} - {M}
|
|
**Gaps addressed:** {count} requirements, {count} integration, {count} flows
|
|
|
|
---
|
|
|
|
## ▶ Next Up
|
|
|
|
**Plan first gap closure phase**
|
|
|
|
`/gsd:plan-phase {N}`
|
|
|
|
<sub>`/clear` first → fresh context window</sub>
|
|
|
|
---
|
|
|
|
**Also available:**
|
|
- `/gsd:execute-phase {N}` — if plans already exist
|
|
- `cat .planning/ROADMAP.md` — see updated roadmap
|
|
|
|
---
|
|
|
|
**After all gap phases complete:**
|
|
|
|
`/gsd:audit-milestone` — re-audit to verify gaps closed
|
|
`/gsd:complete-milestone {version}` — archive when audit passes
|
|
```
|
|
|
|
</process>
|
|
|
|
<gap_to_phase_mapping>
|
|
|
|
## How Gaps Become Tasks
|
|
|
|
**Requirement gap → Tasks:**
|
|
```yaml
|
|
gap:
|
|
id: DASH-01
|
|
description: "User sees their data"
|
|
reason: "Dashboard exists but doesn't fetch from API"
|
|
missing:
|
|
- "useEffect with fetch to /api/user/data"
|
|
- "State for user data"
|
|
- "Render user data in JSX"
|
|
|
|
becomes:
|
|
|
|
phase: "Wire Dashboard Data"
|
|
tasks:
|
|
- name: "Add data fetching"
|
|
files: [src/components/Dashboard.tsx]
|
|
action: "Add useEffect that fetches /api/user/data on mount"
|
|
|
|
- name: "Add state management"
|
|
files: [src/components/Dashboard.tsx]
|
|
action: "Add useState for userData, loading, error states"
|
|
|
|
- name: "Render user data"
|
|
files: [src/components/Dashboard.tsx]
|
|
action: "Replace placeholder with userData.map rendering"
|
|
```
|
|
|
|
**Integration gap → Tasks:**
|
|
```yaml
|
|
gap:
|
|
from_phase: 1
|
|
to_phase: 3
|
|
connection: "Auth token → API calls"
|
|
reason: "Dashboard API calls don't include auth header"
|
|
missing:
|
|
- "Auth header in fetch calls"
|
|
- "Token refresh on 401"
|
|
|
|
becomes:
|
|
|
|
phase: "Add Auth to Dashboard API Calls"
|
|
tasks:
|
|
- name: "Add auth header to fetches"
|
|
files: [src/components/Dashboard.tsx, src/lib/api.ts]
|
|
action: "Include Authorization header with token in all API calls"
|
|
|
|
- name: "Handle 401 responses"
|
|
files: [src/lib/api.ts]
|
|
action: "Add interceptor to refresh token or redirect to login on 401"
|
|
```
|
|
|
|
**Flow gap → Tasks:**
|
|
```yaml
|
|
gap:
|
|
name: "User views dashboard after login"
|
|
broken_at: "Dashboard data load"
|
|
reason: "No fetch call"
|
|
missing:
|
|
- "Fetch user data on mount"
|
|
- "Display loading state"
|
|
- "Render user data"
|
|
|
|
becomes:
|
|
|
|
# Usually same phase as requirement/integration gap
|
|
# Flow gaps often overlap with other gap types
|
|
```
|
|
|
|
</gap_to_phase_mapping>
|
|
|
|
<success_criteria>
|
|
- [ ] MILESTONE-AUDIT.md loaded and gaps parsed
|
|
- [ ] Gaps prioritized (must/should/nice)
|
|
- [ ] Gaps grouped into logical phases
|
|
- [ ] User confirmed phase plan
|
|
- [ ] ROADMAP.md updated with new phases
|
|
- [ ] Phase directories created
|
|
- [ ] Changes committed
|
|
- [ ] User knows to run `/gsd:plan-phase` next
|
|
</success_criteria>
|