architect-plan

Generate architecture documents with technology choices, APIs, and mermaid diagrams.

Updated Mar 5, 2026

Search Tags:#architecture #mermaid #plan #api-design #architect #data-model #test-strategy

Ready to run

npx skills add https://github.com/jaisonerick/spec-plugin --skill architect-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect-plan
Source: https://github.com/jaisonerick/spec-plugin/tree/main/plugins/spec-plugin/skills/architect-plan
Command: npx skills add https://github.com/jaisonerick/spec-plugin --skill architect-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts a single plan spec and surrounding product artifacts into a complete, implementation-ready architecture document that makes every important technical decision explicit and justified.

Core Features & Use Cases

Contextual analysis: Reads the target plan spec, overall architecture, roadmap, product spec, and related plans to build a complete context for decisions.
Decision engineering: Identifies technology choices, data models, API contracts, component boundaries, and integration points and evaluates trade-offs against architecture constraints.
Interactive design: Consults the user on major decision points in manageable rounds and produces mermaid diagrams, state machines, and a pragmatic test strategy.
Use Case: Prepare an implementation-ready architecture for plan-0-infrastructure before breaking it into stories and tasks.

Quick Start

Generate a comprehensive architecture document for plan-0-infrastructure using the repository specs and roadmap.

Frequently Asked Questions about architect-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an architecture document from a plan spec?▼

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.

How do you create mermaid diagrams for API design and data models?▼

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.

What is the best way to document technical decisions with trade-offs?▼

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.

Can I define a test strategy within a software architecture plan?▼

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.

Do I need an overall architecture and roadmap before generating plan specs?▼

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.

What are the limitations of automated architecture document generation?▼

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.