architecture-skeleton

Define architecture skeletons and ADRs with technology stack and NFR policies for Wave A projects.

Updated Feb 6, 2026

Search Tags:#architecture #ADR #NFR #tech-stack #design-docs #wave-a

Ready to run

npx skills add https://github.com/sizukutamago/blueprint-plugin --skill architecture-skeleton

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-skeleton
Source: https://github.com/sizukutamago/blueprint-plugin/tree/main/skills/architecture-skeleton
Command: npx skills add https://github.com/sizukutamago/blueprint-plugin --skill architecture-skeleton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to quickly establish a coherent high-level architecture and ADRs before diving into Wave A design work. This skill provides a structured starting point that wires together architecture skeletons, technology stack choices, and NFR policies.

Core Features & Use Cases

Define the high-level architecture skeleton and identify key components, boundaries, and interactions.
Capture technology stack decisions and align with NFR policies for Wave A.
Generate ADRs to document rationale and allow traceability across the project lifecycle.

Quick Start

Use the architecture-skeleton skill to outline a high-level architecture skeleton and ADRs from your project requirements and output docs/03_architecture/architecture.md and docs/03_architecture/adr.md.

Frequently Asked Questions about architecture-skeleton

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

FAQPage Schema

How do I define an architecture skeleton and record ADRs before starting design work?▼

To define an architecture skeleton and record ADRs, outline high-level components, boundaries, and interactions, then capture technology stack decisions aligned with NFR policies to generate architecture.md and adr.md documentation.

What is the best way to document technology stack decisions and NFR policies for a new project?▼

Documenting technology stack decisions and NFR policies is best done by generating Architecture Decision Records, which provide structured rationale and traceability for your project's chosen tech stack and non-functional requirements.

How do I structure architecture documentation to cover system boundaries and component interactions?▼

Structure architecture documentation by defining a high-level architecture skeleton that identifies key components, maps system boundaries, and clarifies interactions, outputting the results into a dedicated architecture.md file.

When do I need to create ADRs for my software architecture?▼

You need to create ADRs when making technology stack selections and defining NFR policies, ensuring that the rationale for each architectural decision is documented and traceable across the project lifecycle.

Can I generate architecture documentation files for parallel design phases without manual formatting?▼

Yes, you can generate architecture documentation files for parallel design phases by defining the architecture skeleton and NFR policies, which automatically outputs structured architecture.md and adr.md files.