generating-constrained-specs

To generate PRD and architecture documents with decision traceability, use a constrained spec generator that loads DECISIONS.yaml and RISKS.yaml to build a decision index and mandates explicit DEC-* citations for every requirement before validating against constraint gates.

Decision-backed specification generation creates PRDs and architecture documents where every claim and design choice is explicitly linked to a DEC-* decision from a decision ledger, ensuring complete traceability across product goals, requirements, and architecture.

You enforce DEC-* decision citations by applying a constraint validation gate that checks generated PRD and architecture documents, preventing uncited content delivery and cross-referencing risks to surface mitigations in one place.

Yes, constrained spec generation requires a DECISIONS.yaml ledger and a RISKS.yaml file as inputs to build the decision index and risk framework needed to produce traceable specifications with mandatory citations.

The best way to cross-reference risks across PRD and architecture documents is to load RISKS.yaml into a decision index, generate specs with mandated DEC-* citations, and validate constraint gates to surface traceability and mitigations in one place.

Generated PRD documents fail constraint gate validation when they contain uncited content, meaning requirements or design choices lack explicit DEC-* decision citations from the DECISIONS.yaml ledger required for traceable specification delivery.