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

packet

Skill0 starsChanged 29 days agoApache-2.0View on GitHub

Cut a piece of work into an AOD task packet (T-xxxx) with scope globs, acceptance commands and acceptance tests, ready to delegate to an implementer. Use when the architect decomposes a feature or the user asks to create a task for Codex.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Write the acceptance tests under tests/acceptance/ (or the project's equivalent).

    line 27
  2. Very specific:

    Commit packet and tests to task/T-xxxx: aod task commit T-xxxx <acceptance test paths...> This never switches the main checkout's branch.

    line 31
  3. Very specific:

    If a spec or ADR was committed on the base branch after task/T-xxxx was cut, aod task sync T-xxxx merges it in.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Create a task packet

A good task: acceptance is a list of commands, scope is a list of globs, and it needs no taste or choice between equal architectural options. Otherwise split it further or keep it for the architect.

CLI: aod below means node "${CLAUDE_PLUGIN_ROOT}/scripts/aod.mjs".

  1. The spec and ADRs the packet will reference must be committed on the base branch first (aod task commit refuses otherwise): commit them as docs: <ADR/spec ids>.
  2. Reserve the id and template. Take the milestone from .agents/plans/roadmap.md (use the current one): aod packet new "<imperative title>" --milestone <M>
  3. Edit .agents/tasks/T-xxxx.md (front matter is machine-checked):
    • scope: the narrowest globs the implementer may change (code and its unit tests).
    • forbidden: extra paths beyond the always-forbidden schemas/**, tests/acceptance/**, .agents/**.
    • acceptance: shell commands run from the repo root; every one must exit 0 when done. Name test files explicitly (Node 22 node --test does not accept a directory).
    • contracts: schema paths and ADR ids that bind the task. depends_on: earlier task ids.
    • budget_minutes, effort (low|medium|high; use high only for hard tasks).
    • Replace every <...> placeholder; aod packet validate refuses leftovers.
    • Body: Implements: R1, R2 (requirement ids from the spec, or none), Context (why, links), Design notes (decisions already made), Pitfalls, Out of scope. Reference files by path; do not paste their content.
  4. Write the acceptance tests under tests/acceptance/ (or the project's equivalent). They must test behaviour, not structure. Contracts and acceptance tests are guarded by a hook: first run aod unlock --reason "acceptance tests for T-xxxx" (time-boxed, logged), and aod lock after step 5.
  5. Validate: aod packet validate T-xxxx
  6. Commit packet and tests to task/T-xxxx: aod task commit T-xxxx <acceptance test paths...> This never switches the main checkout's branch; it moves the committed files off the base branch's working tree (they live on task/T-xxxx). To change the packet later: aod packet restore T-xxxx, edit, then aod task commit T-xxxx [changed test paths...] again. Read it any time with aod packet show T-xxxx. If a spec or ADR was committed on the base branch after task/T-xxxx was cut, aod task sync T-xxxx merges it in.
  7. Next: /aod:preflight T-xxxx.

Ledger rule: .agents/tasks/index.json and index.md may stay uncommitted on the base branch while you work. They are committed by aod merge (with the task) or by aod session end --commit, whichever comes first, and never on a task branch.

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