Product Requirements Document (PRD)
技能 已验证 活跃Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
To standardize and professionalize the creation of Product Requirements Documents, ensuring alignment among stakeholders and providing clear specifications for engineering handoff.
功能
- Creates comprehensive PRDs
- Defines goals and success metrics
- Outlines solutions and functional requirements
- Specifies scope boundaries (in/out/future)
- Includes technical considerations and risks
使用场景
- When specifying features, epics, or product initiatives for handoff
- When multiple teams need to coordinate on a shared deliverable
- When stakeholders need to approve scope before investment
- As reference documentation during development and QA
非目标
- Over-specifying implementation details
- Designing the system architecture
- Creating detailed user stories with acceptance criteria (this is a separate skill)
- Handling task dependencies or automated assignment rotation
工作流
- Summarize the Problem
- Define Goals and Success Metrics
- Outline the Solution
- Detail Functional Requirements
- Define Scope Boundaries
- Address Technical Considerations
- Identify Dependencies and Risks
- Propose Timeline and Milestones
实践
- Documentation
- Specification
- Product Management
安装
请先添加 Marketplace
/plugin marketplace add product-on-purpose/pm-skills/plugin install pm-skills@pm-skills-marketplace质量评分
已验证类似扩展
Measure Dashboard Requirements
100Specifies requirements for an analytics dashboard including metrics, visualizations, filters, and data sources. Use when requesting dashboards from data teams, defining KPI tracking, or documenting reporting needs.
Acceptance Criteria Generator
99Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.
Pm Prd
98Generate a Product Requirements Document (PRD) with four modes: Full PRD for net-new features, Lightweight Feature Spec for sprint-level work, Iteration/V2 Spec for follow-ups on shipped features, and Migration/Compliance Spec for regulatory or API migrations. Enforces problem-first thinking, leading + lagging metrics, non-goals, and testable acceptance criteria. Use when someone says "PRD", "product requirements", "feature spec", "write a spec", "requirements document", "what to build", "engineering spec", "technical requirements", "migration spec", "compliance spec", "V2 spec", or "iteration spec".
Feature Forge
98Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists. Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs, PRDs, acceptance criteria, or requirement matrices.
Agent Specification
95Agent skill for specification - invoke with $agent-specification
Teach Guidance
100Guide a person in becoming a better teacher and explainer. AI coaches content structuring, audience calibration, explanation clarity, Socratic questioning technique, feedback interpretation, and reflective practice for technical presentations, documentation, and mentoring. Use when a person needs to present technical content and wants preparation coaching, wants to write better documentation or tutorials, struggles to explain concepts across expertise levels, is mentoring a colleague, or is preparing for a talk or knowledge-sharing session.