new-decision
Skill19 starsChanged 7 days agoMITView on GitHub
Guide the user through documenting a new architectural decision as an ADR (≤100 lines) with real alternatives, then update docs/decisions/_index.md. Use when a significant decision surfaces without an ADR: a new dependency, a moved layer boundary, a choice between plausible patterns, or a new surface verb.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cfd-upgradeSkill
- issue-newSkill
- issue-startSkill
- review-prSkill
- run-siiSkill
- session-closeSkill
- session-startSkill
- telemetry-reportSkill
- validate-contextSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Ask: "What decision needs to be made?"
- Very specific: line 24
Update docs/decisions/_index.md with the new entry (one row).
- Very specific: line 29
If the decision affects a recurring convention, also update docs/CONVENTIONS.md (or docs/conventions/sii-wire.md for an SII wire rule, …
- Distinctive: line 32
Do NOT skip "Alternatives Considered".
- Very specific: line 34
When a rule is ported from the Python sii-cli, cite the source ADR (e.g.
- Distinctive: line 39
When the ADR file is written, stop.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Guide the user through documenting a new architectural decision.
- Ask: "What decision needs to be made?"
- Help articulate the Context: what problem are we solving, what constraints apply, what is the trigger for deciding now.
- Propose 2–3 alternatives with explicit pros and cons. Do not short-circuit to your favorite — the user has to choose.
- Once chosen, generate a new ADR file at
docs/decisions/<NNN>-<slug>.mdfollowingdocs/decisions/TEMPLATE.mdexactly. Increment<NNN>to one above the highest existing. - Update
docs/decisions/_index.mdwith the new entry (one row).
Constraints:
- The ADR MUST be ≤100 lines.
- If the decision affects a recurring convention, also update
docs/CONVENTIONS.md(ordocs/conventions/sii-wire.mdfor an SII wire rule, ADR-033) and reference the new ADR there. - Do NOT skip "Alternatives Considered". Future sessions need to know why the rejected paths were rejected, or they'll re-litigate.
- When a rule is ported from the Python
sii-cli, cite the source ADR (e.g. "lineage: sii-py ADR-019") rather than re-deriving it. - Status starts as
Acceptedunless the user explicitly asks forProposed.
When the ADR file is written, stop. The user reviews it before the implementation that depends on it begins.
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.

