define-requirements

Name: define-requirements
Availability: InStock
Author: sei-newbear

Analyze software feature requests to define scope, objectives, and done conditions.

9|Updated May 11, 2026

Search Tags:#user stories #scope definition #story slicing #requirement elicitation #done conditions

Ready to run

npx skills add https://github.com/sei-newbear/xp-harness --skill define-requirements-sei-newbear

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: define-requirements
Source: https://github.com/sei-newbear/xp-harness/tree/main/.apm/skills/define-requirements
Command: npx skills add https://github.com/sei-newbear/xp-harness --skill define-requirements-sei-newbear

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that software requirements are thoroughly understood and clearly defined before development begins, mitigating the risk of costly misalignments between stakeholder expectations and the final product.

Core Features & Use Cases

Requirement Elicitation: Delve into the true intent behind user requests to uncover underlying needs.
Scoping and Done Conditions: Define specific criteria for completion that are measurable and observable.
Story Slicing: Break down large requirements into smaller, manageable pieces.
Use Case: Ideal for projects where stakeholders require a structured approach to requirement gathering and validation.

Quick Start

Start the define-requirements session and discuss the user story with the AI assistant: "I need a feature to manage customer orders. Let's start by defining the requirements."

Frequently Asked Questions about define-requirements

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

FAQPage Schema

How do I elicit user stories and define clear software requirements?▼

User story elicitation involves engaging in dialogue to understand stakeholder intent and establish clear objectives, scope, and success criteria for proposed software features.

What is the best way to slice large user stories into manageable pieces?▼

Story slicing breaks down large requirements into smaller, manageable pieces, ensuring that each segment maintains measurable done conditions and clear scope definition.

How do you define done conditions for software features?▼

Done conditions are defined by establishing specific, measurable, and observable criteria for completion that align with stakeholder expectations and validate feature feasibility.

When do I need requirement analysis for scope definition?▼

Requirement analysis is needed before development begins to identify the purpose, scope, and feasibility of proposed changes, mitigating costly misalignments between expectations and product.

Can I use this approach for stakeholder intent validation without technical specifications?▼

Yes, the process delves into the true intent behind user requests through structured dialogue, uncovering underlying needs to establish clear objectives independently of technical specs.

Why does requirement gathering fail without measurable success criteria?▼

Requirement gathering fails without measurable success criteria because there are no observable conditions to validate completion, leading to misalignments between stakeholder intent and final software.