agentsclimarketplace

Decision records

Skill batteryshark/skill-tap/skills/productivity/decision-records

Portable, reusable skills for agents and everyday workflows. Clank responsibly.

Install
npx -y skills add batteryshark/skill-tap --skill decision-records

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create, recover, review, or update durable decision records that preserve context, constraints, considered alternatives, chosen direction, consequences, evidence, uncertainty, and reconsideration criteria. Use for architecture decisions, product or operational tradeoffs, design-rationale interviews, superseding stale records, or reconciling documented intent with actual practice.

SKILL.md

2.8 KB, as published. Nobody here has run it

Decision records

Preserve why a consequential choice was reasonable under its constraints. Record the decision without turning inference into historical fact or presenting one option as universally correct.

Choose a mode

  • Create: document a decision being made now.
  • Recover: reconstruct rationale from implementation, history, notes, and informed people.
  • Reconcile: compare a record with current behavior and update, supersede, or flag drift.

Workflow

  1. Identify the decision boundary, affected people or systems, and the durable artifact location. Use an established local convention when one exists.

  2. Gather direct evidence: requirements, implementation, tests, incidents, measurements, prior records, notes, and explicit maintainer statements.

  3. Scaffold a record when useful:

    bin/decision-records --title "Choose the job queue" --output docs/decisions/job-queue.md

  4. Capture context and binding constraints before the choice. Describe serious alternatives fairly, including why they were rejected under those constraints.

  5. State the selected direction, expected benefits, accepted costs, risks, follow-up work, and observable validation.

  6. Separate observed facts, quoted rationale, and inference. Use references/interview-and-reconciliation.md when author context is missing or the record may be stale.

  7. Define concrete reconsideration triggers. Mark a superseded or deprecated record in place and link its successor; do not silently rewrite historical context.

  8. Review the result against references/record-schema.md.

Rules

  • Record consequential choices, not every implementation detail or preference.
  • Keep current project status in the project's tracker or task system; keep durable rationale here.
  • Preserve disagreement and uncertainty when they materially affect future change.
  • Do not manufacture alternatives merely to make the record look complete.
  • Describe consequences as tradeoffs, not promises.
  • Never expose credentials, private personal context, or confidential values in a broadly shared record.

Output

Return the record path or draft, status, evidence basis, confidence limits, confirmation questions, and any follow-up or reconsideration trigger.

Use agents/interviewer.md to recover context and agents/auditor.md to challenge a draft or detect drift.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.