- Analyze phase to identify gray areas by category (UI, UX, Behavior, etc.)
- Present multi-select for user to choose which areas to discuss
- Deep-dive each selected area with focused questioning loop
- Explicit scope guardrail: clarify HOW, never expand WHAT
- Capture deferred ideas without acting on them
- Downstream awareness: CONTEXT.md feeds researcher and planner agents
- Template restructured for decisions (domain, decisions, discretion, deferred)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Split gsd-researcher into two specialized agents:
- gsd-phase-researcher: tailored for phase research before planning
- gsd-project-researcher: tailored for ecosystem research before roadmap
Updated /gsd:plan-phase to auto-research before planning:
- Research runs if no RESEARCH.md exists (silent use if exists)
- --research flag forces re-research
- --skip-research flag bypasses research entirely
- Researchers commit their output
This enables single-command workflow: /gsd:plan-phase does
research → plan → verify in one orchestrated flow.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Adds back guidance that was lost during consolidation:
- Task sizing heuristic (15-60 min target)
- Signals for too large / too small tasks
- Specificity side-by-side examples table
- "The test" for checking task clarity
Tasks completed: 3/3
- Add revision_mode section with 6-step process
- Update role section for revision mode
- Add REVISION COMPLETE return format
SUMMARY: .planning/phases/16-plan-verification-loop/16-03-SUMMARY.md
- Plans created (PLANNING COMPLETE or CHECKPOINT handled)
- gsd-plan-checker spawned (unless --skip-verify)
- Verification passed OR user override OR max iterations with user decision
- User sees status between agent spawns
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Steps 1-7: Validate, parse, spawn planner (existing flow)
- Step 8: Spawn gsd-plan-checker with verification_context
- Step 9: Handle checker return (passed | issues)
- Step 10: Revision loop (max 3 iterations)
- Step 11: Present final status with verification outcome
User sees ping-pong between planner and checker in main context.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Remove context: fork (orchestrator stays in main context)
- Add --skip-verify flag to argument-hint
- Add Task tool to allowed-tools for spawning checker
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Tasks completed: 2/2
- Create gsd-plan-checker agent with six verification dimensions
- Examples included for common failure modes
SUMMARY: .planning/phases/16-plan-verification-loop/16-01-SUMMARY.md
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Replaced 868-line workflow with deprecation notice
- Points to agents/gsd-planner.md for methodology
- Documents historical content for reference
- Kept file for git history
Note clarifies relationship with gsd-planner agent:
- Planning methodology is in agents/gsd-planner.md
- This template defines the PLAN.md output format
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- principles.md: redirects to <philosophy> section
- plan-format.md: redirects to <plan_format> section
- scope-estimation.md: redirects to <scope_estimation> section
- goal-backward.md: redirects to <goal_backward> section
All content preserved in agents/gsd-planner.md
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Adds context: fork and agent: general-purpose to plan-phase command.
This isolates the heavy discovery/synthesis work in a fresh 200k context
window, keeping the main conversation clean.
Removes AskUserQuestion from allowed-tools (workflow doesn't use it).
This agent was correctly deleted in f3e0e69 (subagents can't spawn
subagents), then accidentally re-added in d07ef33 during install fix.
The command audit-milestone.md is the orchestrator. No agent needed.
- Install statusline.sh to {claudeDir}/hooks/
- Configure statusLine in settings.json automatically
- Skip if statusline already exists (non-interactive)
- Prompt to keep/replace in interactive mode
- Add --force-statusline flag to override
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
research-phase.md:
- Added <key_insight> framing ("what don't I know that I don't know")
- Added <downstream_consumer> explaining plan-phase integration
- Added <quality_gate> checklist
research-project.md:
- Added milestone context (greenfield vs v1.1+)
- Added <downstream_consumer> per dimension
- Added <quality_gate> per agent
- Enhanced roadmap implications guidance
gsd-researcher.md:
- Simplified <gsd_integration> to point to orchestrator-provided context
- Agent is now pure research capability, context is injected
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Reduces context exhaustion during /gsd:map-codebase by having agents
write documents directly instead of returning findings to orchestrator.
- Create gsd-codebase-mapper agent with embedded templates
- Agent understands downstream consumers (plan-phase, execute-plan)
- Parameterized by focus: tech, arch, quality, concerns
- Each focus writes specific documents directly to .planning/codebase/
- Orchestrator receives only confirmation + line counts
Context savings: ~40 lines returned vs potentially thousands of lines
of exploration findings previously transferred back to orchestrator.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Explains why research matters: output directly consumed by plan-phase.
Documents the contract between RESEARCH.md sections and planning workflow.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The context section now includes @.planning/MILESTONE-CONTEXT.md so
Claude actually loads the file from discuss-milestone instead of just
seeing a text mention in the process steps.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Reduce from ~540 lines (command + workflow) to 130 lines
- Delegate research methodology to gsd-researcher agent
- Keep phase validation, context gathering in orchestrator
- Add spawn and continuation patterns for agent
