ai-done

Validates AI feature readiness through a five-layer calibration bar covering evals, triage, rollback, and post-ship loops.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/joydai2026-del/skills --skill ai-done-joydai2026-del
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-done
Source: https://github.com/joydai2026-del/skills/tree/main/ai-done
Command: npx skills add https://github.com/joydai2026-del/skills --skill ai-done-joydai2026-del

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Probabilistic AI and LLM features cannot be declared done with a simple "all tests pass" checklist, because the same prompt produces varying outputs across users, sessions, and model updates. This Skill defines a five-layer definition of done so teams know exactly when an AI feature is calibrated and safe to ship. ## Core Features & Use Cases - Five-layer done bar: Checks deterministic floor, distributional quality bands, failure-triage playbook, tripwires with rehearsed rollback, and a post-ship eval loop, refusing to report done on a partial bar. - Thin orchestration: Delegates deterministic checklists to /success-criteria and eval suites to /eval-harness instead of duplicating them, then fills the three gaps neither covers. - Calibration doc generation: Emits a one-page per-feature calibration document from a template, with deterministic path selection and a green/red readiness summary. - Use Case: Before shipping an LLM-powered support chatbot, run this Skill to confirm eval bands pass, a kill switch has been rehearsed with real evidence, and production outputs feed back into the eval suite. ## Quick Start Ask the agent to run the ai-done readiness check on your AI feature to verify all five layers are green before shipping.

Frequently Asked Questions about ai-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I know when an LLM feature is ready to ship?▼

An LLM feature is ready when five layers are green: deterministic checks pass, eval quality bands meet baseline, a failure-triage playbook exists, tripwires and a rehearsed rollback are in place, and a post-ship eval loop samples production outputs.

What is a definition of done for AI features?▼

It is a calibration bar rather than a checkbox: acceptable output variance defined as ranges, planned failure responses, a tested kill switch, and monitoring that keeps learning after launch. Passing unit tests alone covers only the deterministic layer.

Should I use this for deterministic features like auth or billing?▼

No. The scope gate in Step 0 bounces purely deterministic features such as CRUD, auth, billing, and navigation to /success-criteria plus the standard QA bar. This Skill only adds value when a probabilistic surface exists.

Does the rollback rehearsal require real evidence?▼

Yes. The rollback must actually be run once in staging or a controlled production drill, with a concrete artifact such as command output, a log line, or a screenshot path. A prose claim like "flipped the flag, it worked" marks the layer red.

How does this work for a solo developer or small team?▼

Owner cells record pre-decided actions and escalation triggers instead of names, alarm destinations can be a Telegram, Slack, or email webhook, and the review cadence is pinned to a specific day and sample size so the plan is a commitment rather than improvisation.