architecture

Organize durable architectural decisions and system design context across components.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/xiongxianfei/rigorloop --skill architecture-xiongxianfei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/xiongxianfei/rigorloop/tree/main/.codex/skills/architecture
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill architecture-xiongxianfei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Create or update the technical architecture/design artifact after the spec is stable and before execution planning. Use when a change touches multiple components, data flow, persistence, APIs, deployment, performance, or long-lived design decisions.

Core Features & Use Cases

The architecture artifact explains how the repository or system is shaped to satisfy the spec. It should expose structure, runtime flow, deployment impact, cross-cutting rules, quality concerns, risks, and durable decisions without becoming an execution task list. Canonical current architecture lives at docs/architecture/system/architecture.md and related diagrams at docs/architecture/system/diagrams/context.mmd and container.mmd. Change-local deltas live at docs/changes/<change-id>/architecture.md and docs/changes/<change-id>/diagrams/. Update ADRs under docs/adr/ when durable decisions are introduced.

Quick Start

Run the architecture workflow to update the canonical architecture package and create the corresponding diagrams and ADRs.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document system design decisions for changes spanning multiple components?

Document system design decisions by organizing durable architectural context, cross-cutting rules, and risk mitigation into canonical architecture packages, ensuring traceable design decisions across multiple components.

What is the best way to create architecture diagrams and ADRs for a new deployment?

Create architecture diagrams and ADRs by running an architecture workflow that updates canonical context and container diagrams, capturing durable deployment decisions under a dedicated ADR directory for traceability.

When do I need to update my architecture documentation during a project?

Update architecture documentation after the spec is stable and before execution planning, specifically when a change touches data flow, persistence, APIs, deployment, performance, or long-lived design decisions.

Does this architecture workflow support tracking change-local deltas separately from canonical docs?

Yes, the architecture workflow tracks change-local deltas separately by maintaining change-specific architecture and diagram files alongside the canonical architecture package, ensuring traceable design updates.

How do I structure architectural artifacts without creating an execution task list?

Structure architectural artifacts by exposing system structure, runtime flow, deployment impact, cross-cutting rules, and quality concerns as durable design decisions, deliberately avoiding execution task list formatting.