Pm Prd
技能 已验证 活跃Generate 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".
Generate comprehensive and well-structured Product Requirements Documents, ensuring clarity, alignment, and adherence to best practices for product development.
功能
- Generate PRDs in four specialized modes (Full, Lightweight, Iteration, Migration)
- Enforces problem-first thinking and detailed requirements
- Integrates with domain and personal context for tailored output
- Automates quality checks for PRDs before final output
使用场景
- When needing to create a net-new feature specification
- When scoping sprint-level work with a lightweight spec
- When defining follow-ups or improvements on existing features
- When documenting requirements for regulatory or API migrations
非目标
- Generating full product strategy documents
- Acting as a project management tool for task assignment
- Replacing the need for design mockups or technical architecture documents
安装
请先添加 Marketplace
/plugin marketplace add marfoerst/the-pragmatic-pm/plugin install the-pragmatic-pm@the-pragmatic-pm质量评分
已验证类似扩展
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.
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.
Prepare Inspection Readiness
100Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.