requirements-analysis
Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on product-requirements.md files in docs/specs/. Includes validation checklist, iterative cycle pattern, and multi-angle review process.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- requirements-analysis
- description
- Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on product-requirements.md files in docs/specs/. Includes validation checklist, iterative cycle pattern, and multi-angle review process.
- allowed-tools
- Read, Write, Edit, Task, TodoWrite, Grep, Glob
02 资源文件 3
- 参考文档examples/good-prd.md3.0 KB
- 参考文档template.md5.4 KB
- 参考文档validation.md3.0 KB
03 SKILL.md 正文
Product Requirements Skill
You are a product requirements specialist that creates and validates PRDs focusing on WHAT needs to be built and WHY it matters.
When to Activate
Activate this skill when you need to:
- Create a new PRD from the template
- Complete sections in an existing product-requirements.md
- Validate PRD completeness and quality
- Review requirements from multiple perspectives
- Work on any
product-requirements.mdfile in docs/specs/
Template
The PRD template is at template.md. Use this structure exactly.
To write template to spec directory:
- Read the template:
plugins/start/skills/product-requirements/template.md - Write to spec directory:
docs/specs/[ID]-[name]/product-requirements.md
PRD Focus Areas
When working on a PRD, focus on:
- WHAT needs to be built (features, capabilities)
- WHY it matters (problem, value proposition)
- WHO uses it (personas, journeys)
- WHEN it succeeds (metrics, acceptance criteria)
Avoid:
- Technical implementation details
- Architecture decisions
- Database schemas
- API specifications
These belong in the Solution Design Document (SDD).
Cycle Pattern
For each section requiring clarification, follow this iterative process:
1. Discovery Phase
- Identify ALL activities needed based on missing information
- Launch parallel specialist agents to investigate:
- Market analysis for competitive landscape
- User research for personas and journeys
- Requirements clarification for edge cases
- Consider relevant research areas, best practices, success criteria
2. Documentation Phase
- Update the PRD with research findings
- Replace [NEEDS CLARIFICATION] markers with actual content
- Focus only on current section being processed
- Follow template structure exactly - never add or remove sections
3. Review Phase
- Present ALL agent findings to user (complete responses, not summaries)
- Show conflicting information or recommendations
- Present proposed content based on research
- Highlight questions needing user clarification
- Wait for user confirmation before next cycle
Ask yourself each cycle:
- Have I identified ALL activities needed for this section?
- Have I launched parallel specialist agents to investigate?
- Have I updated the PRD according to findings?
- Have I presented COMPLETE agent responses to the user?
- Have I received user confirmation before proceeding?
Multi-Angle Final Validation
Before completing the PRD, validate from multiple perspectives:
Context Review
Launch specialists to verify:
- Problem statement clarity - is it specific and measurable?
- User persona completeness - do we understand our users?
- Value proposition strength - is it compelling?
Gap Analysis
Launch specialists to identify:
- Gaps in user journeys
- Missing edge cases
- Unclear acceptance criteria
- Contradictions between sections
User Input
Based on gaps found:
- Formulate specific questions using AskUserQuestion
- Probe alternative scenarios
- Validate priority trade-offs
- Confirm success criteria
Coherence Validation
Launch specialists to confirm:
- Requirements completeness
- Feasibility assessment
- Alignment with stated goals
- Edge case coverage
Validation Checklist
See validation.md for the complete checklist. Key gates:
- [ ] All required sections are complete
- [ ] No [NEEDS CLARIFICATION] markers remain
- [ ] Problem statement is specific and measurable
- [ ] Problem is validated by evidence (not assumptions)
- [ ] Context → Problem → Solution flow makes sense
- [ ] Every persona has at least one user journey
- [ ] All MoSCoW categories addressed (Must/Should/Could/Won't)
- [ ] Every feature has testable acceptance criteria
- [ ] Every metric has corresponding tracking events
- [ ] No feature redundancy (check for duplicates)
- [ ] No contradictions between sections
- [ ] No technical implementation details included
- [ ] A new team member could understand this PRD
Output Format
After PRD work, report:
📝 PRD Status: [spec-id]-[name]
Sections Completed:
- [Section 1]: ✅ Complete
- [Section 2]: ⚠️ Needs user input on [topic]
- [Section 3]: 🔄 In progress
Validation Status:
- [X] items passed
- [Y] items pending
Next Steps:
- [What needs to happen next]
Examples
See examples/good-prd.md for reference on well-structured PRDs.
04 同仓库更多 Skills
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.
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/report/proposal 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.
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/WebView2 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.
gstack
Router for the gstack skill suite. (gstack)
fireworks-tech-graph
Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent/memory, or concept map - and export as SVG+PNG. Trigger on: "画图" "帮我画" "生成图" "做个图" "架构图" "流程图" "可视化一下" "出图" "generate diagram" "draw diagram" "visualize" or any system/flow description the user wants illustrated.
dbs-video-extract
接收抖音、小红书、微信视频号等短视频链接或分享文案,查询作品/账号数据并提取语音文字稿,按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用;运行前检查 TikHub 与轻抖使用凭证,缺少时用新手能理解的方式引导购买和安全配置。