Notes

Adopt, adapt, skip

Read as
working implementation · tests
Build treatmentUpdated 14 Jul 2026

Agent systems · Capability curation

What you will leave with

Build a decision matrix that prevents redundant advice from displacing stronger controls.

For engineers conducting an evidence-backed review of an external skill library.~3 min read
PrerequisitesCandidate skill libraryInventory of current procedures and gatesOwners for affected workflows
01 · System view

What you will build

One traceable decision record per candidate, backed by control evidence and a revisit trigger.

  1. 01Extract outcomeWhat behaviour or failure does the candidate address?
  2. 02Map coverageExisting skill, gate, owner, and performance.
  3. 03Compare assuranceAdvice, detection, prevention, and recovery are not equivalent.
  4. 04DecideAdopt, adapt, skip, or defer with a reason.
  5. 05RevisitName the control or condition that would change the decision.
02 · Implementation

Build it in sequence

01

Inventory the current system first

List procedures, enforced gates, risk policies, recurring failures, and explicit gaps. A library cannot improve a system you have not described.

02

Normalize each candidate to an outcome

Ignore branding and prose quality. Write the defect prevented, judgment supported, evidence produced, and capability required in one row.

skill-review.ymlyaml
- candidate: code-simplification
  outcome: prevent new duplication
  current: duplication ratchet blocks increases in CI
  assurance: enforced
  decision: skip
- candidate: architecture-decisions
  outcome: record options, decision, and consequences
  current: decisions remain in chat
  assurance: absent
  decision: adopt
03

Compare assurance, not wording

Rank current and candidate mechanisms: reminder, procedure, detector, required gate, or capability boundary. Never replace prevention with advice because the advice reads well.

04

Adapt around the house-specific control

Keep useful sequencing, failure heuristics, or templates while calling the actual merge, permission, test, or observability controls your system uses.

05

Record the decision and revisit trigger

Store owner, reason, evidence, version, and the condition that would reopen the choice. “Skip” is a current architecture decision, not a permanent dismissal.

03 · Review

Definition of done

  • Every candidate maps to a concrete outcome or failure.
  • Existing coverage includes its assurance level and evidence.
  • No gate is downgraded to behavioural advice.
  • Adapted skills call real house controls.
  • Decisions have owners, reasons, and revisit triggers.
04 · Failure modes

What breaks and what it means

Everything looks useful enough to adopt.

Evaluate marginal capability after current controls, not standalone quality.

The review becomes subjective preference.

Require current evidence, assurance comparison, risk, cost, and a falsifiable revisit condition.

Public discussion

Questions, corrections, and useful disagreement

Moderated on GitHub ↗

Sign in with GitHub to join the conversation. Comments are public. Article views are anonymous and counted once per browser, per article, each day.

Read next10

The reviewer rejected my fix twice. Both times it was right.

Why passing tests and a good staging walk did not prove a data-dependent release was safe, and how an independent reviewer found two temporal bugs.

4 min read