agentleFS
45ck45ck/business-analysis-skills/.agents/skills/use-case-specification/SKILL.md

use-case-specification

Skill28 starsChanged 8 months agoMITView on GitHub

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Do not present the technique as the answer.

    line 30
  2. Distinctive:

    Keep terminology consistent with the project glossary.

    line 32

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

Purpose

Define actors, triggers, flows, exceptions, and outcomes for user-system interactions.

Use when

  • functional behavior must be described clearly
  • requirements need structured interaction modelling
  • design/testing traceability is important

Inputs

  • problem context
  • available evidence and constraints
  • known stakeholders or actors
  • desired output format

Procedure

  1. Clarify the decision or deliverable.
  2. State assumptions before analysis.
  3. Apply the technique explicitly rather than implicitly.
  4. Capture findings in a structured table or list.
  5. Separate facts, inferences, and unknowns.
  6. End with implications for next actions.

Outputs

  • use case list
  • use case descriptions
  • normal/alternate/exception flows
  • acceptance notes

Guardrails

  • Do not present the technique as the answer; use it to inform a decision.
  • Flag missing evidence and weak assumptions.
  • Keep terminology consistent with the project glossary.
  • Where tradeoffs exist, rank them explicitly.

Completion criteria

  • technique applied correctly
  • assumptions visible
  • findings actionable
  • next step clear

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.