gather-nfr

Collect non-functional requirements via interactive Q&A and save them to active story files.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/amdmax/claude_marketplace --skill gather-nfr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gather-nfr
Source: https://github.com/amdmax/claude_marketplace/tree/main/.claude/skills/gather-nfr
Command: npx skills add https://github.com/amdmax/claude_marketplace --skill gather-nfr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the collection of crucial Non-Functional Requirements (NFRs) by interactively questioning users, ensuring that performance, scalability, security, and other critical aspects are considered early in the development process.

Core Features & Use Cases

  • Interactive Q&A: Guides users through targeted questions across multiple NFR categories.
  • Contextual Tailoring: Adapts questions based on story context (title, labels, body).
  • Structured Data Collection: Saves collected NFRs directly into the .claude/active-story.json file for use by other skills.
  • Use Case: When starting a new feature, run /gather-nfr to ensure all necessary NFRs like expected user load, data retention policies, and security compliance needs are captured before architecture design begins.

Quick Start

Run the gather-nfr skill to collect non-functional requirements for the current story.

Frequently Asked Questions about gather-nfr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect non-functional requirements for a new feature story?

You collect non-functional requirements by running an interactive Q&A process that asks targeted questions across performance, scalability, security, and cost categories, then appends the structured NFR data directly into your active story file.

What is the best way to capture NFRs like data retention and security compliance before architecture design?

Capturing NFRs before architecture design is best handled by interactively analyzing story context to tailor inquiries about data retention and security compliance, ensuring critical aspects are considered early and saved for subsequent workflow steps.

How do I document non-functional requirements interactively using story context?

You document non-functional requirements interactively by parsing story context such as the title, labels, and body to adapt questions, ensuring the collected NFR data aligns with the specific needs of the active story.

Does gather-nfr work with active story files to save collected NFR data?

Yes, gather-nfr works with active story files by appending collected NFR data directly into the `.claude/active-story.json` file, integrating the structured requirements for use by downstream skills like ADR creation.

Can I use this skill to gather scalability and reliability requirements for my project?

Yes, you can use this skill to gather scalability and reliability requirements, as it interactively guides users through targeted questions across multiple NFR categories including performance, data, and reliability.

What categories of non-functional requirements does this interactive Q&A process cover?

The interactive Q&A process covers six categories of non-functional requirements: performance, scalability, data, security, reliability, and cost, tailoring inquiries based on the provided story context.