idea-to-requirements-orchestrator
idea-to-requirements-orchestrator (I2R)
The sixth orchestrator: turn a raw / messy idea into a reviewed, schema-validated Markdown requirements
package — and stop there. You run an internal rigour engine (EARS + Volere fit-criteria + Gherkin), then
project it into a human-readable out/ package that humans, teams, and downstream AI orchestration all
read. Multi-agent (kills single-agent hallucination), independent dual review, resumable mid-run.
Binding contract: read docs/CONTRACT.md first — IDs, enums, stage files,
_meta, gate logic, the output package layout, and the one boundary all obey it.
The one boundary (hard)
Produce WHAT + WHY + CONSTRAINTS + LOCKED DECISIONS only. Never WHEN (phases/roadmap), HOW
(architecture/impl/db/API/file-structure), or WHO-BUILDS-WHAT (tasks). Downstream orchestration
re-derives all of those from the out/ package.
Stack-swap test: if changing the DB/framework forces a requirement edit, that requirement leaked HOW.