agentleFS
jdinklajdinkla/user-story-skills/skills/story-nonfunctional/SKILL.md

story-nonfunctional

Skill0 starsChanged 7 months agoMITView on GitHub

Extract 6–12 specific, measurable nonfunctional requirements (performance, scalability, security, reliability, accessibility, observability, usability, maintainability) for a user story, with priority and rationale. Use when the user asks about NFRs, quality attributes, SLAs, or "what should this thing do besides the functional part?".

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:

    If none of the above, ask the user to paste the story or point to a file.

    line 17

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

Nonfunctional Requirements

Identify 6–12 concrete, measurable NFRs for a user story with priority and rationale.

Input

Take the user story from whichever of these is available first:

  1. Text passed as arguments to this skill or slash command.
  2. A file reference like @path/to/story.md — read the file first.
  3. The current editor selection or most recently referenced story in the conversation.
  4. If none of the above, ask the user to paste the story or point to a file.

Instructions

You are a senior software architect and systems engineer.

Your task is to identify nonfunctional requirements (NFRs) for a user story. NFRs define how the system should work, not what it should do — quality attributes, constraints, and cross-cutting concerns.

Categories to consider:

  1. Performance — response time targets, throughput, resource usage.
  2. Scalability — concurrent users, data volume, growth projections.
  3. Security — authn, authz, data protection, rate limiting, input validation.
  4. Reliability — uptime, error handling, data consistency, backup/DR.
  5. Accessibility — WCAG compliance level, screen reader, keyboard nav, contrast.
  6. Observability — logging, monitoring, alerting, metrics, debuggability.
  7. Usability — UX standards, error messages, help, mobile responsiveness.
  8. Maintainability — code quality, docs, test coverage, tech-debt considerations.

Guidelines:

  1. Be specific and measurable — concrete numbers, acceptance criteria. "Page load < 2s on 4G", not "fast page loads".
  2. Prioritize — critical (must have), high (significant impact), medium (later is ok), low (nice to have).
  3. Focus on what matters for THIS story — not generic NFRs that apply to everything.
  4. Provide rationale — connect each NFR to user needs or business goals.
  5. Be realistic — balance quality with delivery speed; don't over-engineer.

Output format

Render as markdown in the chat:

  • Title: "Nonfunctional Requirements for [Feature]"
  • Overview — 1–2 sentences
  • Requirements — 6–12 NFRs across relevant categories. For each: Category, Requirement, Rationale, Priority. A table works well.
  • Summary — key takeaways about the most critical NFRs
  • Considerations — trade-offs or implementation concerns

Example requirement:

Category: Security Requirement: Reset tokens must expire after 1 hour Rationale: Prevents token reuse attacks and limits exposure window if email is compromised Priority: critical

No JSON.

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.