36f5bb3d5f
Add 10 new CLI commands that replace manual AI orchestration of mechanical, deterministic operations — saving tokens and reducing errors on the most complex GSD workflows. New commands: - phase add <desc> — append phase to roadmap + create directory - phase insert <after> <desc> — insert decimal phase - phase remove <N> [--force] — remove phase with full renumbering - phase complete <N> — mark done, update state + roadmap, detect milestone end - roadmap analyze — unified roadmap parser with disk status - milestone complete <ver> [--name] — archive roadmap/requirements/audit - validate consistency — check phase numbering and disk/roadmap sync - progress [json|table|bar] — render progress in various formats - todo complete <file> — move todo from pending to completed - scaffold [context|uat|verification|phase-dir] — template generation Updated workflows to use new CLI commands: - remove-phase.md: 13 manual steps → 1 CLI call + confirm + commit - add-phase.md: 6 manual steps → 1 CLI call + state update - insert-phase.md: 7 manual steps → 1 CLI call + state update - transition.md: roadmap/state updates delegated to phase complete - progress.md: roadmap parsing delegated to roadmap analyze - complete-milestone.md: archival delegated to milestone complete 75 tests passing (33 new). https://claude.ai/code/session_01UhMGMrNGGn2bfeAi7MBphs
130 lines
3.5 KiB
Markdown
130 lines
3.5 KiB
Markdown
<purpose>
|
|
Insert a decimal phase for urgent work discovered mid-milestone between existing integer phases. Uses decimal numbering (72.1, 72.2, etc.) to preserve the logical sequence of planned phases while accommodating urgent insertions without renumbering the entire roadmap.
|
|
</purpose>
|
|
|
|
<required_reading>
|
|
Read all files referenced by the invoking prompt's execution_context before starting.
|
|
</required_reading>
|
|
|
|
<process>
|
|
|
|
<step name="parse_arguments">
|
|
Parse the command arguments:
|
|
- First argument: integer phase number to insert after
|
|
- Remaining arguments: phase description
|
|
|
|
Example: `/gsd:insert-phase 72 Fix critical auth bug`
|
|
-> after = 72
|
|
-> description = "Fix critical auth bug"
|
|
|
|
If arguments missing:
|
|
|
|
```
|
|
ERROR: Both phase number and description required
|
|
Usage: /gsd:insert-phase <after> <description>
|
|
Example: /gsd:insert-phase 72 Fix critical auth bug
|
|
```
|
|
|
|
Exit.
|
|
|
|
Validate first argument is an integer.
|
|
</step>
|
|
|
|
<step name="init_context">
|
|
Load phase operation context:
|
|
|
|
```bash
|
|
INIT=$(node ~/.claude/get-shit-done/bin/gsd-tools.js init phase-op "${after_phase}")
|
|
```
|
|
|
|
Check `roadmap_exists` from init JSON. If false:
|
|
```
|
|
ERROR: No roadmap found (.planning/ROADMAP.md)
|
|
```
|
|
Exit.
|
|
</step>
|
|
|
|
<step name="insert_phase">
|
|
**Delegate the phase insertion to gsd-tools:**
|
|
|
|
```bash
|
|
RESULT=$(node ~/.claude/get-shit-done/bin/gsd-tools.js phase insert "${after_phase}" "${description}")
|
|
```
|
|
|
|
The CLI handles:
|
|
- Verifying target phase exists in ROADMAP.md
|
|
- Calculating next decimal phase number (checking existing decimals on disk)
|
|
- Generating slug from description
|
|
- Creating the phase directory (`.planning/phases/{N.M}-{slug}/`)
|
|
- Inserting the phase entry into ROADMAP.md after the target phase with (INSERTED) marker
|
|
|
|
Extract from result: `phase_number`, `after_phase`, `name`, `slug`, `directory`.
|
|
</step>
|
|
|
|
<step name="update_project_state">
|
|
Update STATE.md to reflect the inserted phase:
|
|
|
|
1. Read `.planning/STATE.md`
|
|
2. Under "## Accumulated Context" → "### Roadmap Evolution" add entry:
|
|
```
|
|
- Phase {decimal_phase} inserted after Phase {after_phase}: {description} (URGENT)
|
|
```
|
|
|
|
If "Roadmap Evolution" section doesn't exist, create it.
|
|
</step>
|
|
|
|
<step name="completion">
|
|
Present completion summary:
|
|
|
|
```
|
|
Phase {decimal_phase} inserted after Phase {after_phase}:
|
|
- Description: {description}
|
|
- Directory: .planning/phases/{decimal-phase}-{slug}/
|
|
- Status: Not planned yet
|
|
- Marker: (INSERTED) - indicates urgent work
|
|
|
|
Roadmap updated: .planning/ROADMAP.md
|
|
Project state updated: .planning/STATE.md
|
|
|
|
---
|
|
|
|
## Next Up
|
|
|
|
**Phase {decimal_phase}: {description}** -- urgent insertion
|
|
|
|
`/gsd:plan-phase {decimal_phase}`
|
|
|
|
<sub>`/clear` first -> fresh context window</sub>
|
|
|
|
---
|
|
|
|
**Also available:**
|
|
- Review insertion impact: Check if Phase {next_integer} dependencies still make sense
|
|
- Review roadmap
|
|
|
|
---
|
|
```
|
|
</step>
|
|
|
|
</process>
|
|
|
|
<anti_patterns>
|
|
|
|
- Don't use this for planned work at end of milestone (use /gsd:add-phase)
|
|
- Don't insert before Phase 1 (decimal 0.1 makes no sense)
|
|
- Don't renumber existing phases
|
|
- Don't modify the target phase content
|
|
- Don't create plans yet (that's /gsd:plan-phase)
|
|
- Don't commit changes (user decides when to commit)
|
|
</anti_patterns>
|
|
|
|
<success_criteria>
|
|
Phase insertion is complete when:
|
|
|
|
- [ ] `gsd-tools phase insert` executed successfully
|
|
- [ ] Phase directory created
|
|
- [ ] Roadmap updated with new phase entry (includes "(INSERTED)" marker)
|
|
- [ ] STATE.md updated with roadmap evolution note
|
|
- [ ] User informed of next steps and dependency implications
|
|
</success_criteria>
|