generate-system-design

To generate system architecture documentation, you load upstream documents like PRDs, technical architecture files, and ADRs. The skill synthesizes these inputs to produce a comprehensive markdown report detailing modules, dependencies, and data flows for engineering teams.

Documenting system modules and dependency graphs automatically involves analyzing business requirements and technical architecture inputs. This process identifies module boundaries, interfaces, and data ownership, outputting a structured markdown report with visual diagrams and traceability links.

Yes, you can use architectural decision records to create technical specification documents. The skill loads ADRs as primary input sources, extracting architectural decisions to define module purposes, internal structures, and integration guides within the final system design report.

To outline module boundaries and data flows, the system reads product requirements and technical design files to determine system modules. It defines specific module purposes, interfaces, internal structures, dependencies, and data ownership for the engineering team.

Yes, this system design documentation tool works without external dependencies. It operates autonomously with no listed dependencies, using built-in scripts, references, and assets to analyze your loaded project documents and generate the complete architecture plan.

The generated system design document is output in markdown format. This comprehensive report includes detailed module definitions, dependency graphs, data flow diagrams, and traceability links connecting the architecture back to the original product requirements.