agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/record-decision/SKILL.md

record-decision

Skill0 starsChanged 17 days agoMITView on GitHub

Capture a sticky technical decision as a one-page ADR — context, options, choice, consequences. Use when the user asks to record a decision, write an ADR, or lock a library, shape, or approach. Do not start a full design document.

10 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use verify.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    verify

    End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write a short ADR. This is not write-design, not write-architecture, and not write-prd.

    line 17
  2. Distinctive:

    Write when the choice is expensive to reverse.

    line 29
  3. Distinctive:

    Read AGENTS.md. Link files/symbols you actually opened.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

Record decision

Write a short ADR. This is not write-design, not write-architecture, and not write-prd.

Is this the right skill?

SignalDo this instead
README / API / runbookwrite-docs
What / whywrite-prd
Durable system shapewrite-architecture
How this initiative is builtwrite-design
Local rename / one-line fixstop — no ADR

Write when the choice is expensive to reverse. If the decision is not made, list options and ask. Do not pick when options trade product risk.

Required inputs

  • The choice (or the options) and why it came up
  • AGENTS.md

Human decisions (do not invent)

  • Which option wins when they trade product risk

Procedure

  1. Read AGENTS.md. Link files/symbols you actually opened.
  2. Find the home: first docs/adr/, doc/adr/, adr/, docs/decisions/, or a path AGENTS.md names. Number like existing ADRs; else 0001-<slug>.md.
  3. Open references/adr-template.md. Copy every heading. Write n/a when unused.
  4. Options include “do nothing.” At least two. Decision is one option. If the user already chose, quote them. Keep status proposed until the authorized human decision and exact artifact revision are evidenced in the approval home named by context/decision-rights.md. Missing evidence → stop before claiming the choice is accepted. this session may describe an author, never the human decider. Changed options or consequences require affected approval again.
  5. No secrets.

Output

  • Path: docs/adr/NNNN-<slug>.md
  • Template: references/adr-template.md

Quality bar

  • At least two options including do-nothing or keep-current
  • Decision is one option
  • Consequences include what you give up and when to revisit
  • Unused headings are n/a
  • Accepted status has revision-bound human approval evidence; otherwise the decision remains proposed

Done

  1. Path or full text
  2. Decision in one sentence
  3. Next: data-change / implement-change / write-docs / write-design or stop

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.

Check your setup, free