build-architecture

Convert an approved Scope of Work into a structured System Architecture HTML document.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/aoecosystem/project-foundations --skill build-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-architecture
Source: https://github.com/aoecosystem/project-foundations/tree/main/.cursor/skills/build-architecture
Command: npx skills add https://github.com/aoecosystem/project-foundations --skill build-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts an approved Scope of Work into a complete System Architecture document that guides development, integration, and communication across teams.

Core Features & Use Cases

  • Reads the approved scope-of-work HTML and the empty system-architecture template.
  • Generates a complete seven-section Architecture document and a Mermaid diagram, then saves it to system-architecture/<slug>-system-architecture.html.
  • Transitions the pipeline stage to ARCHITECTURE_DRAFT and provides a hook for review.

Quick Start

Say '/build-architecture' after the SOW is approved to generate the architecture draft.

Frequently Asked Questions about build-architecture

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

FAQPage Schema
How do I generate a system architecture document from an approved scope of work?▼

To generate a system architecture document from an approved scope of work, use a tool that reads the SOW HTML and an architecture template to produce a structured system-architecture HTML file. This process requires the pipeline stage to be SOW_APPROVED before proceeding.

Can I automatically create a Mermaid diagram for my system architecture?▼

Yes, you can automatically create a Mermaid diagram for your system architecture by transforming an approved Scope of Work into a complete seven-section architecture document. The generated output includes the diagram and saves it to a designated system-architecture HTML file.

What is the process for converting an SOW into an architecture-ready design?▼

Converting an SOW into an architecture-ready design involves reading the approved scope-of-work HTML and an empty template to generate a structured architecture document. This action transitions the pipeline stage to ARCHITECTURE_DRAFT and provides a hook for review.

Do I need an approved SOW before starting system architecture generation?▼

Yes, you need an approved SOW before starting system architecture generation. The process explicitly validates that the current pipeline stage is SOW_APPROVED, ensuring the scope of work is finalized before creating the architecture draft.

What sections are included when transforming a scope of work into a system architecture document?▼

Transforming a scope of work into a system architecture document yields a complete seven-section architecture document. It reads the approved SOW HTML and generates the structured sections alongside a Mermaid diagram, saving the output as an HTML file.

Why does my architecture generation fail when the pipeline stage is not SOW_APPROVED?▼

Architecture generation fails when the pipeline stage is not SOW_APPROVED because the system validates the current stage before proceeding. This validation ensures the scope of work is fully approved and finalized before transforming it into a system architecture document.