agentleFS
45ck45ck/business-analysis-skills/.agents/skills/benefit-hypothesis-writer/SKILL.md

benefit-hypothesis-writer

Skill28 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    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 hypotheses in the form: if we change X for Y context, we expect Z outcome because A.

    line 34
  2. Distinctive:

    Prefer structured outputs over loose prose.

    line 51
  3. Distinctive:

    Do not pretend weak evidence is confirmed fact.

    line 56
  4. Distinctive:

    Do not confuse stakeholder opinion with validated rule or process truth.

    line 57
  5. Distinctive:

    Do not hide missing coverage behind polished wording.

    line 58
  6. Distinctive:

    Do not flatten politically different stakeholders into one generic audience.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

benefit-hypothesis-writer

Purpose

Turn proposed process or system changes into explicit benefit hypotheses with measurable expected outcomes and assumptions.

Trigger this skill when

  • A change is being proposed but the benefit case is weak or hand-wavy.
  • Stakeholders want to know why the change matters.
  • You need a bridge from analysis to business value.

Expected inputs

  • problem statement
  • as-is findings
  • to-be proposal
  • stakeholder goals
  • baseline pain points

Deliverables

  • benefit hypotheses
  • success measures
  • dependency assumptions
  • evidence gaps

Operating procedure

  1. List the proposed change and the baseline problem it addresses.
  2. Write hypotheses in the form: if we change X for Y context, we expect Z outcome because A.
  3. Define leading and lagging measures where possible.
  4. Capture assumptions, dependencies, and evidence gaps.
  5. Differentiate direct benefits, indirect benefits, and uncertain upside.

Quality gates

  • Hypotheses are measurable where possible.
  • Causal logic is explicit.
  • Assumptions and evidence gaps are visible.

Handoff targets

  • stakeholder-communication-planner
  • project-charter-writer if present
  • requirements-prioritizer if present

Output style

  • Be explicit about uncertainty.
  • Prefer structured outputs over loose prose.
  • Separate confirmed findings, inferred findings, and open questions.
  • Preserve source context where practical.

Failure modes to avoid

  • Do not pretend weak evidence is confirmed fact.
  • Do not confuse stakeholder opinion with validated rule or process truth.
  • Do not hide missing coverage behind polished wording.
  • Do not flatten politically different stakeholders into one generic audience.

Minimum output skeleton

## Summary
## Findings
## Structured outputs
## Risks or tensions
## Open questions
## Recommended next skill

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.