Skip to content
All skillsPlan

Workflow skill

Architecture Decision Log

draft, under review3 phases1 bundled files

Write down the decision, what it beat, and why, in the same place the handbook already keeps its own hard calls, so the reasoning survives past the conversation that produced it.

Install
/plugin marketplace add Selwynuy/selwynuy
/plugin install selwyn-handbook@selwyn-handbook
# then run: /selwyn-handbook:architecture-decision-log

Or read it as SKILL.md.

When it activates

Use this skill when choosing between real alternatives on architecture, data, or API design and the reasoning is worth keeping.

The workflow

  1. Detect

    Notice the decision moment: a stated conclusion after comparing alternatives, not a trivial or purely stylistic choice.

    decisions

  2. Record

    Write the decision, the alternatives considered with why each lost, and the consequences (including the real trade-offs, not just the upside), in the handbook's Decisions format.

    decisionsnextjs-fit-check

  3. Tag

    Mark how firm the call is (non-negotiable, strong default, or opinion still under review) so a future reader knows how hard to hold the line.

    decisions

What ships in the bundle

  • referencereferences/decision-entry-schema.mdThe fields a decision entry needs: the call, what it beat and why, consequences, and its firmness tag.

0 run, the rest load on demand.