shine-discuss-phase

Adaptive questioning in project planning surveys the codebase for reusable patterns and surfaces undecided areas for deeper analysis. It targets specific implementation gaps rather than asking generic questions, ensuring context gathering remains focused and actionable.

Generating a CONTEXT.md file involves loading prior project context, surveying the codebase for reusable patterns, and applying adaptive questioning to surface undecided areas. The output provides clear, actionable decisions that guide research, planning, and future workflow steps.

Generating a CONTEXT.md file involves loading prior project context, surveying the codebase for reusable patterns, and applying adaptive questioning to surface undecided areas. The output provides clear, actionable decisions that guide research, planning, and future workflow steps.

You can consolidate project context by loading prior markdown files including PROJECT.md, REQUIREMENTS.md, STATE.md, and previous CONTEXT.md. This anchors implementation decisions and ensures continuity across workflow cycles without repeating questions.

The best way to extract implementation decisions is to run a discuss phase workflow that loads prior context, surveys reusable codebase patterns, and outputs a concrete CONTEXT.md. This ensures researchers and planners can act without repeating questions.

Project context breaks down when implementation decisions are not locked into a dedicated file like CONTEXT.md. Without consolidating prior state and surfacing undecided areas, downstream agents must repeat questions, disrupting continuity and planning.