workflow-grill

You can resolve ambiguous requirements by walking a prioritized decision tree one question at a time, grounding answers in repository evidence using file:line citations before implementation begins.

The best way to interrogate codebase decisions is searching the repository first and using precise path/to/file:line evidence to resolve questions automatically, only prompting the user when the code is unclear.

The decision tree clarification loop applies to interactive commands like capture, design, implement, architect, extend, and debug by asking one focused question per turn with a recommended answer until strict exit conditions are met.

Yes, you can use orchestrator-only operation to resolve under-specified requirements for software design by forcing a disciplined, evidence-first interrogation loop before any implementation or delegation begins.

To thread resolved decisions into artifact generation, output exactly one fenced Resolved decisions block that downstream commands thread into their normal artifact or delegation step.

You should not use an evidence-first interrogation loop as a standalone from-scratch workflow, as it requires orchestrator-only operation and is designed to clarify steps inside interactive commands rather than running independently.