agentleFS
albertomartureloalbertomarturelo/sii/.agents/skills/new-decision/SKILL.md

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.

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
  1. Distinctive:

    Ask: "What decision needs to be made?"

    line 11
  2. Very specific:

    Update docs/decisions/_index.md with the new entry (one row).

    line 24
  3. Very specific:

    If the decision affects a recurring convention, also update docs/CONVENTIONS.md (or docs/conventions/sii-wire.md for an SII wire rule, …

    line 29
  4. Distinctive:

    Do NOT skip "Alternatives Considered".

    line 32
  5. Very specific:

    When a rule is ported from the Python sii-cli, cite the source ADR (e.g.

    line 34
  6. Distinctive:

    When the ADR file is written, stop.

    line 39

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Guide the user through documenting a new architectural decision.

  1. Ask: "What decision needs to be made?"
  2. Help articulate the Context: what problem are we solving, what constraints apply, what is the trigger for deciding now.
  3. Propose 2–3 alternatives with explicit pros and cons. Do not short-circuit to your favorite — the user has to choose.
  4. Once chosen, generate a new ADR file at docs/decisions/<NNN>-<slug>.md following docs/decisions/TEMPLATE.md exactly. Increment <NNN> to one above the highest existing.
  5. Update docs/decisions/_index.md with the new entry (one row).

Constraints:

  • The ADR MUST be ≤100 lines.
  • If the decision affects a recurring convention, also update docs/CONVENTIONS.md (or docs/conventions/sii-wire.md for 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 Accepted unless the user explicitly asks for Proposed.

When the ADR file is written, stop. The user reviews it before the implementation that depends on it begins.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.