gsd-discuss-phase

Loading prior project artifacts like PROJECT.md and REQUIREMENTS.md, then interactively resolving gray areas, captures phase-specific implementation decisions. This produces a phase-numbered CONTEXT.md with actionable constraints for downstream researchers and planners.

Phase context gathering collects unresolved implementation questions and contextual constraints for a specific development phase. You need it when prior artifacts like PROJECT.md and STATE.md exist but require clarification before research and planning tasks can proceed.

Generate a CONTEXT.md file by running an interactive workflow that loads PROJECT.md, REQUIREMENTS.md, STATE.md, and previous CONTEXT.md files. The workflow scouts the codebase for patterns, identifies gray areas, and records your decisions in the phase-numbered output file.

Yes, interactive phase planning requires prior artifacts like PROJECT.md, REQUIREMENTS.md, STATE.md, and earlier CONTEXT.md files to exist. The workflow analyzes these documents and repository patterns to avoid re-asking previously decided questions and prepare actionable research tasks.

You can automate context gathering and decision capture by running the workflow with the --auto flag. This applies automated defaults to identified gray areas instead of interactive questions, still producing a phase-numbered CONTEXT.md containing actionable implementation decisions for downstream agents.

The best way to resolve gray areas before handing off to planner agents is to use an adaptive discussion workflow that identifies unresolved questions and presents them for user selection. It deep-dives into each selected area via interactive questions, then outputs a CONTEXT.md with concrete implementation decisions.