skills.rest
nahisaho
nahisahoCOMMUNITY
Explore all skills by this author →
GitHub

requirements-analyst

Automates requirements analysis and specification generation for software projects.

69|5|Updated Nov 16, 2025
Search Tags:#specification#acceptance criteria#requirements analysis#user stories#functional requirements#non-functional requirements#SRS#EARS format
One-click install
npx skills add https://github.com/nahisaho/musubi --skill requirements-analyst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-analyst
Source: https://github.com/nahisaho/musubi/tree/main/.claude/skills/requirements-analyst
Command: npx skills add https://github.com/nahisaho/musubi --skill requirements-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill eliminates ambiguity and ensures comprehensive understanding of project needs by defining clear, testable functional and non-functional requirements. It prevents costly rework and project misalignment by establishing a solid foundation.

Core Features & Use Cases:

  • Requirements Elicitation: Guides through structured questioning to gather project goals, user types, and system interactions.
  • Functional & Non-Functional Requirements: Defines specific system behaviors and quality attributes (performance, security, availability).
  • User Story Creation: Crafts user-centric stories with acceptance criteria in EARS format.
  • Software Requirements Specification (SRS): Generates comprehensive SRS documents.
  • Use Case: You're starting a new project and need to define its scope. This Skill can help gather information about the project's purpose, target users, and key features, then generate a detailed Software Requirements Specification (SRS) including functional requirements, non-functional requirements (e.g., 99.9% uptime), and user stories with clear acceptance criteria.

Quick Start: Help me define the requirements for a new online booking system. The main goal is to allow users to book appointments easily.

Frequently Asked Questions about requirements-analyst

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

FAQPage Schema
How do I write user stories with clear acceptance criteria?▼

User stories define what users need from a system, paired with acceptance criteria—specific, testable conditions that confirm the story is complete. This Skill structures them in EARS format to ensure they're atomic, measurable, and verifiable, preventing ambiguity between developers and stakeholders.

What's the best way to create a Software Requirements Specification?▼

An SRS documents all functional and non-functional requirements in one comprehensive reference. This Skill generates SRS documents by gathering project goals, defining system behaviors, specifying quality attributes like uptime and security, and organizing requirements with consistent terminology and traceability to stakeholder needs.

How do I gather and organize functional and non-functional requirements?▼

Functional requirements describe what the system does; non-functional requirements specify quality attributes like performance and security. This Skill guides structured elicitation through interviews and workshops, then organizes both types into atomic, measurable statements with consistent terminology and enforcement of EARS patterns.

Can I use acceptance criteria to prevent implementation details in requirements?▼

Yes. Acceptance criteria define testable outcomes without prescribing how to build them, keeping requirements focused on what users need rather than how developers should code. This Skill enforces this separation by applying EARS-based patterns to ensure statements remain verifiable and implementation-agnostic.

What's the difference between functional requirements and use cases?▼

Functional requirements describe specific system behaviors; use cases map user interactions and system responses step by step. This Skill develops both together during requirements elicitation, linking user goals to system capabilities and acceptance criteria, so every interaction is traceable from stakeholder need to implementation.

Do I need requirements traceability to ensure nothing is missed?▼

Traceability links each requirement to its source (stakeholder need, business goal) and downstream artifacts (design, tests), ensuring nothing is lost and impact is visible. This Skill maintains end-to-end traceability from elicitation through validation, supporting bilingual documentation and steering-file references for comprehensive coverage.

Related Skills

Explore More Product & Management Skills→
chausskychaussky
40

elicitation_prep

Guide business analysts through structured requirements elicitation preparation.

Community
Intermediate
Eigo-Mt-FujiEigo-Mt-Fuji

requirements-analyst

Convert stakeholder needs into testable requirements and SRS documentation.

Community
Advanced
beekeeper-labbeekeeper-lab

Build Traceability

Generate traceability matrices mapping user stories and acceptance criteria to test cases.

Community
Advanced
zphzph
20

technical-spec

Convert natural-language requirements into EARS syntax for systems engineering.

Community
Basic