requirements-expert

Break epic into INVEST-compliant stories

Break story into implementation tasks

Discover product vision and create issue

Identify epics from vision, create issues

Initialize GitHub Project with custom fields

Prioritize requirements with MoSCoW

Validate requirements quality and traceability

Show requirements project status and health

Use this agent when the user is working on project planning, requirements gathering, or breaking down work into manageable pieces. Triggers when discussing visions, epics, user stories, tasks, acceptance criteria, or when starting new projects/features. <example> Context: User has a new project idea and wants help planning it user: "I want to build a meal planning app that helps people eat healthier" assistant: "I'll use the requirements-assistant agent to help structure your meal planning app, starting with project initialization." <commentary>User describing a new application concept triggers the agent to begin the requirements lifecycle with project initialization.</commentary> </example> <example> Context: User has already created a vision and wants to continue user: "I've got my vision done, what's next?" assistant: "I'll use the requirements-assistant agent to check your GitHub Project state and guide you through identifying epics from your vision." <commentary>User asking about next steps after completing a phase triggers the agent to assess state and suggest the appropriate next command.</commentary> </example> <example> Context: User mentions specific requirements terminology user: "Can you help me write acceptance criteria for my user authentication story?" assistant: "I'll use the requirements-assistant agent to help write acceptance criteria for your user authentication story, ensuring they're specific, measurable, and testable." <commentary>User asking about requirements artifacts (acceptance criteria, user stories) triggers the agent to help with structured requirements creation.</commentary> </example> <example> Context: User wants to validate or review requirements quality user: "Can you check if my requirements are complete and properly linked?" assistant: "I'll use the requirements-assistant agent to run /re:review and provide a validation report covering completeness, consistency, quality, and traceability." <commentary>User asking for validation or quality checks triggers the agent to run comprehensive requirements review.</commentary> </example> <example> Context: User asks for simple status without needing workflow guidance user: "Show me the current status of my requirements project" assistant: "I'll run `/re:status` to show your project overview." <commentary>Simple status requests don't need the agent - run the command directly. The agent is for workflow guidance, not routine command execution.</commentary> </example>

This skill should be used when the user asks to "identify epics", "break down vision into epics", "find major features", "discover capability areas", "decompose vision", "group requirements into themes", "define high-level features", "what epics do I need", "turn vision into work items", or "split project into epics". Provides methodology for deriving epics from a vision statement using user journey mapping, capability decomposition, and stakeholder analysis.

This skill should be used when the user asks to "prioritize requirements", "prioritize epics", "prioritize stories", "prioritize tasks", "prioritize backlog", "use MoSCoW", "apply MoSCoW priorities", "assign priorities", "set priority labels", "rank features", "what should I build first", "what's most important", "order by importance", "must have vs should have", or when they need to determine the priority order of epics, user stories, or tasks using the MoSCoW framework.

This skill should be used when the user asks about "feedback loops", "iterate on requirements", "continuous documentation", "refine requirements", "update requirements", "requirements changed", "stakeholder review", "validate requirements", "incorporate feedback", "gather feedback", "requirements review meeting", "backlog refinement feedback", "user research findings", "sprint retrospective feedback", "help me gather feedback", "run a feedback session", "get input on my vision", "get input on my epics", "get input on my stories", "collect user feedback", "document feedback from meeting", "review requirements with stakeholders", or when they need guidance on collecting and incorporating feedback throughout the requirements lifecycle.

This skill should be used when the user asks to "implement recovery flow", "add error handling to command", "handle gh operation failures", "implement idempotency check", "prevent duplicate issues", "check before creating", "implement batch tracking", "track created and failed items", "implement two-layer metadata", "update custom fields and labels", "standardize command patterns", or when developing or modifying /re:* commands that need consistent error handling, duplicate detection, batch operation tracking, or GitHub Projects metadata updates.

This skill should be used when the user asks to "create tasks", "break down story into tasks", "define tasks", "what tasks are needed", "write acceptance criteria", "implementation tasks", "task list", "create work items", "technical tasks", "work breakdown", "decompose story", "story to tasks", or when decomposing user stories into specific, executable tasks with clear acceptance criteria for GitHub Projects.

This skill should be used when the user asks to "create user stories", "write user stories", "break down epic into stories", "define user stories", "what stories do I need", "apply INVEST criteria", "write acceptance criteria", "split a large story", "story is too big", "story splitting", or when decomposing epics into specific, valuable user stories.

This skill should be used when the user asks to "validate requirements", "review requirements quality", "check requirements completeness", "verify traceability", "check INVEST compliance", "validate user stories", "requirements health check", "quality gate check", or when running /re:review validation.

This skill should be used when the user asks to "discover vision", "create a vision", "define product vision", "document vision", "what should my vision be", "help me with vision", "start requirements from scratch", "begin new product planning", "define product direction", "establish product vision", or when starting a new requirements project and needs to establish the foundational product vision before identifying epics or stories.

1 hook across 1 event