four-documents

To generate a project deliverable kit from scattered sources, draft the Datasheet, Specification, Guidance, and Procedure documents in a unified workflow. This grounds all four artifacts in local references to prevent misalignment.

Maintaining cross-document consistency across a specification and procedure requires a source-grounded workflow that enforces provenance. Citing authoritative source slices ensures all generated artifacts remain aligned during drafting.

The best way to create source-grounded documentation for a software decomposition deliverable is using a staged workflow. It drafts the four-document kit for a single SOFTWARE_DECOMP unit while citing local references for provenance.

You can track document drafting status safely across multiple passes using _STATUS.md. The workflow checks the current _STATUS.md state and completes the run with a safe status update to prevent overwriting progress.

Yes, you need existing local references to draft the four-document kit. The workflow generates synchronized deliverables for a PROJECT_DECOMP or SOFTWARE_DECOMP unit by grounding the content directly in those authoritative local sources.

Project documentation loses provenance when drafted separately because scattered sources cause misalignment between artifacts. A unified, source-grounded workflow enforces cross-document consistency by citing source slices directly.