gaia-create-arch

Orchestrate PRD-to-ADR architecture authoring and generate a validated architecture document.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-create-arch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-create-arch
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-create-arch
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-create-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Orchestrates end-to-end architecture authoring by delegating design work to the architect subagent and generating a validated architecture document.

Core Features & Use Cases

  • Load upstream artifacts such as PRD, threat model, UX design, and brownfield documentation to inform architecture decisions.
  • Coordinate technology selection, system and data architecture, API design, and infrastructure planning with the architect subagent, producing a complete architecture artifact.
  • Generate and store the architecture document at docs/planning-artifacts/architecture.md using the architecture-template.md and inline ADRs that map decisions to business requirements.

Quick Start

Provide the PRD at docs/planning-artifacts/prd.md and start the architecture workflow to generate the architecture document.

Frequently Asked Questions about gaia-create-arch

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

FAQPage Schema
How do I generate an architecture document from a PRD?

To generate an architecture document from a PRD, provide your PRD at docs/planning-artifacts/prd.md. The orchestrator delegates design work to the architect subagent and outputs a validated architecture.md file.

What is the best way to write ADRs for system design?

Writing ADRs for system design is handled by generating inline Architecture Decision Records within the architecture.md output. The workflow maps technology choices directly to business requirements defined in your PRD.

Can I use this for brownfield architecture design?

Yes, you can use this for brownfield architecture design. The workflow loads existing brownfield documentation alongside upstream artifacts like threat models and UX designs to inform your architecture decisions.

Do I need a completed PRD before starting the architecture workflow?

Yes, a completed PRD is a strict prerequisite. The workflow enforces PRD prerequisites at docs/planning-artifacts/prd.md before coordinating tech selection, data architecture, and infrastructure planning.

How does the architect subagent coordinate API design and infrastructure planning?

The architect subagent coordinates API design and infrastructure planning by loading upstream artifacts, iterating on technology selection, and producing a complete architecture artifact using the architecture-template.md.

What limitations exist when generating validated architecture documents?

Limitations include strict dependency on the PRD format and output path. The workflow enforces the PRD prerequisite and strictly outputs the validated architecture document to docs/planning-artifacts/architecture.md.