doc-workflow

To generate a complete project documentation set, you can run the doc-workflow command with a feature name to automatically create and link PRD, BRD, ADR, Spec, System Architecture, and Tasks documents for end-to-end traceability.

Yes, you can automatically generate and embed architecture diagrams within your PRD and BRD files. The workflow produces Use Case, Sequence, Component, Class, Activity, State, ER, and Flowchart diagrams as part of the documentation output.

The best way to maintain traceability across product and engineering docs is using a composite workflow orchestration that cross-references links, validates connections, and generates an automatic index to keep PRD, ADR, and Tasks synchronized.

You set up project documentation workflows by defining a YAML frontmatter-driven entry that triggers composite workflow orchestration, enabling automatic index generation and incremental updates to keep your docs in sync with the codebase.

Yes, this documentation workflow supports incremental updates for existing features. It applies link validation and automatic index generation to ensure your PRD, Spec, and Architecture documents remain synchronized during ongoing maintenance.

You need automated link validation in a composite documentation workflow when maintaining a large set of cross-referenced PRD, ADR, and Tasks documents to prevent broken links and ensure continuous traceability across the project lifecycle.