flagship-docs-create

To generate full project documentation, define your project outcome and scope, then use a contracts-first approach to produce vision, requirements, architecture, invariants, NFRs, risk registers, and testing strategies.

A contracts-first documentation approach generates versioned domain contracts before implementation, ensuring requirements are testable and maintaining full traceability from requirements to tests and release gates.

Traceability from requirements to tests is maintained by generating a comprehensive traceability matrix that links vision, requirements, architecture, and testing strategies to release and rollback plans.

Yes, you can generate architecture, risk registers, and non-functional requirements for new projects without existing documentation by providing the initial outcome and scope to establish foundational files.

The best way to create a release and rollback strategy alongside requirements is to generate a complete documentation package that includes testing strategies and plan slices for end-to-end implementation.

No, you do not need existing architecture files to generate invariants and non-functional requirements; the documentation package can be created from scratch based solely on the provided outcome and scope.