refactor(execute-phase): slim command, delegate to workflow

Command now references workflow for checkpoint handling details
instead of duplicating logic. Keeps command thin as intended.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Lex Christopherson
2026-01-14 16:30:23 -06:00
parent e98bebfeeb
commit aaf5bceebc
2 changed files with 6 additions and 19 deletions

2
.gitignore vendored
View File

@@ -4,4 +4,4 @@ package-lock.json
TO-DOS.md
CLAUDE.md
.planning
/research
/research.claude/

View File

@@ -158,25 +158,12 @@ All three run in parallel. Task tool blocks until all complete.
</wave_execution>
<checkpoint_handling>
Plans with `autonomous: false` in frontmatter have checkpoints:
- Run in their assigned wave (can be parallel with other plans)
- Pause at checkpoint, return structured state to orchestrator
- Orchestrator presents checkpoint to user (see execute-plan.md for presentation formats)
- User responds, orchestrator spawns fresh continuation agent
Plans with `autonomous: false` have checkpoints. The execute-phase.md workflow handles the full checkpoint flow:
- Subagent pauses at checkpoint, returns structured state
- Orchestrator presents to user, collects response
- Spawns fresh continuation agent (not resume)
**Checkpoint flow:**
1. Subagent returns `## CHECKPOINT REACHED` with Completed Tasks table
2. Orchestrator parses return and presents rich formatted checkpoint
3. User responds (approved/done/option selection)
4. Orchestrator fills continuation-prompt.md template with state
5. Spawns fresh agent: `Task(prompt=filled_continuation_template, subagent_type="general-purpose")`
**Why fresh agent, not resume:**
Task tool resume fails after multiple tool calls. Fresh agent with state handoff is the correct pattern.
**Templates:**
- `@~/.claude/get-shit-done/templates/checkpoint-return.md` - Subagent return format
- `@~/.claude/get-shit-done/templates/continuation-prompt.md` - Fresh agent spawn template
See `@~/.claude/get-shit-done/workflows/execute-phase.md` step `checkpoint_handling` for complete details.
</checkpoint_handling>
<deviation_rules>