agentleFS
45ck45ck/business-analysis-skills/.agents/skills/functional-vs-nonfunctional-splitter/SKILL.md

functional-vs-nonfunctional-splitter

Skill28 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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 short, testable statements over long prose.

    line 47
  2. Distinctive:

    Do not invent stakeholder intent.

    line 52
  3. Distinctive:

    Do not convert preferences into mandatory requirements without evidence.

    line 53
  4. Distinctive:

    Do not hide unresolved ambiguity behind polished wording.

    line 54
  5. Distinctive:

    Do not collapse functional, non-functional, and business rule concerns into one blob.

    line 55

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

functional-vs-nonfunctional-splitter

Purpose

Separate behaviors the system must perform from quality attributes, constraints, and operational rules.

Trigger this skill when

  • Requirements are mixed together in prose.
  • A brief uses vague statements like reliable, scalable, simple, secure, fast.
  • You need a cleaner input for design, estimation, or test planning.

Expected inputs

  • requirements text
  • scope notes
  • stakeholder needs

Deliverables

  • functional requirements list
  • non-functional requirements list
  • misclassified statements list

Operating procedure

  1. Extract each requirement statement independently.
  2. Classify it as functional, non-functional, business rule, external constraint, assumption, or design choice.
  3. Rewrite blended statements into multiple atomic requirements where necessary.
  4. Group non-functional items by category such as performance, security, usability, reliability, maintainability, compliance, and supportability.

Quality gates

  • Each requirement is atomic.
  • Quality constraints are not mislabeled as features.
  • Design choices are not silently treated as requirements.

Handoff targets

  • acceptance-criteria-writer
  • requirements-prioritizer
  • requirements-traceability-starter

Output style

  • Be explicit about uncertainty.
  • Prefer short, testable statements over long prose.
  • Surface risk and ambiguity instead of guessing.
  • Separate facts, assumptions, constraints, and open questions.

Failure modes to avoid

  • Do not invent stakeholder intent.
  • Do not convert preferences into mandatory requirements without evidence.
  • Do not hide unresolved ambiguity behind polished wording.
  • Do not collapse functional, non-functional, and business rule concerns into one blob.

Minimum output skeleton

## Summary
## Findings
## Structured outputs
## Assumptions
## Constraints
## 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.