kramme:connect-existing-feature-documentation-writer

To create feature documentation in a monorepo, you need a layered structure with a central navigation hub, separate audience-specific documents, and Mermaid diagrams. This ensures clear, actionable guidance for both product and developer teams while keeping docs maintainable.

The best way to structure documentation for both audiences is a layered approach with a central navigation hub. Separate documents for product and developer teams provide targeted guidance, while cross-referencing and Mermaid diagrams maintain consistency across architecture and API references.

To generate architecture and API references with Mermaid diagrams, use a structured workflow that enforces layered documentation. This creates technical deep-dives describing system components, data flows, and API interfaces with code snippets, ensuring cross-referenced and maintainable feature docs.

Yes, this documentation workflow enforces consistent structure and cross-linking across feature docs. It uses governed templates, prompts, and checklists to plan, author, and publish content, ensuring documentation remains up to date and properly cross-referenced as features evolve.

You need layered documentation with a navigation hub when documenting or updating features in a monorepo for distinct audiences. It is necessary when providing both product workflows and technical implementation guidance, ensuring all documents are cross-referenced and maintainable as the feature evolves.