3306a77a79
The discuss-phase command file contained a 93-line detailed <process> block that competed with the actual workflow file. The agent treated this summary as complete instructions and never read the execution_context files (discuss-phase.md, discuss-phase-assumptions.md, context.md template). Root cause: Unlike execute-phase and plan-phase commands (which have short 2-line process blocks deferring to the workflow file), discuss-phase had inline step-by-step instructions detailed enough to act on without reading the referenced workflow files. Changes: - Replace discuss-phase command's <process> block with a short directive that forces reading the workflow file, matching execute-phase/plan-phase pattern - Add MANDATORY instruction that execution_context files ARE the instructions, not optional reading - Register workflow.research_before_questions and workflow.discuss_mode as valid config keys (were missing from VALID_CONFIG_KEYS) - Fix config key mismatch: workflows referenced "research_questions" but documented key is "workflow.research_before_questions" - Move research_before_questions from hooks section to workflow section in settings workflow - Add research_before_questions default to config template and builder - Add suggestion mapping for deprecated hooks.research_questions key - Add 6 regression tests covering config keys and process block guard Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.6 KiB
name, description, argument-hint, allowed-tools
| name | description | argument-hint | allowed-tools | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| gsd:discuss-phase | Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (Claude picks recommended defaults). | <phase> [--auto] [--batch] [--analyze] [--text] |
|
How it works:
- Load prior context (PROJECT.md, REQUIREMENTS.md, STATE.md, prior CONTEXT.md files)
- Scout codebase for reusable assets and patterns
- Analyze phase — skip gray areas already decided in prior phases
- Present remaining gray areas — user selects which to discuss
- Deep-dive each selected area until satisfied
- Create CONTEXT.md with decisions that guide research and planning
Output: {phase_num}-CONTEXT.md — decisions clear enough that downstream agents can act without asking the user again
<execution_context>
@/.claude/get-shit-done/workflows/discuss-phase.md
@/.claude/get-shit-done/workflows/discuss-phase-assumptions.md
@~/.claude/get-shit-done/templates/context.md
</execution_context>
Context files are resolved in-workflow using init phase-op and roadmap/state tool calls.
If DISCUSS_MODE is "assumptions": Read and execute @~/.claude/get-shit-done/workflows/discuss-phase-assumptions.md end-to-end.
If DISCUSS_MODE is "discuss" (or unset, or any other value): Read and execute @~/.claude/get-shit-done/workflows/discuss-phase.md end-to-end.
MANDATORY: The execution_context files listed above ARE the instructions. Read the workflow file BEFORE taking any action. The objective and success_criteria sections in this command file are summaries — the workflow file contains the complete step-by-step process with all required behaviors, config checks, and interaction patterns. Do not improvise from the summary.
<success_criteria>
- Prior context loaded and applied (no re-asking decided questions)
- Gray areas identified through intelligent analysis
- User chose which areas to discuss
- Each selected area explored until satisfied
- Scope creep redirected to deferred ideas
- CONTEXT.md captures decisions, not vague vision
- User knows next steps </success_criteria>