garura:arch

Generate grounded product architecture artifacts with traceable decisions and validated layers.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill garura-arch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: garura:arch
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/plays/arch
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill garura-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps teams produce a complete, deterministic architecture shape for a product—grounded in upstream specify/design inputs, user answers, and KB memory—so enterprise delivery can proceed without guesswork or invented components.

Core Features & Use Cases

  • Six canonical architecture artifacts: Produces a refined quality profile, systems inventory, logical architecture, physical architecture, tech stack with patterns, and a technical risk register.
  • Grounded, non-invented decisions: Ensures every component and decision traces back to upstream artifacts, project-profile pins, KB entries, or captured user answers.
  • Layered design with safety checks: Builds a layer model, maps capabilities end-to-end, prevents graph cycles, and validates the architecture specification.

Quick Start

Run the arch play with your current product context so it produces the six architecture artifacts under architecture/.

Frequently Asked Questions about garura:arch

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

FAQPage Schema
How do I generate a complete product architecture with a risk register and systems inventory?

You can generate a complete product architecture by running the arch play, which produces six deterministic architecture artifacts including a refined quality profile, systems inventory, layered logical and physical deployment, tech stack patterns, and a technical risk register.

Can I produce architecture artifacts if my upstream design inputs are partially missing?

Yes, you can produce architecture artifacts with partially missing locked upstream inputs because the workflow applies stage-appropriate interactive fallbacks to capture missing information and ensure all decisions remain grounded.

How do I make sure my logical architecture decisions are traceable and non-invented?

To make architecture decisions traceable, this process enforces that every component selection is inventory-grounded, typed with source manifests, and traces back to upstream artifacts, project-profile pins, or captured user answers.

What is the best way to map NFRs to physical delivery mechanisms in a tech stack?

The best way to map NFRs to physical delivery mechanisms is to refine your quality profile during generation, ensuring every non-functional requirement has a named physical delivery mechanism within the tech stack and industry patterns.

When should I not use an automated architecture generation workflow for my product?

You should not use automated architecture generation if you cannot provide stage-appropriate interactive fallbacks for missing inputs, as the technical risk register is withheld until all prior architecture stages pass validation checks.