Skip to content

v0.9.2 — add four AI-adoption skills (RFC-0023) and release 0.9.2

Choose a tag to compare

@sananthanarayan sananthanarayan released this 14 Aug 23:42
· 9 commits to main since this release

The ai-engineering pack was strong on building AI systems (agent-loop-design,
subagent-design, agent-budget, agent-threat-model, llm-eval-harness) and on measuring
usage after the fact (ai-usage-report), but had nothing for the stage before any of
that — deciding whether, where and how to adopt at all. Four artifacts no existing
skill produces:

  • ai-readiness-assessment — six fixed dimensions scored 0-4, each with an evidence
    line or [insufficient evidence]; gaps ranked by what blocks first, not by lowest
    score; a posture sentence that takes a position.
  • ai-use-case-triage — value x feasibility x risk with the weights shown; candidates
    restated as a workflow and a person; a first slice with an observable kill condition;
    a mandatory not-yet list where each rejection carries its promotion condition.
  • ai-adoption-rollout — the human counterpart to migration-plan: cohorts smallest
    first, per-cohort enablement, champions with protected hours, an adoption gate per
    wave (observable + threshold + bake time + rollback), and a comms plan that must
    state what will NOT change about headcount and evaluation.
  • ai-usage-policy — three data tiers with examples from the org, prohibitions that
    always name a permitted alternative, a review matrix keyed to consequence rather
    than to model names, and an exception route with a turnaround time.

All standard tier, all in ai-engineering (triage also in product-manager), each with
evals whose no-trigger rows point at the siblings they collide with. Registered in
model-routing.json, packs.json and the README (51 -> 55).

Declined: a fifth AI-ROI skill. It fails the fit check's own duplication test —
business-case prices the investment, success-metrics defines the measure and decision
rule, ai-usage-report reports actual usage. A wrapper over those three would be filler.
Recorded in RFC-0023 so the idea leaves a trace.

The og.svg and README count guards both caught the stale 51 — og.png re-rendered.


npx skilldrop-cli@0.9.2 install --pack solution-architect

skilldrop-cli@0.9.2 on npm