agentleFS
Sign inStart free
timursafiullintimursafiullin/aod/skills/delegate/SKILL.md

delegate

Skill0 starsChanged 29 days agoApache-2.0View on GitHub

Delegate a ready AOD task packet to a Codex implementer in a worktree slot, running in the background with a schema-enforced report. Use when a task is ready and the user or architect wants it implemented by Codex.

84 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use state, preview and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    state

    Store and query a Microsoft Managed App's built-in state and file attachments with `ms project state` CLI schema commands and generated TypeScript clients. First, with the user signed in to the CLI, run `ms feature status --name state --json`; if `feature.enabled` is not `true`, recommend an alternative connector or data source.

    Also in 3 projects that use this

  • kv0906Skill

    preview

    Render vault notes as styled HTML and open in browser. Turn markdown docs, decisions, progress reports into readable previews. Use for "/preview docs/project-a/checkout-flow.md", "/preview progress all", "/preview decide auth-approach", or when user wants to see a doc before sharing.

    Also in 3 projects that use this

  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 5 projects that use this

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 3 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    skill-authoring

    Write Agent Skills that comply with the agentskills.io specification. WHEN: "create a skill", "new skill", "write a skill", "skill template", "skill structure", "review skill", "skill PR", "skill compliance", "SKILL.md format", "skill frontmatter", "skill best practices". DO NOT USE FOR: general documentation. INVOKES: vally CLI.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 73 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start the job as a background shell command so you are notified when it ends (do not poll): node "${CLAUDE_PLUGIN_ROOT}/scripts/aod.mjs" …

    line 10
  2. Distinctive:

    When notified, read the JSON result:

    line 15
  3. Very specific:

    Never trust the report's claims.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 73 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Delegate T-xxxx to Codex

  1. The task must be ready (run /aod:preflight first). Check slots with node "${CLAUDE_PLUGIN_ROOT}/scripts/aod.mjs" status. Slots are created on demand from the base branch.
  2. Start the job as a background shell command so you are notified when it ends (do not poll): node "${CLAUDE_PLUGIN_ROOT}/scripts/aod.mjs" delegate T-xxxx The model comes from the routing (aod route show): implement first, escalate automatically after a failed job or from review round 2. Override only with evidence: --model <id>, --effort low|medium|high, --slot codex-2.
  3. While it runs, do other work: prepare the next packet, write contracts, or review another task.
  4. When notified, read the JSON result:
    • exit 0, status: review -> run /aod:verify T-xxxx.
    • exit 3, status: blocked -> the implementer asked open_questions. Answer from ADRs/spec if possible; otherwise ask the user (context, options, recommendation). Record the answer in the packet if it is a decision, write the answer to a file and resume (background): node "${CLAUDE_PLUGIN_ROOT}/scripts/aod.mjs" revise T-xxxx --findings <file> --answer
    • exit 1, status: failed -> read .agents/tasks/jobs/T-xxxx/stderr.log and the error; fix the environment and retry, or aod reject T-xxxx and split the task. The result's failures counts failed jobs; at 2, reject and split the task.
    • exit 5 -> Codex is unavailable or out of quota. The task is back to ready and nothing was counted as a failure. Stop and ask the user (/aod:decision): wait for the quota window, switch the preset (aod route preset economy), or something else. Never implement it yourself without the user's go-ahead.

Never trust the report's claims; verification happens in /aod:verify.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free