pm-write-spec

What problem does it solve?

Product teams and stakeholders often have vague ideas, scattered feedback, or feature requests that lack structure, measurable goals, and clear acceptance criteria. This Skill converts informal inputs into a scannable, implementation-ready product requirements document so teams can align quickly and reduce rework.

Core Features & Use Cases

• Structured PRD generation: Produces a complete PRD with problem statement, goals, non-goals, user stories, categorized requirements (P0/P1/P2), success metrics, open questions, and timeline considerations.
• Context-aware sourcing: Prompts for essential context and integrates available research, tickets, or designs when connected, falling back to user-provided details when not available.
• Scoped delivery & iteration: Breaks large asks into phased specs, clarifies acceptance criteria in Given/When/Then or checklist format, and supports follow-up artifacts like design briefs or ticket breakdowns.
• Use case: Turn a support ticket or stakeholder request into a prioritized, testable spec with measurable success metrics and a recommended phase 1 scope.

Quick Start

Write a product specification for "SSO support" that defines the problem, three measurable goals, P0 requirements with acceptance criteria, and a suggested rollout timeline.