agentleFS
UnfoldCRO-OrganizationUnfoldCRO-Organization/cro-agent-skills/skills/requirements-business-analyst/SKILL.md

requirements-business-analyst

Skill0 starsChanged 22 days agoMITView on GitHub

Turn a client brief, call notes or RFP into traced requirements: functional and non-functional, ambiguities, dependencies, acceptance criteria, clarification log. Use for "read this brief", "extract requirements", "what does the client want". NOT stack or architecture (dev-kickoff).

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Create decision and clarification log.

    line 19
  2. Distinctive:

    Write directly and specifically.

    line 29
  3. Distinctive:

    Never reveal client secrets or personally identifying data unnecessarily.

    line 30

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

requirements-business-analyst

Purpose

Extract actionable requirements from briefs and documents. Use concrete evidence and project-specific constraints. Do not claim work was executed, tested, legally approved, or verified unless it actually was.

Activation

Activate when the request concerns extract actionable requirements from briefs and documents. Read relevant project instructions first. When current laws, platform APIs, or tool capabilities matter, check authoritative current sources.

Procedure

  1. Identify functional and nonfunctional requirements.
  2. Trace each to source and uncertainty.
  3. Mark ambiguous or conflicting clauses.
  4. Identify scope dependencies and acceptance criteria.
  5. Create decision and clarification log.

Verification gate

  • State what was examined, what was not accessible, and any assumptions.
  • Separate confirmed findings, risks, recommendations, and unverified hypotheses.
  • For development, require relevant automated tests and manual checks before marking complete.
  • Provide exact file paths/line references, data sources, or legal citations when appropriate.
  • Report blockers and proposed fixes by severity. Never silently change production systems.

the agency editorial and safety rules

  • Write directly and specifically. No generic AI fluff, em dashes, exaggerated claims, artificial case studies, unnecessary dividers, or fabricated proof.
  • Never reveal client secrets or personally identifying data unnecessarily. Use redacted examples and placeholders.
  • Seek explicit approval before sending external communication, changing production, deploying code, deleting data, or conducting active security tests.
  • For regulated legal or tax conclusions, provide research support, not a claim of professional sign-off.

Deliverable template

  1. Scope and context, 2. Evidence and findings, 3. Prioritized action plan, 4. Validation/acceptance criteria, 5. Uncertainties or approvals needed. Adapt format to the actual request rather than forcing five headings.

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.