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

spec

Skill0 starsChanged 29 days agoApache-2.0View on GitHub

Write a feature spec (S-xxxx) with EARS requirements, each traced to an acceptance test, before any implementation. Use when a feature or requirement is planned in an AOD project, before cutting task packets.

173 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use backprop, ios-clean 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.
  • JuliusBrusseeSkill

    backprop

    Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

    Also in 4 projects that use this

  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 projects that use this

  • Saqlain-811Skill

    ios-fix

    Autonomous iOS bug fixer. (gstack)

    Also in 5 projects that use this

  • bastosSkill

    ios-design-review

    Review iOS app UI/UX design quality using Apple's design principles and the Liquid Glass-era design language from WWDC25/26. Use when asked for a design review, UX critique, visual design assessment, or evaluation of an app's interface quality, design intent, alignment with the new Apple design system, or usability. Triggers: "design review", "UX review", "visual design critique", "review the UI", "does this design work", "evaluate this interface", "design feedback", "Liquid Glass review".

    Also in 5 projects that use this

  • ShreyRaviSkill

    plan-tune

    Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.

    Also in 7 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 6 projects that use this

  • +2 more from Saqlain-811

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 150 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write Context (who needs it, why, links to ADRs and contracts) and Out of scope.

    line 11
  2. Distinctive:

    Write requirements, one testable EARS sentence each, numbered R1, R2, ...:

    line 12
  3. Very specific:

    Commit the approved spec on the base branch (docs: S-xxxx) before /aod:packet.

    line 25

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

Feature spec with EARS requirements

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

  1. aod spec new "<feature title>" creates .agents/specs/S-xxxx-<slug>.md (status draft).
  2. Write Context (who needs it, why, links to ADRs and contracts) and Out of scope.
  3. Write requirements, one testable EARS sentence each, numbered R1, R2, ...:
    • Ubiquitous: The <system> shall <response>.
    • Event: When <trigger>, the <system> shall <response>.
    • State: While <state>, the <system> shall <response>.
    • Unwanted behaviour: If <condition>, then the <system> shall <response>.
    • Optional feature: Where <feature is present>, the <system> shall <response>. One "shall" per requirement; no vague words (should, fast, user-friendly, etc.). Cover error cases with "If ..., then ...". Under each, add Acceptance: <test file> :: <test name> for the test that will prove it.
  4. aod spec check S-xxxx must report no errors; resolve warnings or say why they stay.
  5. Approve before cutting packets (status: approved; preflight warns on draft):
    • the architect approves a spec that only refines the vision and accepted ADRs (no new product behaviour the user has not asked for);
    • anything product-visible, costly or ambiguous goes to the user first (/aod:decision). Commit the approved spec on the base branch (docs: S-xxxx) before /aod:packet.
  6. Cut packets with /aod:packet: set the packet's spec: to the spec path and write Implements: R1, R2 in the packet body. Write each acceptance test exactly as traced.

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