mp-grill

To clarify requirements and resolve design ambiguity, you can use an interrogative planning approach that relentlessly questions assumptions and settles every decision-tree branch until shared understanding is reached. This ensures explicit acceptance criteria and scope.

Stress-testing a project plan involves interviewing stakeholders to surface ambiguity, edge cases, and dependencies until they are explicit. This approach reconciles requirements and closes gaps in design alignment before implementation begins.

Yes, you can use an Explore agent to inspect the codebase and answer questions directly from the source. This prevents unnecessary manual checks and grounds requirement gathering in existing codebase architecture.

You document architecture decisions and domain language by writing confirmed terms and settled choices into project files like CONTEXT.md and DECISIONS.md. This keeps documentation concise and ensures project alignment throughout the workflow.

Yes, this requirements clarification method is designed for doc-backed planning within a GitHub-driven project workflow. It reads existing context files and updates only confirmed domain terms to maintain project alignment.