Skip to content

ericrisco/rsc-harness / skills/decision-records

decision-records

Verified

Use when a hard-to-reverse choice (database, framework, vendor, auth model) must be frozen as an immutable numbered ADR — the context that forced it, the options weighed, the decision, consequences both ways — or superseded without erasing history. NOT a meeting recap (that is meeting-notes), NOT standing project principles (that is constitution).

FileKindSize
SKILL.mdskill md11.6 KB
evals/README.mdmarkdown904 B
evals/cases.yamlconfig3.3 KB
references/templates.mdmarkdown8.0 KB
scripts/verify.shexecutablescript3.3 KB

evals/cases.yaml

View on GitHub
skill: decision-records

should_trigger:
  - prompt: "We just picked Postgres over DynamoDB — write it up so we don't argue about it again."
    why: "Classic ADR: a consequential, hard-to-reverse store choice that needs its rationale and alternatives frozen."
  - prompt: "Freeze the rationale for choosing Remix instead of Next before everyone forgets why we did it."
    why: Non-obvious phrasing ("freeze the rationale", "before everyone forgets") for the durable why-capture this skill owns.
  - prompt: "We're dropping REST for tRPC; record the change but keep the old decision in history."
    why: Supersession path — new ADR plus immutable old one, the core lifecycle this skill enforces.
  - prompt: "Documenta por qué elegimos Hetzner y qué alternativas descartamos, con sus pros y contras."
    why: Spanish phrasing asking for decision + rejected options with pros/cons — exactly the ADR structure.
  - prompt: "Every new hire re-asks why we use a monorepo; capture the decision once with the trade-offs."
    why: Onboarding re-litigation of a settled choice; the cure is a single durable record, not a wiki page.
  - prompt: "Registra la decisió d'usar Clerk en comptes de muntar auth nosaltres, amb les opcions que vam valorar."
    why: Catalan build-vs-buy auth decision with weighed options — a bounded, costly-to-reverse choice.

should_not_trigger:
  - prompt: "Summarize today's architecture call and list the action items with owners and due dates."
    route_to: meeting-notes
    why: A point-in-time session recap with tasks/owners, not a durable single-decision artifact.
  - prompt: "Write a step-by-step procedure for how we cut a release."
    route_to: sop-builder
    why: A repeatable how-to-every-time process, not a one-time why-we-chose-X record.
  - prompt: "Define our project-wide coding standards and the canonical stack everyone must use."
    route_to: constitution
    why: Standing non-negotiable principles run once and amended, not one bounded decision.
  - prompt: "Write the implementation plan for the new billing feature."
    route_to: plan
    why: Describes how to build the thing, not the decision behind a fork.
  - prompt: "Draft the feature spec for the new export tool with user stories."
    route_to: specify
    why: Defines what to build, not the rationale for a settled architectural choice.

capability:
  - scenario: "Choosing between Stripe and Lemon Squeezy for billing. Team of 2, EU customers, need invoicing and EU VAT handling. Produce the decision record and wire it into the log."
    must_include:
      - A numbered, dated ADR file (e.g. docs/adr/0003-choose-billing-provider.md) with a recognized status (proposed/accepted/...).
      - Context stated as problem + constraints (team of 2, EU customers, invoicing, VAT), not the answer.
      - At least 2 real options (Stripe, Lemon Squeezy) scored against the same drivers with pros/cons.
      - An explicit Decision Outcome naming the chosen option and the dominant driver.
      - Consequences in both directions — gains plus costs/risks/follow-ups, not only upside.
      - An index/log row added for the new ADR (id, title, status, date).
      - If a prior billing decision is being replaced, correct supersession (new ADR + old status flipped to "superseded by", back-linked) rather than an in-place edit.
deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall