gaia-edit-arch

Edit architecture documents with cascade-aware impact analysis and ADR preservation.

2|Updated Apr 15, 2026

Search Tags:#architecture #adr #traceability #change-management #cascade-edit #theo

Ready to run

npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-edit-arch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gaia-edit-arch
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-edit-arch
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-edit-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires checkpoint.sh, lifecycle-event.sh, resolve-config.sh, validate-gate.sh, and includes scripts (resource) components.

What problem does it solve?

Edit an existing architecture document with cascade-aware downstream artifact detection, delegating architecture-authoring reasoning to the architect subagent (Theo) — Cluster 6 architecture skill. Use when the user wants to modify sections of an existing architecture while preserving consistency with epics, stories, test plans, and infrastructure design.

Core Features & Use Cases

Cascade-aware edits to docs/planning-artifacts/architecture.md with cascade impact analysis on downstream artifacts (epics, stories, test plans, and infrastructure design).
Coordination with the architect subagent (Theo) for change impact evaluation, ADR logging, and version-history updates.
Strict preservation of unchanged sections, automated ADR auto-increment, and traceability maintenance across edits.

Quick Start

Propose targeted edits to docs/planning-artifacts/architecture.md and trigger the cascade-aware edit flow with Theo.

Frequently Asked Questions about gaia-edit-arch

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

FAQPage Schema

How do I edit an existing architecture document while preserving traceability?▼

To edit an architecture document while preserving traceability, apply scoped cascade-aware edits to architecture.md, which assesses downstream artifacts like epics and test plans for impact and maintains version history.

What is cascade impact analysis in architecture change management?▼

Cascade impact analysis in architecture change management evaluates how modifying sections of an existing system architecture document affects downstream artifacts, ensuring consistency across epics, stories, test plans, and infrastructure design.

How do I log Architecture Decision Records with auto-incremented IDs?▼

You can log Architecture Decision Records with auto-incremented IDs by triggering the architect subagent Theo during the architecture edit flow, which records ADRs and updates the version history automatically.

Does editing architecture.md affect downstream infrastructure design and test plans?▼

Yes, editing architecture.md affects downstream artifacts because the process assesses epics, stories, test plans, and infrastructure design for cascading impact to ensure strict consistency across the planning artifacts.

What are the setup gates required before modifying a system architecture document?▼

Before modifying a system architecture document, setup gates are enforced through validation scripts like checkpoint.sh and validate-gate.sh, ensuring the environment is correctly configured before loading the architecture for editing.

Can I update specific sections of architecture.md without altering unchanged parts?▼

Yes, you can update specific sections of architecture.md without altering unchanged parts, as the cascade-aware edit flow enforces strict preservation of unchanged sections while applying targeted modifications.