architect-plan

To generate an architecture document from a plan spec, the Skill reads your target plan, overall architecture, and roadmap to identify technology choices, API contracts, and data models, then produces an implementation-ready document with mermaid diagrams.

Creating mermaid diagrams for API design and data models involves analyzing your plan spec context to map out component boundaries and integration points, then automatically generating state machines and structural diagrams to visualize the architecture.

The best way to document technical decisions with trade-offs is to enumerate key choices for technology, data models, and API design, evaluating each against your architecture constraints while interactively consulting you to resolve any unresolved design points.

Yes, you can define a test strategy within a software architecture plan. The Skill produces a pragmatic test strategy alongside your API contracts and integration points, ensuring your implementation-ready architecture document covers validation requirements.

You need an overall architecture, roadmap, and target plan spec available in your product repository before starting. The Skill uses these surrounding product artifacts to build complete context and make justified technical decisions.

A limitation of automated architecture document generation is that it applies to a single plan within a product repository at a time, requiring interactive user consultation across manageable rounds to resolve major decision points rather than operating fully autonomously.