factory-intake

To clarify ambiguous requirements, the system validates current inputs and poses targeted questions to generate a concrete brief, project scope, and acceptance criteria for greenfield or brownfield initiatives.

Generating a brief and scope for greenfield or brownfield evolutions requires orchestrating gate checks during the BREAK phase to produce core governance documents like brief.md, scope.md, and acceptance.md from templates.

Automating requirement clarification during the BREAK phase requires running a process that reads the current project state, validates provided inputs, and guides the user through questions to produce core governance documents.

Enriching existing documentation is fully supported for brownfield evolutions, allowing the intake process to update current briefs, scope definitions, and acceptance criteria rather than generating entirely new files from templates.

Optional resources such as scripts, references, and assets are not required but can be managed under the SKILL definition to enhance the intake process and support the generation of core project scoping documents.

Requirement scoping fails without input validation because ambiguous needs cannot be reliably transformed into concrete acceptance criteria, leading to misaligned project briefs and increased downstream rework.