skills/decide/SKILL.md
3-line ADR lite. Capture a decision you just made in under 60 seconds — problem, choice, rejected alternative. Complements the heavier `adr` skill; use this when a full ADR is overkill but the decision will be forgotten.
npx skillsauth add the-own-lab/Claude-company-of-one decideInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
For decisions that are too small for a full ADR but too important to forget.
Problem: <one sentence>
Chose: <what you picked, and why>
Rejected: <one alternative, and why not>
That's it. No sections. No heavy template.
adr| Use decide | Use adr |
| --------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| Decided in < 30 min | Decided after a design doc |
| Impact scoped to a file or module | Impact on architecture / public API |
| Won't need to re-litigate unless context changes | May be revisited quarterly |
| Example: "chose pg trigram over elasticsearch for search — ES is too heavy for 5k rows" | Example: "chose Electron over Tauri for desktop app" |
Append to ${COMPANY_OF_ONE_PLUGIN_DATA}/decisions.md with a date prefix:
## 2026-04-20 — Search backend
Problem: Need fuzzy search over project notes (5k rows).
Chose: Postgres pg_trgm. Already have pg; zero new infra.
Rejected: Elasticsearch — operational overhead unjustified at this scale.
One file, append-only. Grep-friendly.
decide entries into mini-essays — if it's getting long, you need an ADRdecide for things you haven't actually decided ("maybe X, maybe Y, TBD") — that's an open question, not a decisionGoogle's decision-log culture at scale becomes heavy. At solo-dev scale, the friction is the enemy: a format you won't fill in doesn't exist. Three lines you'll actually write beats a template you won't.
documentation
Update BRIEF.md sections during a command run. Any skill that produces a brief-persisted artifact calls this to write it back.
development
Post-code check: run tests + confirm TODO acceptance items map to passing tests; applies a security lens but is not a separate scan.
documentation
Command post-step: write CHANGELOG + TODO once per command run. One call, not per-skill doc writes.
content-media
Author REQUIREMENTS.md + DESIGN.md + TODO.md for a feature. The three files are one contract; they ship together.