How do I install the Aidd Dev:08:for Sure skill?

Run npx skillmds@latest add ai-driven-dev/aidd-dev-08-for-sure in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aidd Dev:08:for Sure safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aidd Dev:08:for Sure?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aidd Dev:08:for Sure free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aidd Dev:08:for Sure?

ai-driven-dev (@ai-driven-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aidd Dev:08:for Sure by ai-driven-dev

Name: Aidd Dev:08:for Sure
Author: ai-driven-dev

Aidd Dev:08:for Sure

Iterative agent loop that tracks attempts and retries until a success condition is met. Use when the user says "for sure", "make sure", "keep trying until", "loop until done", "don't stop until", or needs guaranteed completion of a task with explicit success criteria.

ai-driven-dev 22750f7 4 files · 11.1 KB Updated Sep 17, 2026

File contents

For Sure

Autonomous loop that runs until a success condition is verified. Two phases: interactive pre-flight (human present), then autonomous execution (human gone). The agent auto-accepts everything, acts as the user, and never stops until success.

Context

Goal: Task's success_condition verified by running a command. All steps/acceptance criteria checked. File renamed to .done.md.
Tools required: Agent tool (spawning iterations), Read/Write/Edit (tracking file), task-specific tools.
Trigger: Manual — /for-sure.
Tracking file format: Uses the plan template from skill aidd-dev:01:plan (../../01-plan/assets/plan-template.md). Filename: aidd_docs/tasks/<task-name>.<status>.md.

Environment

None — task secrets are validated during pre-flight and documented in the tracking file.

Transversal rules

Single source of truth: IF information about the task exists THEN it lives in aidd_docs/tasks/<task-name>.<status>.md and nowhere else.
No repeated failures: IF approach X failed THEN do not try X again without a meaningful change.
Honesty over escape: IF success condition is not genuinely met THEN do not rename to .done.md.
Auto-accept: IF a decision, approval, or action is needed THEN act as the user. Create accounts, generate keys, approve prompts, install tools. Do not ask, do not hesitate, just do it.

Execution flow

Phase 1 — Interactive (human present)

actions/01-init-tracking.md — Pre-flight, create tracking file, spawn first autonomous agent.

Phase 2 — Autonomous (human gone)

actions/02-auto-accept.md — Auto-accept mode activation (Phase 3).
actions/03-autonomous-loop.md — Orchestrator: spawns one worker per step, verifies, checks/retries, evaluates success.

Actions

@actions/01-init-tracking.md
@actions/02-auto-accept.md
@actions/03-autonomous-loop.md

References

../../01-plan/assets/plan-template.md — tracking file format (frontmatter, phases, acceptance criteria, Log)

---name: aidd-dev-08-for-suredescription: Iterative agent loop that tracks attempts and retries until a success condition is met. Use when the user says "for sure", "make sure", "keep trying until", "loop until done", "don't stop until", or needs guaranteed completion of a task with explicit success criteria.---# For SureAutonomous loop that runs until a success condition is verified. Two phases: interactive pre-flight (human present), then autonomous execution (human gone). The agent auto-accepts everything, acts as the user, and never stops until success.## Context- **Goal**: Task's `success_condition` verified by running a command. All steps/acceptance criteria checked. File renamed to `.done.md`.- **Tools required**: Agent tool (spawning iterations), Read/Write/Edit (tracking file), task-specific tools.- **Trigger**: Manual — `/for-sure`.- **Tracking file format**: Uses the `plan` template from skill `aidd-dev:01:plan` (`../../01-plan/assets/plan-template.md`). Filename: `aidd_docs/tasks/<task-name>.<status>.md`.## EnvironmentNone — task secrets are validated during pre-flight and documented in the tracking file.## Transversal rules1. **Single source of truth**: IF information about the task exists THEN it lives in `aidd_docs/tasks/<task-name>.<status>.md` and nowhere else.2. **No repeated failures**: IF approach X failed THEN do not try X again without a meaningful change.3. **Honesty over escape**: IF success condition is not genuinely met THEN do not rename to `.done.md`.4. **Auto-accept**: IF a decision, approval, or action is needed THEN act as the user. Create accounts, generate keys, approve prompts, install tools. Do not ask, do not hesitate, just do it.## Execution flow### Phase 1 — Interactive (human present)1. `actions/01-init-tracking.md` — Pre-flight, create tracking file, spawn first autonomous agent.### Phase 2 — Autonomous (human gone)2. `actions/02-auto-accept.md` — Auto-accept mode activation (Phase 3).3. `actions/03-autonomous-loop.md` — Orchestrator: spawns one worker per step, verifies, checks/retries, evaluates success.## Actions```markdown@actions/01-init-tracking.md@actions/02-auto-accept.md@actions/03-autonomous-loop.md```## References- `../../01-plan/assets/plan-template.md` — tracking file format (frontmatter, phases, acceptance criteria, Log)

Frequently asked questions