requirement-definition

Transform product briefs and stakeholder input into validated requirements and an initial Product Backlog.

15|5|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/sohei56/maul-team --skill requirement-definition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirement-definition
Source: https://github.com/sohei56/maul-team/tree/main/skills/requirement-definition
Command: npx skills add https://github.com/sohei56/maul-team --skill requirement-definition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an initial product brief and stakeholder input into clear, testable requirements and an actionable starting backlog, preventing ambiguity and scope drift before development begins.

Core Features & Use Cases

  • Guided Requirements Interview: Elicits business, functional, non-functional, technical, and constraint details through structured dialogue.
  • Benchmark Research: Investigates similar products and prior art through mandatory web searches, then records source-backed adopt, adapt, or reject decisions.
  • Backlog and Project Setup: Produces requirements documentation, reconciles conflicts with the product brief, initializes coarse-grained backlog items, and prepares project guidance in CLAUDE.md.
  • Use Case: Start with a brief for a new product, validate its scope against user needs and relevant market examples, and finish with approved requirements and an initial Product Backlog ready for Scrum execution.

Quick Start

Activate the requirement-definition skill in a project whose state is new or requirements_sprint to interview stakeholders, research benchmarks, create the requirements documents, and initialize the backlog.

Frequently Asked Questions about requirement-definition

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

FAQPage Schema
How do I turn a product brief into a testable Scrum backlog?

This Skill transforms a product brief into testable requirements by eliciting stakeholder input, performing live benchmark research, reconciling scope conflicts, and generating requirements artifacts alongside an initial Product Backlog.

What is the best way to elicit and validate product requirements before development?

Validating product requirements involves a structured interview capturing functional and technical details, cross-checking them against live web benchmark research, and requiring documented Product Owner decisions to resolve scope ambiguity.

How do I conduct benchmark research and reconcile product scope during discovery?

Conduct benchmark research by executing mandatory web searches for similar products, recording source-backed adopt, adapt, or reject decisions, and reconciling scope conflicts against the product brief before finalizing requirements.

Can I initialize a Scrum project directly from validated requirements?

Yes, you can initialize a Scrum project directly from validated requirements. This Skill sets up project guidance in CLAUDE.md and creates coarse-grained Product Backlog items ready for sprint execution.

Do I need live web research and stakeholder input to generate requirements documents?

Yes, live web research and documented stakeholder or Product Owner decisions are required. The workflow mandates web searches for benchmark validation and recorded state transitions to ensure requirements are fully validated.