Requirements Analyst
Convert vague requirements into clear, executable requirement documents.
How to Use
Trigger Method
Describe your requirements directly to Claude, for example:
I need a user login function
Help me analyze this requirement: Users can post and browse products on the platform
Write a PRD for the user system
Usage Process
- Describe Requirements - Describe the function you want in natural language (can be vague or incomplete)
- Select Format - The assistant will ask about the output format (User Story / PRD)
- Answer Questions - The assistant will ask clarification questions, select or enter your answers
- Obtain Document - The assistant outputs a structured requirement document
- Confirm Adjustments - Request modifications or supplements as needed
Example Conversation
User Input:
I need a shopping cart function
Assistant Response:
- Identify missing information (user type, function scope, boundary conditions)
- Ask clarification questions:
- Does the shopping cart support guest users?
- What features are needed for MVP? (Add/remove items/save/coupons)
- Is there a quantity limit for items?
- Generate User Story based on answers:
markdown
## User Story: Add Product to Shopping Cart
**As a** website visitor or registered user
**I want** to add products to the shopping cart
**So that** I can continue browsing and checkout together later
### Acceptance Criteria
- [ ] Given the user is on the product detail page, when clicking "Add to Cart", then the product is added and a success prompt is displayed
- [ ] Given the product is already in the shopping cart, when adding again, then the quantity increases instead of adding a duplicate entry
Analysis Workflow
Phase 1: Understanding Stage
- Receive Requirements - Read the original requirement text provided by the user
- Identify Key Elements:
- User Role (Who) - Explicit or implicit user types
- Desired Outcome (What) - What the user wants to achieve
- Business Value (Why) - Why this feature is needed
- Constraints - Technical, time, resource limitations
- Mark Vague Points - Identify parts that need clarification
Phase 2: Clarification Stage
Use AskUserQuestion to resolve vague points. Ask questions by priority:
- Critical Unknowns - Cannot write the story without this information
- Scope Clarification - Boundary conditions and edge cases
- Acceptance Details - How to verify feature completion
Question Principles:
- Ask in batches (3-5 questions per group)
- Provide options instead of open-ended questions
- Explain default assumptions if no answer is provided
Phase 3: Generation Stage
Generate documents based on the selected output format:
- User Story: Generated according to USER_STORY_TEMPLATE.md
- PRD: Generated according to PRD_TEMPLATE.md
Phase 4: Confirmation Stage
- Use the INVEST checklist to verify story completeness
- If the story is too large, provide splitting options
- Confirm with the user and accept feedback
Quick Start
Typical requirements analysis process:
- User provides vague requirements
- Assistant identifies missing information and asks clarification questions
- User answers the questions
- Assistant generates formatted User Stories and acceptance criteria
Output Formats
User Story Format
markdown
## User Story: [Short Title]
**As a** [User Type/Role]
**I want** [Function/Capability]
**So that** [Value/Benefit]
### Acceptance Criteria
- [ ] Given [Context], when [Action], then [Expected Result]
- [ ] Given [Context], when [Action], then [Expected Result]
### Notes
- [Assumption Explanations]
- [Identified Dependencies]
- [Excluded Scope]
PRD Format
markdown
# [Product/Function Name] PRD
## 1. Overview
### 1.1 Background
[Why this feature is needed]
### 1.2 Objectives
[Business and user objectives]
### 1.3 Success Metrics
[How to measure success]
## 2. User Analysis
### 2.1 Target Users
[User personas]
### 2.2 User Pain Points
[Current problems]
### 2.3 User Scenarios
[Typical usage scenarios]
## 3. Functional Requirements
### 3.1 Feature List
[Feature list and priorities]
### 3.2 Feature Details
[Detailed description of each feature]
### 3.3 User Stories
[Corresponding user stories]
## 4. Non-Functional Requirements
[Performance/security/compatibility requirements]
## 5. Data Requirements
[Data model and flow]
## 6. Open Issues
[Pending decisions]
Reference Materials
User Story Template
When to Load: When generating User Stories
See USER_STORY_TEMPLATE.md:
- Standard User Story format
- INVEST checklist
- Story splitting strategies
PRD Template
When to Load: When generating PRD documents
See PRD_TEMPLATE.md:
- Complete PRD structure
- Guidelines for each section
- PRD vs User Story comparison
Acceptance Criteria Guide
When to Load: When writing acceptance criteria
See ACCEPTANCE_CRITERIA.md:
- Given-When-Then format
- Examples of different types of acceptance criteria
- Writing principles
Questioning Strategy
When to Load: When needing to ask users questions
See CLARIFICATION_QUESTIONS.md:
- When to ask vs when to assume
- Categorized question library
- Question templates