c3-alter_skill

Overview

This skill implements an ADR-first, staged workflow to make architectural changes in a C3 repository. It requires a .c3/ directory and ensures every change flows through a validated ADR, then immediate planning and execution once the ADR is accepted. Use the skill directly for inline alterations or let the c3-orchestrator agent dispatch it when running via a Task tool.

How this skill works

The skill runs a seven-stage loop: clarify intent, document current state, assess scope, create an ADR, get ADR acceptance, create and execute a plan, then verify with /c3 audit. At each stage it analyzes files, asks targeted questions until confident, synthesizes results, and reviews with the user. If provisioned components are detected in .c3/provisioned, the skill prompts whether to implement from that design and handles promotion or superseding accordingly. For unknowns, it routes human-facing questions to c3-query.

When to use it

• Add a new component or service to the architecture
• Change architecture, refactor a component, or implement a new feature
• Fix a bug that requires design-level changes
• Update diagrams, container READMEs, or component docs
• Remove or replace an existing component and assess impact

Best practices

• Ensure .c3/ exists and repository C3 docs are up to date before starting
• Answer the skill's clarifying questions fully—do not proceed with TODO fields
• Prefer using provisioned designs when appropriate; promote them per the workflow
• Create refs for reusable patterns and include concrete code references for Foundation/Feature components
• Accept ADRs only when you are ready for immediate execution; the skill continues automatically after acceptance

Example use cases

• Add rate limiting middleware: produce ADR, create component doc, implement middleware, update container README, run /c3 audit
• Fix login timeout bug: record current behavior, generate concise ADR, accept and patch code, verify links and docs
• Refactor auth chain: assess impacted c3 IDs, detect breaking changes, create plan with ordered steps and rollbacks
• Promote a provisioned component into active implementation and update frontmatter and code references