Lex Christopherson d9625ed320 fix(planner): don't surface user_setup in planning output ...

User setup info belongs in plan frontmatter only. The execute-plan
workflow surfaces it at the right time (after automation completes).

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-16 12:29:15 -06:00

..

gsd-codebase-mapper.md

feat(gsd): add dedicated codebase mapper agent

2026-01-15 17:16:02 -06:00

gsd-debugger.md

docs(debugger): restore high-value examples and patterns

2026-01-15 16:46:10 -06:00

gsd-executor.md

style(agents): update subagent colors

2026-01-15 11:15:35 -06:00

gsd-integration-checker.md

style(agents): update subagent colors

2026-01-15 11:15:35 -06:00

gsd-phase-researcher.md

feat: integrate research into plan-phase with specialized agents

2026-01-16 10:10:22 -06:00

gsd-plan-checker.md

feat(16-01): create gsd-plan-checker agent

2026-01-16 08:56:31 -06:00

gsd-planner.md

fix(planner): don't surface user_setup in planning output

2026-01-16 12:29:15 -06:00

gsd-project-researcher.md

fix: remove commit capability from project researcher agent

2026-01-16 11:54:37 -06:00

gsd-research-synthesizer.md

fix: synthesizer commits all research files together

2026-01-16 11:52:10 -06:00

gsd-roadmapper.md

feat: unify project initialization into single /gsd:new-project flow

2026-01-16 11:15:58 -06:00

gsd-verifier.md

docs(verifier): clarify step flow for re-verification mode

2026-01-15 11:50:32 -06:00