agentleFS
45ck45ck/business-analysis-skills/.agents/skills/requirements-packager/SKILL.md

requirements-packager

Skill28 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Prefer evidence-backed conclusions over polished speculation.

    line 33

≈ “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

Purpose

Assemble BA outputs into a coherent, reusable requirements or analysis pack.

Use when

  • elicitation and analysis outputs exist but are fragmented
  • a formal document or pack is needed
  • traceability and reviewability matter

Inputs

  • project or problem context
  • goals and constraints
  • known stakeholders, systems, and documents
  • level of formality required

Procedure

  1. Gather all existing artifacts and normalise terminology.
  2. Organise content into background, scope, models, catalogue, and open issues.
  3. Structure requirements into a navigable hierarchy.
  4. Link requirements back to needs, stakeholders, and sources.
  5. Insert diagrams, glossary, assumptions, and traceability references.
  6. Flag unresolved contradictions and decisions pending.
  7. Produce a review-ready package.

Outputs

  • requirements document structure
  • requirements catalogue
  • glossary
  • source/traceability notes
  • open issues register

Guardrails

  • Explicitly separate fact, inference, and assumption.
  • Prefer evidence-backed conclusions over polished speculation.
  • Where conflict exists, record it rather than smoothing it away.
  • Produce artifacts that can be inspected, edited, and reused.

Completion criteria

  • deliverable pack exists
  • tradeoffs are explicit
  • unknowns are logged
  • next decisions are obvious

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.