---

name: c3-alter description: | This skill should be used when the user asks to "add a component", "change architecture", "refactor X", "implement feature", "fix bug", "create new service", "update diagram", or "remove component". Requires .c3/ to exist. All changes flow through ADR process. For questions, route to c3-query instead.

C3 Alter - Change Through ADR

Every change flows through an ADR. No exceptions.

REQUIRED: Load References First

1. ../../references/skill-harness.md - Routing and red flags
2. ../../references/layer-navigation.md - How to traverse C3 docs

Core Loop (All Stages)

CopyANALYZE → ASK (until confident) → SYNTHESIZE → REVIEW
              │                        │
              └── until no open ───────┘
                  questions

On conflict: ASCEND → fix earlier stage → re-descend

Confident = No open questions. Don't proceed with "TODO" or unclear fields.

---

Stage 1: Intent

---

Stage 2: Current State

---

Stage 3: Scope Impact

---

Stage 4: Create ADR

Generate at .c3/adr/adr-YYYYMMDD-{slug}.md. Use ../../references/adr-template.md.

Key sections: Problem, Decision, Rationale, Affected Layers, References Affected, Verification

---

Stage 5: Create Plan

Generate at .c3/adr/adr-YYYYMMDD-{slug}.plan.md.

Include:

• Pre-execution checklist (update ## References in affected components)
• Ordered steps: docs first, then code, then diagrams
• Verification commands

---

Stage 6: Execute

Follow plan order:

1. Make change (doc or code)
2. Check for conflicts
3. Update ## References if code moved/added/removed

On conflict - Tiered response:

Ref Maintenance

If change affects a pattern:

1. Check if ref-* exists for pattern
2. Update ref if pattern changes
3. Create new ref if pattern is new and reusable

---

Stage 7: Verify

Run /c3 audit. Check diagrams, IDs, linkages, code-doc match.

---

Response Format

Copy**Stage N: {Name}**
{findings}
**Open Questions:** {list or "None - confident"}
**Next:** {what happens next}