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

decision

Skill0 starsChanged 29 days agoApache-2.0View on GitHub

Ask the product owner (the user) for a decision in the AOD format - one line of what, short context, options with trade-offs, a recommendation, and what happens without an answer - then record the answer. Use when a choice is genuinely the user's (product, cost, licence, public commitments, equal architectural options, round-3 review disputes).

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brief, plan and 3 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.
  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • OpenAISkill

    audit

    Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    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, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the request exactly in this shape (in the user's language.

    line 11
  2. Distinctive:

    When you ask, record the open request at once: a line under Open questions in today's journal entry (and in the spec's Open questions when …

    line 24
  3. Distinctive:

    If the answer can wait, say so and keep working on something else.

    line 29

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

Decision request to the product owner

The user's time is the scarcest resource. Ask only what cannot be derived from the vision, invariants and accepted ADRs; decide everything else yourself and record it.

Write the request exactly in this shape (in the user's language; keep it short):

Decision needed on: <task/feature, one line>
Context: <2-3 sentences: what is known, why it matters now>
Options:
  A. <option> - pros / cons / cost
  B. <option> - pros / cons / cost
Recommendation: <A|B> because <reason>
Without an answer: <I continue with the recommendation | work on <branch/task> waits>

Rules:

  • When you ask, record the open request at once: a line under Open questions in today's journal entry (and in the spec's Open questions when it concerns a spec), with the recommendation and what happens without an answer.
  • At most one decision per request; two or three options, never a menu of everything.
  • For a review dispute after round 3: name the task, what the implementer and the reviewer disagree on, and the evidence (failing command, diff lines).
  • If the answer can wait, say so and keep working on something else.
  • Record the answer the moment it arrives: an ADR (/aod:adr) for architectural or product decisions, the packet for task-level answers (then aod revise T-xxxx --findings <file> --answer if an implementer is blocked), and a line in the journal's Decisions or Open questions section.

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