09-for-sure — Claude Code skill: what it does, how to install
The 09-for-sure skill runs an agent through repeated attempts until a runnable success check passes. Use it for work with a result that can be verified, such as a command.
MIT ★ 571 updated 2026-10-29
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-dev@aidd-frameworkWhat 09-for-sure does
The skill starts by checking the goal, mapping the steps, creating a tracking file, and launching an autonomous loop. The loop assigns a worker agent to each step, checks the outcome, and retries when needed. Task state stays in aidd_docs/tasks/<task-name>.md.
A retry must change the approach; repeating a failed attempt unchanged is not allowed. The skill makes decisions as the user when approval is needed, but stops before payment or destructive actions. The goal needs an executable success check. This loop is not suited to work with no verifiable finish condition.
What it helps with
- break a task into steps and track progress
- retry agent work until a runnable check passes
- assign a separate worker to each step
- keep a task unimplemented until its success condition passes
Example prompts for the agent
- Keep working on this task until
npm testpasses. - Retry the build until
npm run buildcompletes successfully. - Plan and carry out the steps autonomously until the stated check passes.
How to install 09-for-sure
1Plugin marketplace
/plugin marketplace add ai-driven-dev/framework/plugin install aidd-dev@aidd-frameworkThis installs the whole aidd-dev plugin with all its skills
2Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 09-for-sure -a claude-code3Manually: put the files in place
~/.claude/skills/09-for-sure/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/09-for-sure/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 09-for-sure -a codex2Manually: put the files in place
.agents/skills/09-for-sure/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 09-for-sure -a cursor2Manually: put the files in place
.cursor/skills/09-for-sure/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework plugins/aidd-dev/skills/09-for-sure2Manually: put the files in place
.github/skills/09-for-sure/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 09-for-sure -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path plugins/aidd-dev/skills/09-for-sureManually: put the files in place
.devin/skills/09-for-sure/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 09-for-sure -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 09-for-sure
How do I install 09-for-sure in Claude Code?
Add the marketplace with /plugin marketplace add ai-driven-dev/framework, then install the skill with /plugin install aidd-dev@aidd-framework.
What does 09-for-sure do?
It sets up an autonomous task loop that assigns a worker to each step and checks the success condition. The loop retries until that condition passes.
When is 09-for-sure unsuitable?
The goal needs a runnable way to verify success. It is not intended for one-off tasks or outcomes that cannot be checked.
Source text
SKILL.md · MIT
--- name: 09-for-sure description: Run an iterative agent loop that retries until a runnable success condition passes. Use when the user says "for sure", "keep trying until", or wants guaranteed completion against a success command. Not for one-shot tasks or uncheckable goals. argument-hint: task | command --- # Skill: for-sure Run an autonomous loop until a success condition is verified. An interactive pre-flight (human present) sets it up, then autonomous execution (human gone) retries until success, acting as the user and never stopping early. ## Actions | # | Action | Phase | Role | | --- | ----------------- | ---------------------- | -------------------------------------------------------------------------- | | 01 | `init-tracking` | interactive pre-flight | validate the goal, build the journey map, create the tracking file, spawn the loop | | 02 | `auto-accept` | autonomous | decide and act as the user, stopping only on money or destructive actions | | 03 | `autonomous-loop` | autonomous | spawn one worker per step, verify, retry, evaluate the success condition | Run `01` interactively; it spawns `03`, which runs unattended under the `02` auto-accept rules until the success condition passes. Before running an action, read its file in `actions/`, not only the table or assets. ## Transversal rules - Single source of truth: all task state lives in `aidd_docs/tasks/<task-name>.md` and nowhere else. - No repeated failures: never retry a failed approach without a meaningful change. - Honesty over escape: never set `status: implemented` until the success condition genuinely passes. - Auto-accept: when a decision or approval is needed, act as the user (create accounts, generate keys, approve prompts, install tools), never asking. Stop only on a payment or a destructive action. - The loop spawns one worker agent per step and never does the work itself. ## Assets - `assets/plan-template.md`: the tracking file format (frontmatter, phases, acceptance criteria, Log). - `assets/autonomous-loop-worker-prompt.md`: the prompt the loop spawns each per-step worker with. ## References - `references/autonomous-loop-log-format.md`: the Log entry format the loop appends per attempt.
© AI-Driven Dev · MIT · ai-driven-dev/framework