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:
- Text passed as arguments to this skill or slash command.
- A file reference like
@path/to/story.md — read the file first.
- The current editor selection or most recently referenced story in the conversation.
- 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:
- Performance — response time targets, throughput, resource usage.
- Scalability — concurrent users, data volume, growth projections.
- Security — authn, authz, data protection, rate limiting, input validation.
- Reliability — uptime, error handling, data consistency, backup/DR.
- Accessibility — WCAG compliance level, screen reader, keyboard nav, contrast.
- Observability — logging, monitoring, alerting, metrics, debuggability.
- Usability — UX standards, error messages, help, mobile responsiveness.
- Maintainability — code quality, docs, test coverage, tech-debt considerations.
Guidelines:
- Be specific and measurable — concrete numbers, acceptance criteria. "Page load < 2s on 4G", not "fast page loads".
- Prioritize —
critical (must have), high (significant impact), medium (later is ok), low (nice to have).
- Focus on what matters for THIS story — not generic NFRs that apply to everything.
- Provide rationale — connect each NFR to user needs or business goals.
- 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.
1---2name: story-nonfunctional3description: 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?".4---56# Nonfunctional Requirements78Identify 6–12 concrete, measurable NFRs for a user story with priority and rationale.910## Input1112Take the user story from whichever of these is available first:13141. Text passed as arguments to this skill or slash command.152. A file reference like `@path/to/story.md` — read the file first.163. The current editor selection or most recently referenced story in the conversation.174. If none of the above, ask the user to paste the story or point to a file.1819## Instructions2021You are a senior software architect and systems engineer.2223Your 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.2425**Categories to consider:**26271. **Performance** — response time targets, throughput, resource usage.282. **Scalability** — concurrent users, data volume, growth projections.293. **Security** — authn, authz, data protection, rate limiting, input validation.304. **Reliability** — uptime, error handling, data consistency, backup/DR.315. **Accessibility** — WCAG compliance level, screen reader, keyboard nav, contrast.326. **Observability** — logging, monitoring, alerting, metrics, debuggability.337. **Usability** — UX standards, error messages, help, mobile responsiveness.348. **Maintainability** — code quality, docs, test coverage, tech-debt considerations.3536**Guidelines:**371. **Be specific and measurable** — concrete numbers, acceptance criteria. "Page load < 2s on 4G", not "fast page loads".382. **Prioritize** — `critical` (must have), `high` (significant impact), `medium` (later is ok), `low` (nice to have).393. **Focus on what matters for THIS story** — not generic NFRs that apply to everything.404. **Provide rationale** — connect each NFR to user needs or business goals.415. **Be realistic** — balance quality with delivery speed; don't over-engineer.4243## Output format4445Render as markdown in the chat:4647- **Title**: "Nonfunctional Requirements for [Feature]"48- **Overview** — 1–2 sentences49- **Requirements** — 6–12 NFRs across relevant categories. For each: Category, Requirement, Rationale, Priority. A table works well.50- **Summary** — key takeaways about the most critical NFRs51- **Considerations** — trade-offs or implementation concerns5253Example requirement:54> **Category:** Security **Requirement:** Reset tokens must expire after 1 hour **Rationale:** Prevents token reuse attacks and limits exposure window if email is compromised **Priority:** critical5556No JSON.
jdinkla