get-shit-done-cc 1.5.27 → 1.5.29

package/get-shit-done/templates/context.md

@@ -4,6 +4,8 @@ Template for `.planning/phases/XX-name/{phase}-CONTEXT.md` - captures implementa
 
 **Purpose:** Document decisions that downstream agents need. Researcher uses this to know WHAT to investigate. Planner uses this to know WHAT choices are locked vs flexible.
 
+**Key principle:** Categories are NOT predefined. They emerge from what was actually discussed for THIS phase. A CLI phase has CLI-relevant sections, a UI phase has UI-relevant sections.
+
 **Downstream consumers:**
 - `gsd-phase-researcher` — Reads decisions to focus research (e.g., "card layout" → research card component patterns)
 - `gsd-planner` — Reads decisions to create specific tasks (e.g., "infinite scroll" → task includes virtualization)
@@ -28,11 +30,14 @@ Template for `.planning/phases/XX-name/{phase}-CONTEXT.md` - captures implementa
 <decisions>
 ## Implementation Decisions
 
-### [Category discussed, e.g., UI]
+### [Area 1 that was discussed]
 - [Specific decision made]
 - [Another decision if applicable]
 
-### [Category discussed, e.g., Behavior]
+### [Area 2 that was discussed]
+- [Specific decision made]
+
+### [Area 3 that was discussed]
 - [Specific decision made]
 
 ### Claude's Discretion
@@ -65,6 +70,9 @@ Template for `.planning/phases/XX-name/{phase}-CONTEXT.md` - captures implementa
 ```
 
 <good_examples>
+
+**Example 1: Visual feature (Post Feed)**
+
 ```markdown
 # Phase 3: Post Feed - Context
 
@@ -81,18 +89,17 @@ Display posts from followed users in a scrollable feed. Users can view posts and
 <decisions>
 ## Implementation Decisions
 
-### UI
+### Layout style
 - Card-based layout, not timeline or list
 - Each card shows: author avatar, name, timestamp, full post content, reaction counts
 - Cards have subtle shadows, rounded corners — modern feel
-- Show 10 posts initially, load more on scroll
 
-### Behavior
+### Loading behavior
 - Infinite scroll, not pagination
 - Pull-to-refresh on mobile
 - New posts indicator at top ("3 new posts") rather than auto-inserting
 
-### Empty State
+### Empty state
 - Friendly illustration + "Follow people to see posts here"
 - Suggest 3-5 accounts to follow based on interests
 
@@ -108,7 +115,6 @@ Display posts from followed users in a scrollable feed. Users can view posts and
 
 - "I like how Twitter shows the new posts indicator without disrupting your scroll position"
 - Cards should feel like Linear's issue cards — clean, not cluttered
-- No infinite scroll fatigue — maybe show "You're all caught up" after ~50 posts
 
 </specifics>
 
@@ -116,7 +122,6 @@ Display posts from followed users in a scrollable feed. Users can view posts and
 ## Deferred Ideas
 
 - Commenting on posts — Phase 5
-- Reaction picker (not just counts) — Phase 5
 - Bookmarking posts — add to backlog
 
 </deferred>
@@ -126,6 +131,131 @@ Display posts from followed users in a scrollable feed. Users can view posts and
 *Phase: 03-post-feed*
 *Context gathered: 2025-01-20*
 ```
+
+**Example 2: CLI tool (Database backup)**
+
+```markdown
+# Phase 2: Backup Command - Context
+
+**Gathered:** 2025-01-20
+**Status:** Ready for planning
+
+<domain>
+## Phase Boundary
+
+CLI command to backup database to local file or S3. Supports full and incremental backups. Restore command is a separate phase.
+
+</domain>
+
+<decisions>
+## Implementation Decisions
+
+### Output format
+- JSON for programmatic use, table format for humans
+- Default to table, --json flag for JSON
+- Verbose mode (-v) shows progress, silent by default
+
+### Flag design
+- Short flags for common options: -o (output), -v (verbose), -f (force)
+- Long flags for clarity: --incremental, --compress, --encrypt
+- Required: database connection string (positional or --db)
+
+### Error recovery
+- Retry 3 times on network failure, then fail with clear message
+- --no-retry flag to fail fast
+- Partial backups are deleted on failure (no corrupt files)
+
+### Claude's Discretion
+- Exact progress bar implementation
+- Compression algorithm choice
+- Temp file handling
+
+</decisions>
+
+<specifics>
+## Specific Ideas
+
+- "I want it to feel like pg_dump — familiar to database people"
+- Should work in CI pipelines (exit codes, no interactive prompts)
+
+</specifics>
+
+<deferred>
+## Deferred Ideas
+
+- Scheduled backups — separate phase
+- Backup rotation/retention — add to backlog
+
+</deferred>
+
+---
+
+*Phase: 02-backup-command*
+*Context gathered: 2025-01-20*
+```
+
+**Example 3: Organization task (Photo library)**
+
+```markdown
+# Phase 1: Photo Organization - Context
+
+**Gathered:** 2025-01-20
+**Status:** Ready for planning
+
+<domain>
+## Phase Boundary
+
+Organize existing photo library into structured folders. Handle duplicates and apply consistent naming. Tagging and search are separate phases.
+
+</domain>
+
+<decisions>
+## Implementation Decisions
+
+### Grouping criteria
+- Primary grouping by year, then by month
+- Events detected by time clustering (photos within 2 hours = same event)
+- Event folders named by date + location if available
+
+### Duplicate handling
+- Keep highest resolution version
+- Move duplicates to _duplicates folder (don't delete)
+- Log all duplicate decisions for review
+
+### Naming convention
+- Format: YYYY-MM-DD_HH-MM-SS_originalname.ext
+- Preserve original filename as suffix for searchability
+- Handle name collisions with incrementing suffix
+
+### Claude's Discretion
+- Exact clustering algorithm
+- How to handle photos with no EXIF data
+- Folder emoji usage
+
+</decisions>
+
+<specifics>
+## Specific Ideas
+
+- "I want to be able to find photos by roughly when they were taken"
+- Don't delete anything — worst case, move to a review folder
+
+</specifics>
+
+<deferred>
+## Deferred Ideas
+
+- Face detection grouping — future phase
+- Cloud sync — out of scope for now
+
+</deferred>
+
+---
+
+*Phase: 01-photo-organization*
+*Context gathered: 2025-01-20*
+```
+
 </good_examples>
 
 <guidelines>
@@ -133,11 +263,11 @@ Display posts from followed users in a scrollable feed. Users can view posts and
 
 The output should answer: "What does the researcher need to investigate? What choices are locked for the planner?"
 
-**Good content:**
+**Good content (concrete decisions):**
 - "Card-based layout, not timeline"
-- "Infinite scroll with pull-to-refresh"
-- "Show 10 posts initially"
-- "New posts indicator rather than auto-insert"
+- "Retry 3 times on network failure, then fail"
+- "Group by year, then by month"
+- "JSON for programmatic use, table for humans"
 
 **Bad content (too vague):**
 - "Should feel modern and clean"
@@ -148,7 +278,7 @@ The output should answer: "What does the researcher need to investigate? What ch
 **Sections explained:**
 
 - **Domain** — The scope anchor. Copied/derived from ROADMAP.md. Fixed boundary.
-- **Decisions** — Organized by category (UI, UX, Behavior, etc.). Actual choices made.
+- **Decisions** — Organized by areas discussed (NOT predefined categories). Section headers come from the actual discussion — "Layout style", "Flag design", "Grouping criteria", etc.
 - **Claude's Discretion** — Explicit acknowledgment of what Claude can decide during implementation.
 - **Specifics** — Product references, examples, "like X but..." statements.
 - **Deferred** — Ideas captured but explicitly out of scope. Prevents scope creep while preserving good ideas.

package/get-shit-done/templates/phase-prompt.md

@@ -573,5 +573,4 @@ Task completion ≠ Goal achievement. A task "create chat component" can complet
 5. Gaps found → fix plans created → execute → re-verify
 6. All must_haves pass → phase complete
 
-See `~/.claude/get-shit-done/references/goal-backward.md` for derivation process.
 See `~/.claude/get-shit-done/workflows/verify-phase.md` for verification logic.

package/get-shit-done/templates/planner-subagent-prompt.md

@@ -34,7 +34,7 @@ Template for spawning gsd-planner agent. The agent contains all planning experti
 </planning_context>
 
 <downstream_consumer>
-Output consumed by /gsd:execute-phase or /gsd:execute-plan
+Output consumed by /gsd:execute-phase
 Plans must be executable prompts with:
 - Frontmatter (wave, depends_on, files_modified, autonomous)
 - Tasks in XML format

package/get-shit-done/workflows/discovery-phase.md

@@ -107,7 +107,7 @@ For: Choosing between options, new external integration.
 
 5. **Cross-verify:** Any WebSearch finding → confirm with Context7/official docs.
 
-6. **Quality check:** Before finalizing findings, consult ~/.claude/get-shit-done/references/research-pitfalls.md to avoid common research gaps.
+6. **Quality check:** Before finalizing findings, consult the gsd-researcher agent's verification protocols to avoid common research gaps.
 
 7. **Create DISCOVERY.md** using ~/.claude/get-shit-done/templates/discovery.md structure:
 
@@ -160,7 +160,7 @@ For: Architectural decisions, novel problems, high-risk choices.
    - Mark what's verified vs assumed
    - Flag contradictions
 
-6. **Quality check:** Before finalizing findings, consult ~/.claude/get-shit-done/references/research-pitfalls.md to ensure comprehensive coverage and avoid common research gaps.
+6. **Quality check:** Before finalizing findings, consult the gsd-researcher agent's verification protocols to ensure comprehensive coverage and avoid common research gaps.
 
 7. **Create comprehensive DISCOVERY.md:**
 

package/get-shit-done/workflows/discuss-phase.md

@@ -66,23 +66,44 @@ For now, let's focus on [phase domain]."
 Capture the idea in a "Deferred Ideas" section. Don't lose it, don't act on it.
 </scope_guardrail>
 
-<gray_area_categories>
-Use these categories when analyzing a phase. Not all apply to every phase.
-
-| Category | What it clarifies | Example questions |
-|----------|-------------------|-------------------|
-| **UI** | Visual presentation, layout, information density | "Card-based or list view?" "What info shows on each item?" |
-| **UX** | Interactions, flows, feedback | "How does loading work?" "What happens when you tap X?" |
-| **Behavior** | Runtime behavior, state changes | "Auto-refresh or manual?" "How does pagination work?" |
-| **Empty/Edge States** | What shows in unusual situations | "What appears with no data?" "How do errors display?" |
-| **Content** | What information is shown/hidden | "Show timestamps?" "How much preview text?" |
-
-**Categories to AVOID:**
-- **Scope** — The roadmap defines scope, not discussion
-- **Technical** — You figure out implementation
-- **Architecture** — You decide patterns
-- **Performance** — You handle optimization
-</gray_area_categories>
+<gray_area_identification>
+Gray areas are **implementation decisions the user cares about** — things that could go multiple ways and would change the result.
+
+**How to identify gray areas:**
+
+1. **Read the phase goal** from ROADMAP.md
+2. **Understand the domain** — What kind of thing is being built?
+   - Something users SEE → visual presentation, interactions, states matter
+   - Something users CALL → interface contracts, responses, errors matter
+   - Something users RUN → invocation, output, behavior modes matter
+   - Something users READ → structure, tone, depth, flow matter
+   - Something being ORGANIZED → criteria, grouping, handling exceptions matter
+3. **Generate phase-specific gray areas** — Not generic categories, but concrete decisions for THIS phase
+
+**Don't use generic category labels** (UI, UX, Behavior). Generate specific gray areas:
+
+```
+Phase: "User authentication"
+→ Session handling, Error responses, Multi-device policy, Recovery flow
+
+Phase: "Organize photo library"
+→ Grouping criteria, Duplicate handling, Naming convention, Folder structure
+
+Phase: "CLI for database backups"
+→ Output format, Flag design, Progress reporting, Error recovery
+
+Phase: "API documentation"
+→ Structure/navigation, Code examples depth, Versioning approach, Interactive elements
+```
+
+**The key question:** What decisions would change the outcome that the user should weigh in on?
+
+**Claude handles these (don't ask):**
+- Technical implementation details
+- Architecture patterns
+- Performance optimization
+- Scope (roadmap defines this)
+</gray_area_identification>
 
 <process>
 
@@ -109,8 +130,9 @@ Exit workflow.
 Check if CONTEXT.md already exists:
 
 ```bash
-ls .planning/phases/${PHASE}-*/CONTEXT.md 2>/dev/null
-ls .planning/phases/${PHASE}-*/${PHASE}-CONTEXT.md 2>/dev/null
+# Match both zero-padded (05-*) and unpadded (5-*) folders
+PADDED_PHASE=$(printf "%02d" ${PHASE})
+ls .planning/phases/${PADDED_PHASE}-*/CONTEXT.md .planning/phases/${PADDED_PHASE}-*/${PADDED_PHASE}-CONTEXT.md .planning/phases/${PHASE}-*/CONTEXT.md .planning/phases/${PHASE}-*/${PHASE}-CONTEXT.md 2>/dev/null
 ```
 
 **If exists:**
@@ -168,47 +190,79 @@ We'll clarify HOW to implement this.
 
 **Then use AskUserQuestion (multiSelect: true):**
 - header: "Discuss"
-- question: "Which areas do you want to discuss?"
-- options: Generate 2-4 based on your analysis, each formatted as:
-  - "[Category] — [Specific gray area question]"
-  - Last option always: "None — you decide, proceed to planning"
+- question: "Which areas do you want to discuss for [phase name]?"
+- options: Generate 3-4 phase-specific gray areas, each formatted as:
+  - "[Specific area]" (label) — concrete, not generic
+  - [1-2 questions this covers] (description)
+
+**Do NOT include a "skip" or "you decide" option.** User ran this command to discuss — give them real choices.
+
+**Examples by domain:**
 
-**Example options:**
+For "Post Feed" (visual feature):
 ```
-☐ UI — Card layout or timeline? How much of each post shows?
-☐ Behavior — Infinite scroll or pagination? Pull to refresh?
-☐ Empty state — What appears when there are no posts?
-☐ None — You decide, proceed to planning
+☐ Layout style — Cards vs list vs timeline? Information density?
+☐ Loading behavior — Infinite scroll or pagination? Pull to refresh?
+☐ Content ordering — Chronological, algorithmic, or user choice?
+☐ Post metadata — What info per post? Timestamps, reactions, author?
 ```
 
-If user selects "None": Skip to write_context with minimal context.
-Otherwise: Continue to discuss_areas with selected areas.
+For "Database backup CLI" (command-line tool):
+```
+☐ Output format — JSON, table, or plain text? Verbosity levels?
+☐ Flag design — Short flags, long flags, or both? Required vs optional?
+☐ Progress reporting — Silent, progress bar, or verbose logging?
+☐ Error recovery — Fail fast, retry, or prompt for action?
+```
+
+For "Organize photo library" (organization task):
+```
+☐ Grouping criteria — By date, location, faces, or events?
+☐ Duplicate handling — Keep best, keep all, or prompt each time?
+☐ Naming convention — Original names, dates, or descriptive?
+☐ Folder structure — Flat, nested by year, or by category?
+```
+
+Continue to discuss_areas with selected areas.
 </step>
 
 <step name="discuss_areas">
 For each selected area, conduct a focused discussion loop.
 
+**Philosophy: 4 questions, then check.**
+
+Ask 4 questions per area before offering to continue or move on. Each answer often reveals the next question.
+
 **For each area:**
 
 1. **Announce the area:**
    ```
-   Let's talk about [Category].
+   Let's talk about [Area].
    ```
 
-2. **Ask focused questions using AskUserQuestion:**
-   - header: "[Category]"
-   - question: Specific question about that gray area
-   - options: 2-3 concrete choices + "Let me describe" + "You decide"
+2. **Ask 4 questions using AskUserQuestion:**
+   - header: "[Area]"
+   - question: Specific decision for this area
+   - options: 2-3 concrete choices (AskUserQuestion adds "Other" automatically)
+   - Include "You decide" as an option when reasonable — captures Claude discretion
+
+3. **After 4 questions, check:**
+   - header: "[Area]"
+   - question: "More questions about [area], or move to next?"
+   - options: "More questions" / "Next area"
+
+   If "More questions" → ask 4 more, then check again
+   If "Next area" → proceed to next selected area
 
-3. **Follow up based on response:**
-   - If they chose an option: Capture it, ask if there's more about this area
-   - If "Let me describe": Receive their input, reflect it back, confirm understanding
-   - If "You decide": Note that Claude has discretion here
+4. **After all areas complete:**
+   - header: "Done"
+   - question: "That covers [list areas]. Ready to create context?"
+   - options: "Create context" / "Revisit an area"
 
-4. **Loop control — Always offer:**
-   - "Ask more about [Category]" — Continue probing this area
-   - "Move to next area" — Done with this category
-   - "That's enough, create context" — Done with all discussion
+**Question design:**
+- Options should be concrete, not abstract ("Cards" not "Option A")
+- Each answer should inform the next question
+- If user picks "Other", receive their input, reflect it back, confirm
 
 **Scope creep handling:**
 If user mentions something outside the phase domain:
@@ -216,24 +270,30 @@ If user mentions something outside the phase domain:
 "[Feature] sounds like a new capability — that belongs in its own phase.
 I'll note it as a deferred idea.
 
-Back to [current domain]: [return to current question]"
+Back to [current area]: [return to current question]"
 ```
 
 Track deferred ideas internally.
-
-**Continue until:**
-- User says "Move to next area" and all selected areas are done, OR
-- User says "That's enough, create context"
 </step>
 
 <step name="write_context">
 Create CONTEXT.md capturing decisions made.
 
-**File location:** `.planning/phases/${PADDED_PHASE}-${SLUG}/${PADDED_PHASE}-CONTEXT.md`
+**Find or create phase directory:**
 
-Zero-pad the phase number: `PADDED_PHASE=$(printf "%02d" ${PHASE})`
+```bash
+# Match existing directory (padded or unpadded)
+PADDED_PHASE=$(printf "%02d" ${PHASE})
+PHASE_DIR=$(ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE}-* 2>/dev/null | head -1)
+if [ -z "$PHASE_DIR" ]; then
+  # Create from roadmap name (lowercase, hyphens)
+  PHASE_NAME=$(grep "Phase ${PHASE}:" .planning/ROADMAP.md | sed 's/.*Phase [0-9]*: //' | tr '[:upper:]' '[:lower:]' | tr ' ' '-')
+  mkdir -p ".planning/phases/${PADDED_PHASE}-${PHASE_NAME}"
+  PHASE_DIR=".planning/phases/${PADDED_PHASE}-${PHASE_NAME}"
+fi
+```
 
-Create phase directory if it doesn't exist. Use roadmap phase name for slug (lowercase, hyphens).
+**File location:** `${PHASE_DIR}/${PADDED_PHASE}-CONTEXT.md`
 
 **Structure the content by what was discussed:**
 
@@ -334,18 +394,18 @@ Created: .planning/phases/${PADDED_PHASE}-${SLUG}/${PADDED_PHASE}-CONTEXT.md
 Commit phase context:
 
 ```bash
-git add .planning/phases/${PHASE}-${SLUG}/${PHASE}-CONTEXT.md
+git add "${PHASE_DIR}/${PADDED_PHASE}-CONTEXT.md"
 git commit -m "$(cat <<'EOF'
-docs(${PHASE}): capture phase context
+docs(${PADDED_PHASE}): capture phase context
 
-Phase ${PHASE}: ${PHASE_NAME}
+Phase ${PADDED_PHASE}: ${PHASE_NAME}
 - Implementation decisions documented
 - Phase boundary established
 EOF
 )"
 ```
 
-Confirm: "Committed: docs(${PHASE}): capture phase context"
+Confirm: "Committed: docs(${PADDED_PHASE}): capture phase context"
 </step>
 
 </process>

package/get-shit-done/workflows/execute-phase.md

@@ -39,7 +39,9 @@ Options:
 Confirm phase exists and has plans:
 
 ```bash
-PHASE_DIR=$(ls -d .planning/phases/${PHASE_ARG}* 2>/dev/null | head -1)
+# Match both zero-padded (05-*) and unpadded (5-*) folders
+PADDED_PHASE=$(printf "%02d" ${PHASE_ARG} 2>/dev/null || echo "${PHASE_ARG}")
+PHASE_DIR=$(ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE_ARG}-* 2>/dev/null | head -1)
 if [ -z "$PHASE_DIR" ]; then
   echo "ERROR: No phase directory matching '${PHASE_ARG}'"
   exit 1

package/get-shit-done/workflows/execute-plan.md

@@ -1196,7 +1196,7 @@ You will NOT be resumed. A new agent continues from where you stopped, using you
 
 **How to know if you were spawned:**
 
-If you're reading this workflow because an orchestrator spawned you (vs running directly from /gsd:execute-plan), the orchestrator's prompt will include checkpoint return instructions. Follow those instructions when you hit a checkpoint.
+If you're reading this workflow because an orchestrator spawned you (vs running directly), the orchestrator's prompt will include checkpoint return instructions. Follow those instructions when you hit a checkpoint.
 
 **If running in main context (not spawned):**
 
@@ -1701,7 +1701,7 @@ Summary: .planning/phases/{phase-dir}/{phase}-{plan}-SUMMARY.md
 
 **{phase}-{next-plan}: [Plan Name]** — [objective from next PLAN.md]
 
-`/gsd:execute-plan .planning/phases/{phase-dir}/{phase}-{next-plan}-PLAN.md`
+`/gsd:execute-phase {phase}`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/get-shit-done/workflows/map-codebase.md

@@ -170,7 +170,7 @@ Continue to collect_confirmations.
 <step name="collect_confirmations">
 Wait for all 4 agents to complete.
 
-Use TaskOutput tool to collect confirmations from each agent.
+Read each agent's output file to collect confirmations.
 
 **Expected confirmation format from each agent:**
 ```
@@ -282,7 +282,7 @@ End workflow.
 - .planning/codebase/ directory created
 - 4 parallel gsd-codebase-mapper agents spawned with run_in_background=true
 - Agents write documents directly (orchestrator doesn't receive document contents)
-- TaskOutput used to collect confirmations only
+- Read agent output files to collect confirmations
 - All 7 codebase documents exist
 - Clear completion summary with line counts
 - User offered clear next steps in GSD style

package/get-shit-done/workflows/resume-project.md

@@ -121,7 +121,7 @@ Present complete project status to user:
     Task: [task description from agent-history.json]
     Interrupted: [timestamp]
 
-    Resume with: /gsd:resume-task
+    Resume with: Task tool (resume parameter with agent ID)
 
 [If pending todos exist:]
 📋 [N] pending todos — /gsd:check-todos to review
@@ -141,7 +141,7 @@ Present complete project status to user:
 Based on project state, determine the most logical next action:
 
 **If interrupted agent exists:**
-→ Primary: Resume interrupted agent (/gsd:resume-task)
+→ Primary: Resume interrupted agent (Task tool with resume parameter)
 → Option: Start fresh (abandon agent work)
 
 **If .continue-here file exists:**
@@ -178,11 +178,9 @@ Present contextual options based on project state:
 What would you like to do?
 
 [Primary action based on state - e.g.:]
-1. Resume interrupted agent (/gsd:resume-task) [if interrupted agent found]
+1. Resume interrupted agent [if interrupted agent found]
    OR
-1. Resume from checkpoint (/gsd:execute-plan .planning/phases/XX-name/.continue-here-02-01.md)
-   OR
-1. Execute next plan (/gsd:execute-plan .planning/phases/XX-name/02-02-PLAN.md)
+1. Execute phase (/gsd:execute-phase {phase})
    OR
 1. Discuss Phase 3 context (/gsd:discuss-phase 3) [if CONTEXT.md missing]
    OR
@@ -217,7 +215,7 @@ Based on user selection, route to appropriate workflow:
 
   **{phase}-{plan}: [Plan Name]** — [objective from PLAN.md]
 
-  `/gsd:execute-plan [path]`
+  `/gsd:execute-phase {phase}`
 
   <sub>`/clear` first → fresh context window</sub>
 

package/get-shit-done/workflows/verify-phase.md

@@ -19,7 +19,6 @@ Then verify each level against the actual codebase.
 
 <required_reading>
 **Load these references:**
-- ~/.claude/get-shit-done/references/goal-backward.md (derivation process)
 - ~/.claude/get-shit-done/references/verification-patterns.md (detection patterns)
 - ~/.claude/get-shit-done/templates/verification-report.md (output format)
 </required_reading>
@@ -30,8 +29,9 @@ Then verify each level against the actual codebase.
 **Gather all verification context:**
 
 ```bash
-# Phase directory
-PHASE_DIR=$(ls -d .planning/phases/${PHASE_ARG}* 2>/dev/null | head -1)
+# Phase directory (match both zero-padded and unpadded)
+PADDED_PHASE=$(printf "%02d" ${PHASE_ARG} 2>/dev/null || echo "${PHASE_ARG}")
+PHASE_DIR=$(ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE_ARG}-* 2>/dev/null | head -1)
 
 # Phase goal from ROADMAP
 grep -A 5 "Phase ${PHASE_NUM}" .planning/ROADMAP.md
@@ -97,7 +97,7 @@ If no must_haves in frontmatter, derive using goal-backward process:
 
 5. **Document derived must-haves** before proceeding to verification.
 
-See ~/.claude/get-shit-done/references/goal-backward.md for detailed derivation guidance.
+<!-- Goal-backward derivation expertise is baked into the gsd-verifier agent -->
 </step>
 
 <step name="verify_truths">

package/get-shit-done/workflows/verify-work.md

@@ -73,8 +73,9 @@ Continue to `create_uat_file`.
 Parse $ARGUMENTS as phase number (e.g., "4") or plan number (e.g., "04-02").
 
 ```bash
-# Find phase directory
-PHASE_DIR=$(ls -d .planning/phases/${PHASE_ARG}* 2>/dev/null | head -1)
+# Find phase directory (match both zero-padded and unpadded)
+PADDED_PHASE=$(printf "%02d" ${PHASE_ARG} 2>/dev/null || echo "${PHASE_ARG}")
+PHASE_DIR=$(ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE_ARG}-* 2>/dev/null | head -1)
 
 # Find SUMMARY files
 ls "$PHASE_DIR"/*-SUMMARY.md 2>/dev/null