ferrox-discuss-phase

To resolve unresolved implementation decisions before phase planning, extract open questions from prior project context and interactively discuss them with stakeholders to lock down specific approaches, constraints, and assumptions for downstream agents.

A phase-specific CONTEXT.md file synthesizes reviewed project context, requirements, and state files into a single handoff document, enabling downstream researchers and planners to proceed without re-asking settled questions or encountering ambiguity.

Extract gray area implementation choices by loading prior project state files and requirements, identifying what is already settled versus what remains undecided, and prompting the user interactively only on unresolved areas that downstream agents need clarified.

Yes, when a build phase has multiple plausible approaches, interactive discussion clarifies the phase by surfacing remaining undecided implementation choices and turning them into explicit decisions before execution begins.

Yes, prior project context, requirements, and state files must be reviewed before discussion to identify settled decisions and accurately extract only the remaining unresolved implementation choices requiring user input.

The best way to hand off locked down phase decisions is producing a phase-specific CONTEXT.md file that synthesizes all extracted context, ensuring downstream agents can plan and research without ambiguity or re-asking questions.