architecture-review
Skill0 starsChanged 26 days agoMITView on GitHub
Critique an existing technical design or proposed architecture for complexity, interfaces, failure modes, and migration cost. Read-only design review; not an implementation request.
85 other projects use a version of this.
Adopted by
Most recently taken up by
- lx-wnk/skillstheir own version, first seen Nov 16, 2026
- seancabalse/agentic-playbooktheir own version, first seen Nov 16, 2026
- erikperttu/steering-coding-agentstheir own version, first seen Nov 16, 2026
- Sequela02/canastatheir own version, first seen Nov 15, 2026
- OmarAlex24/audit-skillstheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
Used with
Projects with it also use create-stories, story-done and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
lilangMaxSkillstory-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 11 projects that use this
- +10 more from lilangMax
Other versions85 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 85
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- langwatch/langwatch★ 5ksame name
- ghuntley/loom★ 1.7ksame name
- microsoft/hve-core★ 1.6ksame name
- DataDog/dd-trace-js★ 842same name
- decebals/claude-code-java★ 763same name
- borgbase/vykar★ 726same name
- appdevforall/CodeOnTheGo★ 621same name
- owainlewis/blueprint★ 432same name
- getsentry/warden★ 424same name
75 more not listed
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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- acceptance-qaSkill
- bug-fix-verificationSkill
- dependency-upgradeSkill
- docs-syncSkill
- idea-to-scopeSkill
- implementation-planSkill
- independent-reviewSkill
- migration-safetySkill
- performance-investigationSkill
- pull-request-handoffSkill
- release-checkpointSkill
- root-cause-investigationSkill
- security-reviewSkill
- surgical-changeSkill
- test-gap-auditSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 77 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Follow one concrete request or data record through the proposed components.
- Distinctive: line 12
Look for accidental complexity: extra services, frameworks, queues, caches, shared abstractions, duplicated state, and premature …
- Distinctive: line 13
Test the important edges: retries, idempotency, authorization, partial failure, observability, concurrency, schema versions, and recovery.
- Distinctive: line 19
Do not mutate source, schemas, infrastructure, or config.
“Common” is measured: kept by at least 6 in 10 of the 77 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Architecture review
Review decisions, not personalities or diagram aesthetics. This is read-only.
- Establish the proposed change, present architecture, traffic/data assumptions, and decision deadline. Mark unknowns; never invent scale or SLO figures.
- Follow one concrete request or data record through the proposed components. Identify ownership, side effects, dependency boundaries, and how failures surface.
- Look for accidental complexity: extra services, frameworks, queues, caches, shared abstractions, duplicated state, and premature configurability.
- Test the important edges: retries, idempotency, authorization, partial failure, observability, concurrency, schema versions, and recovery. Limit focus to actual risk.
- Compare the proposal against a simpler viable alternative and the status quo. Describe what each option buys and costs.
- Identify decisions that are easy to reverse versus expensive to reverse. Recommend a proof or spike only if it can resolve material uncertainty.
Boundaries
Do not mutate source, schemas, infrastructure, or config. Do not claim performance or security guarantees without measurements or analysis of concrete controls.
Output
Recommendation, what works, blocking risks, simplifications, decisions to defer, missing evidence. Prefer one decision table over an exhaustive catalog of patterns.
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.

