docs(10-01): update documentation mentions to execute-plan.md

- commands/gsd/resume-task.md: infrastructure mention
- get-shit-done/workflows/plan-phase.md: execution context reference
- get-shit-done/templates/agent-history.md: 2 workflow mentions
- get-shit-done/templates/summary.md: 3 workflow mentions
- get-shit-done/templates/codebase/structure.md: example workflow

commands/gsd/resume-task.md

@@ -16,7 +16,7 @@ Resume an interrupted subagent execution using the Task tool's resume parameter.
 
 When a session ends mid-execution, subagents may be left in an incomplete state. This command allows users to continue that work without starting over.
 
-Uses the agent ID tracking infrastructure from execute-phase to identify and resume agents.
+Uses the agent ID tracking infrastructure from execute-plan to identify and resume agents.
 </objective>
 
 <execution_context>

get-shit-done/templates/agent-history.md

@@ -63,7 +63,7 @@ spawned ────────────────────────
 ### When to Create File
 
 Create `.planning/agent-history.json` from this template when:
-- First subagent spawn in execute-phase workflow
+- First subagent spawn in execute-plan workflow
 - File doesn't exist yet
 
 ### When to Add Entry
@@ -152,7 +152,7 @@ Then add new entry with resumed status:
 
 ## Template Notes
 
-**When to create:** First subagent spawn during execute-phase workflow.
+**When to create:** First subagent spawn during execute-plan workflow.
 
 **Location:** `.planning/agent-history.json`
 

get-shit-done/templates/codebase/structure.md

@@ -166,7 +166,7 @@ get-shit-done/
 **get-shit-done/workflows/**
 - Purpose: Reusable multi-step procedures
 - Contains: Workflow definitions called by commands
-- Key files: execute-phase.md, research-phase.md
+- Key files: execute-plan.md, research-phase.md
 - Subdirectories: None
 
 ## Key File Locations

get-shit-done/templates/summary.md

@@ -139,7 +139,7 @@ Logged to .planning/ISSUES.md for future consideration:
 
 **Patterns:** Established conventions future phases should maintain.
 
-**Population:** Frontmatter is populated during summary creation in execute-phase.md. See `<step name="create_summary">` for field-by-field guidance.
+**Population:** Frontmatter is populated during summary creation in execute-plan.md. See `<step name="create_summary">` for field-by-field guidance.
 </frontmatter_guidance>
 
 <one_liner_rules>
@@ -238,7 +238,7 @@ Logged to .planning/ISSUES.md for future consideration:
 <guidelines>
 **When to create:**
 - After completing each phase plan
-- Required output from execute-phase workflow
+- Required output from execute-plan workflow
 - Documents what actually happened vs what was planned
 
 **Frontmatter completion:**

get-shit-done/workflows/plan-phase.md

@@ -361,7 +361,7 @@ Use template from `~/.claude/get-shit-done/templates/phase-prompt.md`.
 Each plan follows template structure with:
 - Frontmatter (phase, plan, type, domain)
 - Objective (plan-specific goal, purpose, output)
-- Execution context (execute-phase.md, summary template, checkpoints.md if needed)
+- Execution context (execute-plan.md, summary template, checkpoints.md if needed)
 - Context (@references to PROJECT, ROADMAP, STATE, codebase docs, RESEARCH/DISCOVERY/CONTEXT if exist, prior summaries, source files, prior decisions, deferred issues, concerns)
 - Tasks (XML format with types)
 - Verification, Success criteria, Output specification