architecture

Generate an ARCHITECTURE.md document from a REQUIREMENTS.md file.

294|54|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/owainlewis/blueprint --skill architecture-owainlewis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/owainlewis/blueprint/tree/main/skills/architecture
Command: npx skills add https://github.com/owainlewis/blueprint --skill architecture-owainlewis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms high-level requirements into a detailed technical architecture document, providing a clear blueprint for software development.

Core Features & Use Cases

  • Architecture Generation: Creates ARCHITECTURE.md from REQUIREMENTS.md.
  • Decision Documentation: Identifies and documents key technical decisions and assumptions.
  • Use Case: After defining project requirements, use this Skill to generate a comprehensive architecture document that guides engineers on system design, components, data flow, and more.

Quick Start

Generate the architecture document based on the existing requirements file.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I generate a technical architecture document from software requirements?

To generate a technical architecture document, you process a requirements file to produce a blueprint detailing system design, data flow, error handling, and security. This ensures all architectural decisions trace directly to specific requirements.

What should a system design document include for software development?

A system design document should include components, data flow, external dependencies, file structure, configuration, observability, security, and testing strategies. It must document key technical decisions and flag ambiguities to guide engineers effectively.

Can I create architecture documentation if my project requirements are ambiguous?

Yes, you can create architecture documentation from ambiguous requirements, but the process will actively flag those ambiguities. It ties architectural decisions to specific requirements, ensuring gaps are identified rather than silently overlooked.

How do I document technical decisions and assumptions during system design?

Document technical decisions and assumptions by mapping them directly to project requirements within the architecture file. This captures key choices regarding components, data flow, and dependencies, providing clear rationale for future development.

What is the best way to transition from requirements definition to software architecture?

The best way to transition is to transform high-level requirements directly into a comprehensive architecture document. This bridges design and development by detailing system structure, security, and observability, ensuring engineering teams have a clear blueprint.