How does it handle prioritization?

It uses a Value/Cost/Risk scoring system or a MoSCoW (Must, Should, Could, Won't) framework to help teams focus on the most impactful features first.

What is the primary goal of the Elicit Requirements skill?

The goal is to transform a broad vision into concrete, testable, and prioritized user stories that a developer can implement immediately without ambiguity.

Can it define performance and security requirements?

Yes, it specifically includes a step for Quality Requirements, using measurable targets for attributes like response time, uptime, and security protocols.

Should I use this before or after defining a project scope?

This skill should be used after you have a basic vision or scope. If you don't have a vision yet, it is recommended to use the discover-and-define skill first.

Does this skill help with testing?

Yes. It mandates the creation of Acceptance Criteria for every requirement, providing the exact Given/When/Then scenarios needed to write automated tests.

Elicit Requirements

Name: Elicit Requirements
Author: NazarKalytiuk

byNazarKalytiuk

0•

생산성 및 워크플로

Transforms high-level project visions into concrete, implementation-ready user stories with testable acceptance criteria.

Elicit Requirements is a specialized skill designed to bridge the gap between abstract project ideas and actionable technical specifications. It systematically guides the user through mapping user flows, drafting INVEST-compliant user stories, and defining rigorous Given/When/Then acceptance criteria. By extracting business rules and setting measurable quality targets, this skill ensures that every line of code written has a clear business justification and a defined path for testing and validation.

주요 기능

010 GitHub stars

02Measurable quality requirement (Planguage) specification

03Business rule and logic extraction

04INVEST-compliant user story generation

05Value/Cost/Risk-based story prioritization

06Given/When/Then acceptance criteria formatting

사용 사례

01Converting user feedback and 'wishes' into testable technical requirements

02Refining project scope to ensure every feature is traceable to a business objective

03Breaking down a vague 'vision document' into a structured developer backlog

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add nazarkalytiuk/claude-woow elicit-requirements

For use in Claude.ai and ChatGPT

주요 기능

010 GitHub stars

02Measurable quality requirement (Planguage) specification

03Business rule and logic extraction

04INVEST-compliant user story generation

05Value/Cost/Risk-based story prioritization

06Given/When/Then acceptance criteria formatting

사용 사례

01Converting user feedback and 'wishes' into testable technical requirements

02Refining project scope to ensure every feature is traceable to a business objective

03Breaking down a vague 'vision document' into a structured developer backlog

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add nazarkalytiuk/claude-woow elicit-requirements

For use in Claude.ai and ChatGPT