write-architecture
Skill0 starsChanged 16 days agoMITView on GitHub
Write a system architecture document — boundaries, data, control flow, and quality attributes. Use when the user asks for architecture, system design of the durable shape, or /write-architecture. Do not write product code. Do not architecture a local rename.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- rpraharaj/ai-engineeredited, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- rpraharaj/ai-engineer★ 128% same
Wrote their own version · 0
None found.
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 repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- a11y-passSkill
- assess-changeSkill
- build-regression-packSkill
- charter-exploratorySkill
- classify-dataSkill
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- design-experimentSkill
- diff-environmentsSkill
- draft-steercoSkill
- engineering-barSkill
- explain-codeSkill
- explore-codebaseSkill
- fix-ciSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- map-dependenciesSkill
- map-design-handoffSkill
- map-processSkill
- open-prSkill
- performanceSkill
- plan-data-migrationSkill
- plan-incrementSkill
- plan-rollbackSkill
- plan-uatSkill
- prioritize-backlogSkill
- production-passSkill
- ready-to-mergeSkill
- record-decisionSkill
- refactor-safelySkill
- revert-changeSkill
- review-architectureSkill
- review-changeSkill
- review-pipelineSkill
- security-passSkill
- shape-workSkill
- ship-notesSkill
- spec-analyticsSkill
- spec-observabilitySkill
- start-projectSkill
- synthesize-discoverySkill
- triage-blockersSkill
- triage-defectSkill
- update-raidSkill
- verify-uiSkill
- write-api-examplesSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-integration-contractSkill
- write-nfrSkill
- write-opportunitySkill
- write-prdSkill
- write-requirementsSkill
- write-runbookSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 19
Do not implement. Do not invent services, stores, or SLOs this product does not have.
- Very specific: line 32
If the ask is a single feature inside a settled system, say so and offer write-design.
- Distinctive: line 46
Read AGENTS.md. Map current apps, packages, stores from the tree.
≈ “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
Write architecture
Describe the durable shape. This is not a PRD, not write-design, and not record-decision.
Do not implement. Do not invent services, stores, or SLOs this product does not have.
Is this the right skill?
| Signal | Do this instead |
| What / why for users | write-prd |
| How this feature will be built | write-design |
| One sticky choice | record-decision |
| One implementable slice | shape-work |
| Local rename | stop — no architecture doc |
| Review an existing architecture file | review-architecture |
If the ask is a single feature inside a settled system, say so and offer write-design.
Required inputs
AGENTS.md. If the repo is unmapped, runexplore-codebaseor say the picture is incomplete.- Existing apps/packages you can name, or an explicit greenfield
Human decisions (do not invent)
- Quality targets not already in the repo or set by the user
- Irreversible vendor/store picks (draft options;
record-decisionafter they choose)
Procedure
- Read
AGENTS.md. Map current apps, packages, stores from the tree. - Find the home: first existing
docs/architecture/,docs/arch/,architecture/, or a pathAGENTS.mdnames. Name:docs/architecture/<area>.md. - Open references/architecture-template.md. Copy every heading. Write
n/awhen unused. - Boundaries are things that can fail or deploy apart. Quality attributes use numbers this repo has or user-set targets — else
unknown/n/a. Alternatives include keep-current when a system exists. - Point sticky choices at
record-decision.
Output
- Path:
docs/architecture/<area>.md - Template:
references/architecture-template.md
Quality bar
- A new engineer could name where a request enters and where data lives
- Proposed shape is smaller than a platform rewrite unless asked
- Unused sections are
n/a - No secrets, no invented vendors
Done
- Path or full text
- Proposed shape in a few sentences
- Which ADRs should follow (or none)
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.