feature-diagram

To generate per-feature architecture diagrams, this Skill extracts HTTP routes, data models, async jobs, and UI screens from a feature inventory row and writes a Mermaid flowchart slice. It connects architectural surfaces by matching a feature slug to a matrix row in feature-inventory.md.

A feature slice is a focused architectural view that isolates the HTTP routes, data models, async jobs, and UI screens participating in one specific feature. It renders as a four-quadrant Mermaid flowchart to aid architecture onboarding and refactor planning.

You create a Mermaid flowchart by running the generate command with a feature slug, such as '/feature-diagram create-order project-name'. The tool reads the inventory, extracts corroborated axis findings, writes the diagram to a features directory, and lints the Mermaid block.

Yes, you need an existing feature-inventory.md file generated by extract-features before generating architecture diagrams. The tool matches a feature slug to a matrix row within this inventory to extract corroborated findings and update the inventory backlink with the diagram target.

Yes, you can validate Mermaid diagrams generated from feature slicing using the included lint.sh script. It runs a Mermaid validation flow on the generated block, and a deterministic grep-based generate.sh helper ensures the output matches expected architectural documentation formats.

The best way to document HTTP routes and data models for a single feature is generating an isolated Mermaid flowchart slice. This approach grounds the documentation in a consolidated feature inventory, ensuring all participating surfaces are accurately mapped and validated for architecture onboarding.