architect-decision-record
Skill2 starsChanged 4 months agoMITView on GitHub
Prepare or review architecture decision notes without adopting ADRs automatically. Use when an architect needs to compare options, recommend a decision, name authority, or ensure a decision note does not become an FCoP protocol change without governance.
In this repository42 other files it gives its agents.
- architect-boundary-reviewSkill
- architect-system-designSkill
- browser-playwright-checkSkill
- browser-useSkill
- code-search-navigationSkill
- controlled-emergence-observerSkill
- dev-code-locationSkill
- dev-small-scope-patchSkill
- dev-test-and-explainSkill
- eval-observation-writingSkill
- eval-promotion-adviceSkill
- eval-risk-gap-analysisSkill
- ops-log-diagnosisSkill
- ops-runtime-healthSkill
- ops-stuck-workflowSkill
- pm-acceptance-criteriaSkill
- pm-architecture-reviewSkill
- pm-delivery-planSkill
- pm-evolve-skillsSkill
- pm-long-horizon-planningSkill
- pm-priority-triageSkill
- pm-product-design-briefSkill
- pm-product-requirementsSkill
- pm-scope-controlSkill
- pm-solve-problemsSkill
- pm-tech-scopeSkill
- qa-regression-checkSkill
- qa-reproduce-issueSkill
- qa-verify-fixSkill
- run-local-command-checkSkill
- test-selectionSkill
- tm-delivery-governanceSkill
- tm-review-routingSkill
- tm-risk-dependencySkill
- ui-information-architectureSkill
- ui-requirementsSkill
- ui-usability-acceptanceSkill
- ui-visual-consistencySkill
- web-extractSkill
- web-researchSkill
- web-searchSkill
- windows-useSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 10
Use this skill when a technical decision needs structure but is not yet an adopted ADR.
- Distinctive: line 17
Keep local CodeFlowMu decisions separate from formal FCoP protocol changes.
- Distinctive: line 25
Do not auto-create or auto-adopt ADRs.
- Very specific: line 26
Do not add adopted-pending 0003.
- Distinctive: line 27
Do not rewrite protocol docs.
- Distinctive: line 28
Do not bypass ADMIN.
≈ “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
Architect Decision Record Review
When to use
Use this skill when a technical decision needs structure but is not yet an adopted ADR.
Rules
- Compare options and risks.
- Name required authority.
- State that the note is not adopted until governance accepts it.
- Keep local CodeFlowMu decisions separate from formal FCoP protocol changes.
Required output
Use docs/skills/architect-playbook/decision-record.md.
Forbidden actions
- Do not auto-create or auto-adopt ADRs.
- Do not add adopted-pending
0003. - Do not rewrite protocol docs.
- Do not bypass ADMIN.
Minimal example
Decision candidate: add playbook catalog
Authority: PM/ADMIN
Non-adoption: this is not an adopted ADRDoes 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.