gsd-discuss-phase

Capturing implementation decisions requires adaptively questioning the team to resolve gray areas before planning. This skill loads prior phase artifacts like PROJECT.md and STATE.md, scouts the codebase, and asks targeted questions to distill explicit choices into a phase-specific CONTEXT.md for downstream agents.

Adaptive questioning for codebase context building dynamically identifies unresolved gray areas by analyzing prior artifacts and codebase state. It routes between interactive discussion and assumptions-first flows, ensuring only unsettled decisions are queried rather than re-asking established requirements.

To avoid re-asking settled questions, load prior phase artifacts including PROJECT.md, REQUIREMENTS.md, and previous CONTEXT.md files. This context-aware execution scouts the codebase to identify only remaining gray areas, skipping previously resolved decisions and generating a focused phase-specific context file.

Yes, you can generate a CONTEXT.md file automatically by running the skill in non-interactive mode using the --auto flag. This bypasses interactive gray area selection and produces a phase-specific context output based on existing artifacts and codebase scouting.

Workflow routing supports multiple decision capture modes including an interactive full discussion flow, an assumptions-first flow, and an auto mode to skip interactivity. Routing behavior is configured via config files, determining how gray areas are processed and resolved for the output context.

Automated decision capture relies entirely on existing prior artifacts and codebase scouting quality. If PROJECT.md, REQUIREMENTS.md, or STATE.md files are incomplete or outdated, the adaptive questioning may misidentify gray areas, and the auto mode will generate assumptions without user validation for downstream agents.