메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.
| 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 | init-tracking | auto-accept | autonomous-loop |
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.
| # | 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.
aidd_docs/tasks/<task-name>.md and nowhere else.status: implemented until the success condition genuinely passes.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/autonomous-loop-log-format.md: the Log entry format the loop appends per attempt.