analyze-requirements

To turn a vague idea into a validated requirements document, apply a structured RA0–RA5 diagnostic dialogue to surface the true problem, define acceptance criteria, and document constraints before any design begins.

The best way to write testable requirements is to guide the feature request through a structured diagnostic progression, ensuring validation and outputting a scoped V1 boundary with a clear constraint inventory.

You generate acceptance criteria and a risk inventory by validating the project scope through a structured diagnostic, outputting the results to a docs/requirements-planning/<topic>.md artifact.

Yes, you can use an RA0–RA5 structured dialogue to prevent premature design decisions, ensuring no implementation choices are made until the requirements are fully validated and scoped.

You need a requirements validation process when handling new projects or incomplete requirements that lack clarity, ensuring you establish a scoped V1 boundary and handoff readiness before design begins.

Yes, this requirements discovery method outputs a docs/requirements-planning/<topic>.md artifact containing the validated requirements, ensuring handoff readiness for design-solution with clear upstream and downstream traces.