agentleFS
Sign inStart free
sohaibtsohaibt/product-mode/skills/decision/SKILL.md

decision

Skill176 starsChanged 33 days agoMITView on GitHub

Write a product-mode decision record for a choice made in this conversation and save it to .product-mode/decisions/. Use when the user types /decision.

17 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

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 3

    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. Very specific:

    Check .product-mode/decisions/ for an entry about the same decision.

    line 11
  2. Distinctive:

    Options considered: every option that was discussed, including the rejected ones

    line 14
  3. Distinctive:

    Never invent options, reasons, or evidence that the conversation does not contain.

    line 18
  4. Distinctive:

    If the decision is a one-way door (public API, data schema, pricing, brand, core UX), confirm that the user signed off and that the …

    line 19

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

Record the decision the user names. Use the text after the command as the decision title. If there is no text, use the most recent non-trivial decision in the conversation, and confirm the title with the user.

  1. Check .product-mode/decisions/ for an entry about the same decision. If one exists, update it instead of writing a new one, and tell the user its path.
  2. Draft each field from the conversation and the code:
    • Context: the problem and the constraints
    • Options considered: every option that was discussed, including the rejected ones
    • Choice: the option chosen, and the reason
    • Reversibility: one-way door or two-way door
    • Revisit trigger: the metric, date, or condition that reopens this decision
  3. Never invent options, reasons, or evidence that the conversation does not contain. If the reason or the revisit trigger is missing, ask for it.
  4. If the decision is a one-way door (public API, data schema, pricing, brand, core UX), confirm that the user signed off and that the tradeoffs are written down.
  5. Show the draft. When the user confirms, save the file as .product-mode/decisions/<UTC timestamp>-<title-slug>.md. Use the timestamp format 2026-01-31T09-05-00-000Z and a lowercase, hyphenated slug. Use this content:
## Decision: <title>
Date: <YYYY-MM-DD>
Context: <context>
Options considered: [<A>, <B>, <C>]
Choice: <X>, because <reason>
Reversibility: <one-way door | two-way door>
Revisit trigger: <trigger>

---
*Generated by product-mode /decision*
  1. Tell the user the saved path.

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