idd-workflow

To convert vague software requirements into verifiable engineering artifacts, an intent-driven workflow maps human intent into structured spec layers like narrative, model, contract, and certification, ensuring traceability across the capability lifecycle.

To start spec-first development for a new capability, begin by generating a solution narrative to capture personas and journeys, establishing foundational scope before creating downstream models, contracts, and fixtures.

To maintain certification traceability from initial intent to final implementation, apply a structured multi-layer workflow that generates evidence alignment across spec artifacts, connecting personas, journeys, stories, and contracts directly to certification.

Use intent-driven workflow orchestration instead of direct task execution when task clarity is uncertain, such as starting new capabilities or onboarding, guiding narrative-to-scope conversion to ensure repo overlay constraints are loaded.

Yes, workflow orchestration supports carrying forward repo overlay constraints during development by performing a repo preflight with overlay resolution, ensuring all constraint carry-forward is maintained across generated spec artifacts.