requirements-consultant

Guide software projects through a six-phase requirements discovery protocol.

2|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Kaakati/sdh-claude-skills --skill requirements-consultant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements-consultant
Source: https://github.com/Kaakati/sdh-claude-skills/tree/main/.claude/skills/requirements-consultant
Command: npx skills add https://github.com/Kaakati/sdh-claude-skills --skill requirements-consultant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses ambiguity in project requirements, ensuring clear understanding and actionable plans before development begins.

Core Features & Use Cases

  • Requirement Clarification: Transforms vague ideas into precise user stories.
  • Scope Definition: Identifies boundaries, assumptions, and acceptance criteria.
  • Use Case: When a product manager says "We need a new user profile page," this skill will elicit details about who the users are, what information they need, and how success will be measured.

Quick Start

Use the requirements-consultant skill to break down the epic "Implement user authentication" into user stories with acceptance criteria.

Frequently Asked Questions about requirements-consultant

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

FAQPage Schema
How do I break down epics into detailed user stories with acceptance criteria?

To break down epics into user stories, this skill guides you through a structured six-phase protocol to define feature scope and generate precise user stories with acceptance criteria, ensuring comprehensive project definition.

What is the best way to define project scope and identify hidden requirements?

Defining project scope and identifying hidden requirements is achieved by facilitating structured requirements discovery, which clarifies business objectives, documents assumptions, and creates a dependency map.

How do I create a risk register and delivery plan for software development?

You can create a risk register and delivery plan by using a structured requirements clarification process that evaluates complexity ratings, maps dependencies, and outlines delivery proposals before development begins.

Can I use this to transform vague product ideas into actionable architecture proposals?

Yes, you can transform vague product ideas into actionable architecture proposals by following the guided discovery protocol that clarifies business objectives and defines detailed feature boundaries.

Does requirements discovery work for fixing ambiguous project scope before development?

Requirements discovery works effectively for fixing ambiguous project scope by eliciting detailed information from vague ideas to ensure clear understanding and actionable plans before development begins.