architecture-change
Skill4 starsChanged 12 days agoMITView on GitHub
Architecture change workflow with mandatory ADR and controlled rollout. Use when proposing or implementing a structural/architectural change to the codebase.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- accnet/claude-skilltheir own version, first seen Aug 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- accnet/claude-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- brainstormingSkill
- doc-auditSkill
- feature-deliverySkill
- find-skillsSkill
- frontend-designSkill
- hotfixSkill
- jules-tasksSkill
- qa-auditSkill
- release-readinessSkill
- requesting-code-reviewSkill
- setup-repoSkill
- skill-creatorSkill
- systematic-debuggingSkill
- using-superpowersSkill
- writing-plansSkill
- architecture-changeSkill
- brainstormingSkill
- doc-auditSkill
- feature-deliverySkill
- find-skillsSkill
- frontend-designSkill
- hotfixSkill
- jules-tasksSkill
- qa-auditSkill
- release-readinessSkill
- requesting-code-reviewSkill
- setup-repoSkill
- skill-creatorSkill
- systematic-debuggingSkill
- using-superpowersSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Write architecture proposal with options/trade-offs.
- Very specific: line 13
Create/update ADR file in docs/decisions/ before finalizing.
- Distinctive: line 16
Run pre-commit checks before final handoff.
- Distinctive: line 19
No architecture-level change may be closed without ADR entry.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Architecture Change
Follow .agent/workflows/architecture-change.md strictly.
Execution requirements:
- Write architecture proposal with options/trade-offs.
- Create/update ADR file in
docs/decisions/before finalizing. - Implement in isolated steps and validate regressions.
- Sync architecture-relevant docs and
CHANGELOG.md. - Run pre-commit checks before final handoff.
- End with ADR + DoD confirmation.
No architecture-level change may be closed without ADR entry.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

