[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70HW5KV5ZVKPMDECDPJ1GSK":3,"skill-same:01M70HW5KV5ZVKPMDECDPJ1GSK":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M70HW5KV5ZVKPMDECDPJ1GSK","requirements-elicitation",null,"Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation. Use when clarifying vague requirements, resolving conflicting needs, documenting specifications, or validating requirements with stakeholders.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Frequirements-elicitation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"requirements elicitation","requirements","elicitation","user","Story","validation","specifications","with","stakeholder analysis","use","techniques","patterns","specification","vague","analysis","when","specification validation","user story","2026-11-10 10:12:30",false,"---\nname: requirements-elicitation\ndescription: Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation. Use when clarifying vague requirements, resolving conflicting needs, documenting specifications, or validating requirements with stakeholders.\n---\n\n# Requirements Elicitation Methodology\n\nSystematic techniques for transforming vague ideas into clear, testable specifications that align stakeholders and guide implementation.\n\n## When to Activate\n\n- Gathering requirements for new features\n- Clarifying vague or ambiguous requests\n- Resolving conflicting stakeholder needs\n- Documenting formal specifications\n- Creating user stories with acceptance criteria\n- Validating requirements before implementation\n\n## Elicitation Techniques\n\n### The 5 Whys\n\nDrill past surface requests to discover root needs:\n\n```\nSurface Request: \"We need a dashboard\"\n\nWhy 1: Why do you need a dashboard?\n→ \"To see our metrics in one place\"\n\nWhy 2: Why do you need to see metrics in one place?\n→ \"To identify problems quickly\"\n\nWhy 3: Why do you need to identify problems quickly?\n→ \"Because slow response affects customer satisfaction\"\n\nWhy 4: Why does customer satisfaction matter right now?\n→ \"We're losing customers and don't know why until it's too late\"\n\nWhy 5: Why don't you know until it's too late?\n→ \"We only see issues in monthly reports\"\n\nRoot Need: Real-time alerting for customer-impacting issues\n(Not just a dashboard - the dashboard was a solution, not the need)\n```\n\n### Concrete Examples\n\nTransform abstract requirements into specific, testable scenarios:\n\n| Abstract | Concrete |\n|----------|----------|\n| \"The system should be fast\" | \"Page loads in under 2 seconds on 3G\" |\n| \"Users should be able to search\" | \"Find orders by customer name, date range, or status\" |\n| \"It needs to be secure\" | \"All PII encrypted at rest, session timeout after 15 min inactive\" |\n| \"Good error handling\" | \"Network failures retry 3x with exponential backoff, then show offline mode\" |\n\n### Boundary Identification\n\nDefine what's explicitly in and out of scope:\n\n```\nFeature: User Registration\n\nIN SCOPE:\n✓ Email\u002Fpassword registration\n✓ Email verification\n✓ Password strength requirements\n✓ Terms of service acceptance\n\nOUT OF SCOPE:\n✗ Social login (Google, Facebook)\n✗ Two-factor authentication\n✗ Password recovery (separate feature)\n\nDEFERRED:\n◐ SSO integration (planned for Q3)\n◐ Biometric login (pending security review)\n```\n\n### Stakeholder Interviews\n\nStructured conversation to extract requirements:\n\n```\nInterview Structure (45 min):\n\n1. CONTEXT (10 min)\n   - What's your role in this project?\n   - What does success look like for you?\n   - What's driving this initiative?\n\n2. CURRENT STATE (10 min)\n   - How do you do this today?\n   - What works well?\n   - What are the pain points?\n\n3. DESIRED STATE (15 min)\n   - What would the ideal solution look like?\n   - Walk me through a typical scenario...\n   - What would make your job easier?\n\n4. CONSTRAINTS (5 min)\n   - What absolutely must be included?\n   - What's definitely out of scope?\n   - Any timeline or budget constraints?\n\n5. WRAP-UP (5 min)\n   - What haven't I asked that I should?\n   - Who else should I talk to?\n   - Can I follow up if I have questions?\n```\n\n### Observation and Shadowing\n\nWatch users perform tasks in their environment:\n\n```\nObservation Protocol:\n\nPREPARE:\n- Define what you're observing\n- Get permission to observe\n- Prepare note-taking template\n\nOBSERVE:\n- Note actions, not interpretations\n- Record workarounds and pain points\n- Note environmental factors\n- Time key activities\n\nDEBRIEF:\n- \"I noticed you did X, can you tell me more?\"\n- \"What would make that easier?\"\n- \"How often does this happen?\"\n\nDocument:\n┌─────────────────────────────────────────────────────────────┐\n│ Observation: Order Processing                               │\n├─────────────────────────────────────────────────────────────┤\n│ Action: Copied customer email from order to support tool    │\n│ Time: 15 seconds per order                                  │\n│ Frequency: ~50 orders\u002Fday                                   │\n│ Pain Point: Manual copy-paste, error-prone                  │\n│ Opportunity: Direct integration between systems             │\n└─────────────────────────────────────────────────────────────┘\n```\n\n## Requirement Documentation\n\n### User Story Format\n\n```\nFormat:\nAs a [role],\nI want [capability],\nSo that [benefit].\n\nComponents:\n- Role: Who benefits (be specific)\n- Capability: What they can do (action, not solution)\n- Benefit: Why it matters (business value)\n\nExample:\nAs a customer service representative,\nI want to see a customer's order history when they call,\nSo that I can resolve their issues without asking them to repeat information.\n```\n\n### Acceptance Criteria (Given-When-Then)\n\n```\nFormat:\nGiven [context\u002Fprecondition]\nWhen [action\u002Fevent]\nThen [expected outcome]\n\nExample:\nFeature: Order Cancellation\n\nScenario: Cancel order before shipping\nGiven an order in \"confirmed\" status\nAnd the order has not been shipped\nWhen the customer requests cancellation\nThen the order status changes to \"cancelled\"\nAnd the customer receives a cancellation confirmation email\nAnd the payment is refunded within 3-5 business days\n\nScenario: Cannot cancel shipped order\nGiven an order in \"shipped\" status\nWhen the customer requests cancellation\nThen the cancellation is rejected\nAnd the customer is directed to the returns process\n```\n\n### Edge Cases and Exceptions\n\nDocument what happens when things go wrong:\n\n```\nFeature: Password Reset\n\nHappy Path:\n- User requests reset → Email sent → User clicks link → Sets new password\n\nEdge Cases:\n| Scenario | Expected Behavior |\n|----------|-------------------|\n| Email not found | Show same success message (security) |\n| Link expired (>24h) | Show \"link expired\" with new reset option |\n| Link already used | Show \"link already used\" message |\n| Weak password | Show requirements, block submission |\n| Same as old password | Show error, require different password |\n| User locked out | Still send reset email (unlock flow) |\n```\n\n### Non-Functional Requirements\n\nDocument quality attributes:\n\n```\nNFR Template:\n┌─────────────────────────────────────────────────────────────┐\n│ Category: Performance                                        │\n├─────────────────────────────────────────────────────────────┤\n│ Requirement: Response Time                                   │\n│ Measure: 95th percentile page load time                     │\n│ Target: \u003C 2 seconds                                          │\n│ Context: Desktop browser, 4G connection                     │\n│ Priority: Must Have                                          │\n└─────────────────────────────────────────────────────────────┘\n\nCommon Categories:\n- Performance: Speed, throughput, latency\n- Scalability: Users, data volume, geographic distribution\n- Availability: Uptime, recovery time, disaster recovery\n- Security: Authentication, authorization, encryption\n- Usability: Accessibility, learnability, efficiency\n- Maintainability: Modularity, testability, documentation\n```\n\n## Stakeholder Management\n\n### Stakeholder Analysis\n\nIdentify and categorize stakeholders:\n\n```\nStakeholder Map:\n\n             High Influence\n                   │\n    ┌──────────────┼──────────────┐\n    │   Manage     │    Partner   │\n    │   Closely    │    With      │\n    │              │              │\nLow ├──────────────┼──────────────┤ High\nInterest          │              Interest\n    │   Monitor    │    Keep      │\n    │   Only       │    Informed  │\n    │              │              │\n    └──────────────┼──────────────┘\n                   │\n             Low Influence\n\nStakeholder Register:\n| Name | Role | Interest | Influence | Communication |\n|------|------|----------|-----------|---------------|\n| VP Sales | Sponsor | High | High | Weekly update |\n| Dev Team | Implementer | High | Medium | Daily standup |\n| Legal | Advisor | Low | High | As needed |\n```\n\n### RACI Matrix\n\nDefine roles for each requirement:\n\n```\nR = Responsible (does the work)\nA = Accountable (final decision maker)\nC = Consulted (provides input)\nI = Informed (kept updated)\n\n| Requirement | Product | Dev | Design | Legal |\n|-------------|---------|-----|--------|-------|\n| User stories | R,A | C | C | I |\n| UI mockups | C | I | R,A | I |\n| API contracts | C | R,A | I | I |\n| Privacy policy | C | I | I | R,A |\n```\n\n### Conflict Resolution\n\nWhen stakeholders disagree:\n\n```\nResolution Process:\n\n1. UNDERSTAND both positions\n   - \"Help me understand why X is important to you\"\n   - Identify underlying needs vs stated positions\n\n2. FIND COMMON GROUND\n   - What do both parties agree on?\n   - What's the shared goal?\n\n3. EXPLORE OPTIONS\n   - Can we do both? (phased approach)\n   - Is there a third option that addresses both needs?\n   - What's the minimum viable for each?\n\n4. ESCALATE if needed\n   - Present options with trade-offs\n   - Let decision-maker decide\n   - Document the decision and rationale\n\nExample:\nMarketing wants: Launch by Q1 with all features\nEngineering says: Can't do all features by Q1\n\nResolution: Launch Q1 with core features (MVP), Phase 2 in Q2\nDocumented: ADR-2024-03: MVP Scope Decision\n```\n\n## Validation Techniques\n\n### Requirements Review Checklist\n\n| Criterion | Question | Pass\u002FFail |\n|-----------|----------|-----------|\n| Complete | Is everything needed documented? | |\n| Consistent | Are there contradictions? | |\n| Correct | Does it match stakeholder intent? | |\n| Unambiguous | Is there only one interpretation? | |\n| Testable | Can we verify it's met? | |\n| Traceable | Can we link to business goal? | |\n| Feasible | Can it be implemented? | |\n| Prioritized | Is importance clear? | |\n\n### Prototype Validation\n\nUse prototypes to validate understanding:\n\n```\nPrototype Levels:\n\nLow Fidelity (Paper\u002FWhiteboard):\n- Quick to create (minutes)\n- Good for: Overall flow, major screens\n- Validate: \"Is this the right approach?\"\n\nMedium Fidelity (Clickable mockups):\n- Moderate effort (hours)\n- Good for: Detailed interactions, UI layout\n- Validate: \"Does this workflow make sense?\"\n\nHigh Fidelity (Functional prototype):\n- Significant effort (days)\n- Good for: Complex interactions, performance\n- Validate: \"Will this actually work?\"\n```\n\n### Acceptance Criteria Review\n\nValidate with stakeholders before implementation:\n\n```\nReview Format:\n\n\"Here's my understanding of [feature]. Please correct me if I'm wrong.\"\n\n[Read each scenario aloud]\n\nQuestions:\n- \"Is this what you expected?\"\n- \"What did I miss?\"\n- \"What edge cases should we handle?\"\n- \"Is the priority right?\"\n\nDocument changes and get sign-off.\n```\n\n## Traceability\n\n### Traceability Matrix\n\nLink requirements to their sources and verification:\n\n```\n| Req ID | Description | Source | Priority | Status | Test Cases |\n|--------|-------------|--------|----------|--------|------------|\n| REQ-001 | User login | Stakeholder interview | Must | Approved | TC-001, TC-002 |\n| REQ-002 | Order history | User observation | Should | Draft | TC-015 |\n| REQ-003 | Export CSV | Sales team request | Could | Approved | TC-020 |\n```\n\n### Requirement States\n\nTrack requirement lifecycle:\n\n```\nStates:\n┌─────────┐     ┌──────────┐     ┌──────────┐     ┌────────────┐\n│ Draft   │────►│ Reviewed │────►│ Approved │────►│ Implemented│\n└─────────┘     └──────────┘     └──────────┘     └────────────┘\n                     │                                   │\n                     ▼                                   ▼\n                ┌──────────┐                      ┌──────────┐\n                │ Rejected │                      │ Verified │\n                └──────────┘                      └──────────┘\n```\n\n## Anti-Patterns\n\n| Anti-Pattern | Problem | Solution |\n|--------------|---------|----------|\n| **Solution First** | \"We need a dashboard\" | Ask \"Why?\" to find the real need |\n| **Assumed Obvious** | Undocumented \"common sense\" | Document everything explicitly |\n| **Gold Plating** | Adding unrequested features | Stick to documented requirements |\n| **Moving Baseline** | Requirements keep changing | Change control process |\n| **Single Stakeholder** | Missing perspectives | Identify all stakeholders |\n| **Technical Jargon** | Users don't understand | Use domain language |\n\n## Templates\n\n### Feature Request Template\n\n```markdown\n# Feature: [Name]\n\n## Problem Statement\n[What problem does this solve?]\n\n## User Stories\n- As a [role], I want [what] so that [why]\n\n## Acceptance Criteria\n- Given [context] when [action] then [outcome]\n\n## Out of Scope\n- [What this feature does NOT include]\n\n## Dependencies\n- [Other features or systems required]\n\n## Open Questions\n- [Unresolved issues needing discussion]\n```\n\n### Requirements Document Template\n\n```markdown\n# [Project Name] Requirements Specification\n\n## 1. Introduction\n### 1.1 Purpose\n### 1.2 Scope\n### 1.3 Definitions\n\n## 2. Overall Description\n### 2.1 Product Perspective\n### 2.2 User Classes\n### 2.3 Constraints\n\n## 3. Functional Requirements\n### 3.1 [Feature Area 1]\n### 3.2 [Feature Area 2]\n\n## 4. Non-Functional Requirements\n### 4.1 Performance\n### 4.2 Security\n### 4.3 Usability\n\n## 5. Appendices\n### A. Stakeholder Register\n### B. Traceability Matrix\n```\n\n## References\n\n- [Interview Question Bank](examples\u002Finterview-questions.md) - Questions by domain\n- [User Story Examples](examples\u002Fuser-stories.md) - Well-written story examples\n","# Requirements Elicitation Methodology\n\nSystematic techniques for transforming vague ideas into clear, testable specifications that align stakeholders and guide implementation.\n\n## When to Activate\n\n- Gathering requirements for new features\n- Clarifying vague or ambiguous requests\n- Resolving conflicting stakeholder needs\n- Documenting formal specifications\n- Creating user stories with acceptance criteria\n- Validating requirements before implementation\n\n## Elicitation Techniques\n\n### The 5 Whys\n\nDrill past surface requests to discover root needs:\n\n```\nSurface Request: \"We need a dashboard\"\n\nWhy 1: Why do you need a dashboard?\n→ \"To see our metrics in one place\"\n\nWhy 2: Why do you need to see metrics in one place?\n→ \"To identify problems quickly\"\n\nWhy 3: Why do you need to identify problems quickly?\n→ \"Because slow response affects customer satisfaction\"\n\nWhy 4: Why does customer satisfaction matter right now?\n→ \"We're losing customers and don't know why until it's too late\"\n\nWhy 5: Why don't you know until it's too late?\n→ \"We only see issues in monthly reports\"\n\nRoot Need: Real-time alerting for customer-impacting issues\n(Not just a dashboard - the dashboard was a solution, not the need)\n```\n\n### Concrete Examples\n\nTransform abstract requirements into specific, testable scenarios:\n\n| Abstract | Concrete |\n|----------|----------|\n| \"The system should be fast\" | \"Page loads in under 2 seconds on 3G\" |\n| \"Users should be able to search\" | \"Find orders by customer name, date range, or status\" |\n| \"It needs to be secure\" | \"All PII encrypted at rest, session timeout after 15 min inactive\" |\n| \"Good error handling\" | \"Network failures retry 3x with exponential backoff, then show offline mode\" |\n\n### Boundary Identification\n\nDefine what's explicitly in and out of scope:\n\n```\nFeature: User Registration\n\nIN SCOPE:\n✓ Email\u002Fpassword registration\n✓ Email verification\n✓ Password strength requirements\n✓ Terms of service acceptance\n\nOUT OF SCOPE:\n✗ Social login (Google, Facebook)\n✗ Two-factor authentication\n✗ Password recovery (separate feature)\n\nDEFERRED:\n◐ SSO integration (planned for Q3)\n◐ Biometric login (pending security review)\n```\n\n### Stakeholder Interviews\n\nStructured conversation to extract requirements:\n\n```\nInterview Structure (45 min):\n\n1. CONTEXT (10 min)\n   - What's your role in this project?\n   - What does success look like for you?\n   - What's driving this initiative?\n\n2. CURRENT STATE (10 min)\n   - How do you do this today?\n   - What works well?\n   - What are the pain points?\n\n3. DESIRED STATE (15 min)\n   - What would the ideal solution look like?\n   - Walk me through a typical scenario...\n   - What would make your job easier?\n\n4. CONSTRAINTS (5 min)\n   - What absolutely must be included?\n   - What's definitely out of scope?\n   - Any timeline or budget constraints?\n\n5. WRAP-UP (5 min)\n   - What haven't I asked that I should?\n   - Who else should I talk to?\n   - Can I follow up if I have questions?\n```\n\n### Observation and Shadowing\n\nWatch users perform tasks in their environment:\n\n```\nObservation Protocol:\n\nPREPARE:\n- Define what you're observing\n- Get permission to observe\n- Prepare note-taking template\n\nOBSERVE:\n- Note actions, not interpretations\n- Record workarounds and pain points\n- Note environmental factors\n- Time key activities\n\nDEBRIEF:\n- \"I noticed you did X, can you tell me more?\"\n- \"What would make that easier?\"\n- \"How often does this happen?\"\n\nDocument:\n┌─────────────────────────────────────────────────────────────┐\n│ Observation: Order Processing                               │\n├─────────────────────────────────────────────────────────────┤\n│ Action: Copied customer email from order to support tool    │\n│ Time: 15 seconds per order                                  │\n│ Frequency: ~50 orders\u002Fday                                   │\n│ Pain Point: Manual copy-paste, error-prone                  │\n│ Opportunity: Direct integration between systems             │\n└─────────────────────────────────────────────────────────────┘\n```\n\n## Requirement Documentation\n\n### User Story Format\n\n```\nFormat:\nAs a [role],\nI want [capability],\nSo that [benefit].\n\nComponents:\n- Role: Who benefits (be specific)\n- Capability: What they can do (action, not solution)\n- Benefit: Why it matters (business value)\n\nExample:\nAs a customer service representative,\nI want to see a customer's order history when they call,\nSo that I can resolve their issues without asking them to repeat information.\n```\n\n### Acceptance Criteria (Given-When-Then)\n\n```\nFormat:\nGiven [context\u002Fprecondition]\nWhen [action\u002Fevent]\nThen [expected outcome]\n\nExample:\nFeature: Order Cancellation\n\nScenario: Cancel order before shipping\nGiven an order in \"confirmed\" status\nAnd the order has not been shipped\nWhen the customer requests cancellation\nThen the order status changes to \"cancelled\"\nAnd the customer receives a cancellation confirmation email\nAnd the payment is refunded within 3-5 business days\n\nScenario: Cannot cancel shipped order\nGiven an order in \"shipped\" status\nWhen the customer requests cancellation\nThen the cancellation is rejected\nAnd the customer is directed to the returns process\n```\n\n### Edge Cases and Exceptions\n\nDocument what happens when things go wrong:\n\n```\nFeature: Password Reset\n\nHappy Path:\n- User requests reset → Email sent → User clicks link → Sets new password\n\nEdge Cases:\n| Scenario | Expected Behavior |\n|----------|-------------------|\n| Email not found | Show same success message (security) |\n| Link expired (>24h) | Show \"link expired\" with new reset option |\n| Link already used | Show \"link already used\" message |\n| Weak password | Show requirements, block submission |\n| Same as old password | Show error, require different password |\n| User locked out | Still send reset email (unlock flow) |\n```\n\n### Non-Functional Requirements\n\nDocument quality attributes:\n\n```\nNFR Template:\n┌─────────────────────────────────────────────────────────────┐\n│ Category: Performance                                        │\n├─────────────────────────────────────────────────────────────┤\n│ Requirement: Response Time                                   │\n│ Measure: 95th percentile page load time                     │\n│ Target: \u003C 2 seconds                                          │\n│ Context: Desktop browser, 4G connection                     │\n│ Priority: Must Have                                          │\n└─────────────────────────────────────────────────────────────┘\n\nCommon Categories:\n- Performance: Speed, throughput, latency\n- Scalability: Users, data volume, geographic distribution\n- Availability: Uptime, recovery time, disaster recovery\n- Security: Authentication, authorization, encryption\n- Usability: Accessibility, learnability, efficiency\n- Maintainability: Modularity, testability, documentation\n```\n\n## Stakeholder Management\n\n### Stakeholder Analysis\n\nIdentify and categorize stakeholders:\n\n```\nStakeholder Map:\n\n             High Influence\n                   │\n    ┌──────────────┼──────────────┐\n    │   Manage     │    Partner   │\n    │   Closely    │    With      │\n    │              │              │\nLow ├──────────────┼──────────────┤ High\nInterest          │              Interest\n    │   Monitor    │    Keep      │\n    │   Only       │    Informed  │\n    │              │              │\n    └──────────────┼──────────────┘\n                   │\n             Low Influence\n\nStakeholder Register:\n| Name | Role | Interest | Influence | Communication |\n|------|------|----------|-----------|---------------|\n| VP Sales | Sponsor | High | High | Weekly update |\n| Dev Team | Implementer | High | Medium | Daily standup |\n| Legal | Advisor | Low | High | As needed |\n```\n\n### RACI Matrix\n\nDefine roles for each requirement:\n\n```\nR = Responsible (does the work)\nA = Accountable (final decision maker)\nC = Consulted (provides input)\nI = Informed (kept updated)\n\n| Requirement | Product | Dev | Design | Legal |\n|-------------|---------|-----|--------|-------|\n| User stories | R,A | C | C | I |\n| UI mockups | C | I | R,A | I |\n| API contracts | C | R,A | I | I |\n| Privacy policy | C | I | I | R,A |\n```\n\n### Conflict Resolution\n\nWhen stakeholders disagree:\n\n```\nResolution Process:\n\n1. UNDERSTAND both positions\n   - \"Help me understand why X is important to you\"\n   - Identify underlying needs vs stated positions\n\n2. FIND COMMON GROUND\n   - What do both parties agree on?\n   - What's the shared goal?\n\n3. EXPLORE OPTIONS\n   - Can we do both? (phased approach)\n   - Is there a third option that addresses both needs?\n   - What's the minimum viable for each?\n\n4. ESCALATE if needed\n   - Present options with trade-offs\n   - Let decision-maker decide\n   - Document the decision and rationale\n\nExample:\nMarketing wants: Launch by Q1 with all features\nEngineering says: Can't do all features by Q1\n\nResolution: Launch Q1 with core features (MVP), Phase 2 in Q2\nDocumented: ADR-2024-03: MVP Scope Decision\n```\n\n## Validation Techniques\n\n### Requirements Review Checklist\n\n| Criterion | Question | Pass\u002FFail |\n|-----------|----------|-----------|\n| Complete | Is everything needed documented? | |\n| Consistent | Are there contradictions? | |\n| Correct | Does it match stakeholder intent? | |\n| Unambiguous | Is there only one interpretation? | |\n| Testable | Can we verify it's met? | |\n| Traceable | Can we link to business goal? | |\n| Feasible | Can it be implemented? | |\n| Prioritized | Is importance clear? | |\n\n### Prototype Validation\n\nUse prototypes to validate understanding:\n\n```\nPrototype Levels:\n\nLow Fidelity (Paper\u002FWhiteboard):\n- Quick to create (minutes)\n- Good for: Overall flow, major screens\n- Validate: \"Is this the right approach?\"\n\nMedium Fidelity (Clickable mockups):\n- Moderate effort (hours)\n- Good for: Detailed interactions, UI layout\n- Validate: \"Does this workflow make sense?\"\n\nHigh Fidelity (Functional prototype):\n- Significant effort (days)\n- Good for: Complex interactions, performance\n- Validate: \"Will this actually work?\"\n```\n\n### Acceptance Criteria Review\n\nValidate with stakeholders before implementation:\n\n```\nReview Format:\n\n\"Here's my understanding of [feature]. Please correct me if I'm wrong.\"\n\n[Read each scenario aloud]\n\nQuestions:\n- \"Is this what you expected?\"\n- \"What did I miss?\"\n- \"What edge cases should we handle?\"\n- \"Is the priority right?\"\n\nDocument changes and get sign-off.\n```\n\n## Traceability\n\n### Traceability Matrix\n\nLink requirements to their sources and verification:\n\n```\n| Req ID | Description | Source | Priority | Status | Test Cases |\n|--------|-------------|--------|----------|--------|------------|\n| REQ-001 | User login | Stakeholder interview | Must | Approved | TC-001, TC-002 |\n| REQ-002 | Order history | User observation | Should | Draft | TC-015 |\n| REQ-003 | Export CSV | Sales team request | Could | Approved | TC-020 |\n```\n\n### Requirement States\n\nTrack requirement lifecycle:\n\n```\nStates:\n┌─────────┐     ┌──────────┐     ┌──────────┐     ┌────────────┐\n│ Draft   │────►│ Reviewed │────►│ Approved │────►│ Implemented│\n└─────────┘     └──────────┘     └──────────┘     └────────────┘\n                     │                                   │\n                     ▼                                   ▼\n                ┌──────────┐                      ┌──────────┐\n                │ Rejected │                      │ Verified │\n                └──────────┘                      └──────────┘\n```\n\n## Anti-Patterns\n\n| Anti-Pattern | Problem | Solution |\n|--------------|---------|----------|\n| **Solution First** | \"We need a dashboard\" | Ask \"Why?\" to find the real need |\n| **Assumed Obvious** | Undocumented \"common sense\" | Document everything explicitly |\n| **Gold Plating** | Adding unrequested features | Stick to documented requirements |\n| **Moving Baseline** | Requirements keep changing | Change control process |\n| **Single Stakeholder** | Missing perspectives | Identify all stakeholders |\n| **Technical Jargon** | Users don't understand | Use domain language |\n\n## Templates\n\n### Feature Request Template\n\n```markdown\n# Feature: [Name]\n\n## Problem Statement\n[What problem does this solve?]\n\n## User Stories\n- As a [role], I want [what] so that [why]\n\n## Acceptance Criteria\n- Given [context] when [action] then [outcome]\n\n## Out of Scope\n- [What this feature does NOT include]\n\n## Dependencies\n- [Other features or systems required]\n\n## Open Questions\n- [Unresolved issues needing discussion]\n```\n\n### Requirements Document Template\n\n```markdown\n# [Project Name] Requirements Specification\n\n## 1. Introduction\n### 1.1 Purpose\n### 1.2 Scope\n### 1.3 Definitions\n\n## 2. Overall Description\n### 2.1 Product Perspective\n### 2.2 User Classes\n### 2.3 Constraints\n\n## 3. Functional Requirements\n### 3.1 [Feature Area 1]\n### 3.2 [Feature Area 2]\n\n## 4. Non-Functional Requirements\n### 4.1 Performance\n### 4.2 Security\n### 4.3 Usability\n\n## 5. Appendices\n### A. Stakeholder Register\n### B. Traceability Matrix\n```\n\n## References\n\n- [Interview Question Bank](examples\u002Finterview-questions.md) - Questions by domain\n- [User Story Examples](examples\u002Fuser-stories.md) - Well-written story examples\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Frequirements-elicitation",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill requirements-elicitation",{"tool":63,"command":64},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill requirements-elicitation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill requirements-elicitation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Frequirements-elicitation\u002FSKILL.md",true,[],[72,81,89,97,105,113],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":80},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":80},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":80},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":80},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":80},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]