AI agent skill · by @vanillagreencom

Decider

Load to create, search, or supersede an architecture decision record.

Archived 2026-10-23 · Source updated 2026-09-18 · License: MIT. Check the original repository for the latest version.

SKILL.md instructions

# Decider

Numbered decision documents indexed in one `INDEX.md` (default `docs/decisions/`), with a search CLI, canonical format, and creation/supersession workflows.

```bash
.agents/skills/decider/scripts/decisions <command> [options]
```

Actions (`search`, `search --issue`, `list`, `next-id`, `get`), search coverage and scoring, output shapes, and the `DECISIONS_DIR` / `DECISION_ID_*` environment: `decisions --help`. There is no bare `issue` action; use `search --issue`.

Read the full decision file before acting on a hit. A suggestion contradicting an active decision is invalid unless the decision itself is flawed.

## Workflows

| Workflow | Trigger |
|----------|---------|
| `workflows/create-decision.md` | A significant path choice is settled |
| `workflows/update-decision.md` | A new decision supersedes, partially supersedes, or revisits an existing one |

Format: `schemas/decision-format.md` (constraints), `templates/decision-entry.md` (document skeleton), `templates/index-row.md` (INDEX row).

## Approval

Never create a decision document without explicit user approval. When work settles a choice worth recording, say on completion: "this introduced a decision worth recording: [summary]. Want me to create a decision entry?"

Record: technology selections with alternatives, performance trade-offs, path choices whose conditions may change. Do not record: variable names, small refactors, bug fixes, choices with no realistic alternative, standard pattern applications.