Specify Requirements

What it does

This skill helps AI agents extract specific details from text to create structured Product Requirements Documents (PRDs). It acts as a product requirements specialist, focusing on defining what needs to be built and why it's important. The skill structures information around four key dimensions: what, why, who, and when. It is designed to exclude technical implementation details which belong in Software Design Documents (SDDs).

When to use it

• When you need to organize unstructured text into a formal PRD format.
• To clarify requirements for a new product or feature by defining user personas, journeys, and acceptance criteria.
• When ensuring that documented requirements are MECE (Mutually Exclusive, Collectively Exhaustive).
• To create a clear understanding of the problem being solved and its value proposition.

Key capabilities

• Extracts information related to "what," "why," "who," and "when" from text.
• Structures extracted data into PRD sections including user personas, journeys, feature requirements, and acceptance criteria.
• Enforces the MECE principle for structured enumerations within the PRD.
• Identifies areas needing clarification (using topic?: string in the PRDSection interface).

Example prompts

• "Analyze this document and create a PRD outlining the requirements for a new mobile app."
• "Based on this user feedback, generate a list of feature requirements and acceptance criteria."
• "Extract the key personas and their journeys from this meeting transcript and structure them into a PRD section."

Tips & gotchas

• This skill focuses solely on defining what needs to be built and why, excluding technical implementation details.
• The output will adhere to the MECE principle, ensuring requirements are distinct and comprehensive.
• If areas require further clarification, the agent will flag them using a topic field within the PRDSection.