carl-dev-flow-requirements

Structured requirements development is coordinated through a staged lifecycle from draft to revised draft to final, involving user, Sisyphus, and Hephaestus roles with explicit artifact handling and review rules to ensure traceability.

The pre-draft interrogation procedure is a structured questioning process that surfaces unknowns and shapes business intent before producing a requirements draft, ensuring acceptance criteria are fully defined prior to artifact creation.

Traceability for requirements artifacts is ensured through artifact-location guidance and promotion rules that govern the transition from draft to final, applying an explicit output contract to guardrail decisions.

No prior artifact management setup is required to begin defining acceptance criteria for stakeholders; loading the Skill initiates the structured interrogation to produce the initial draft directly.

The best way to manage the transition to a final requirements artifact is through explicit artifact-location guidance and promotion rules, applying the staged review roles to validate the revised draft before finalization.

Explicit output contracts and guardrails are needed in requirements development to enforce structured artifact handling, prevent unreviewed changes, and maintain decision traceability across the Sisyphus and Hephaestus workflow stages.