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

preflight

Skill0 starsChanged 29 days agoApache-2.0View on GitHub

Pre-flight check of an AOD task packet before delegation - consistency of packet, spec, ADRs, contracts and acceptance tests, and that acceptance fails for the expected reason. Use before /aod:delegate.

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ship, report and 8 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.
  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 5 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 3 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 4 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 3 projects that use this

  • DockerSkill

    review-pr

    Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 0

    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:

    Run the deterministic checks: aod preflight T-xxxx It verifies the packet front matter, the task/T-xxxx branch, depends_on, every contracts …

    line 10
  2. Very specific:

    If everything holds: aod task set T-xxxx status=ready, then /aod:delegate T-xxxx.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 44 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

Pre-flight for T-xxxx

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

  1. Run the deterministic checks: aod preflight T-xxxx It verifies the packet front matter, the task/T-xxxx branch, depends_on, every contracts entry (files exist on the task branch, ADRs are Accepted), the spec (EARS lint, requirement ids named in the packet), new acceptance tests, scope overlap with active tasks and brief size. It then runs every acceptance command on a checkout of task/T-xxxx (a free slot or a temporary worktree). Each must fail, and for the right reason: a failing assertion, or "module not found" for a module inside the task scope. A command that passes, or fails with a syntax error, an out-of-scope missing module or a missing tool, is a fail.
  2. Any fail: a spec or ADR missing on the task branch means it was committed on the base branch later: run aod task sync T-xxxx. Otherwise fix it (aod packet restore T-xxxx, edit, aod task commit T-xxxx ...; acceptance-test edits need aod unlock --reason ... first and aod lock after), then run preflight again.
  3. Judge what a script cannot: read the packet (aod packet show T-xxxx) next to the spec, ADRs and contracts it names, and confirm they do not contradict each other (names, types, units, error cases) and that the tail of each red acceptance run is about the missing behaviour. Resolve or accept each warn explicitly.
  4. If everything holds: aod task set T-xxxx status=ready, then /aod:delegate T-xxxx.

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