Product Manager PRD Workflow

Problem to Solve

Product requirements are often scattered across chats, verbal notes, and fragmented documents, making PRDs prone to missing fields, unclear priorities, and absent flow logic. This skill targets the handoff from requirement description to deliverable documentation, turning requirement capture, confirmation, diagrams, demos, and Word export into explicit steps.

How It Works

It progresses in stages:
- Structured requirements: prompts for features, target users, and use cases, then produces a table with fields such as presentation format, functional module, feature description, and priority.
- Multi-turn confirmation: supports add, delete, modify, and review before moving forward.
- Optional diagram: generates a main business logic flow in Mermaid for review.
- Optional demo and document: outputs an HTML demo or creates a .docx PRD using scripts/generate_prd_docx.py.

Boundaries

It is useful for requirement organization, first-draft PRDs, and quick demos, but it does not replace competitor research, usability testing, or full visual design. Output quality depends on the input; if business constraints, permission models, or data definitions are missing, they should be completed during confirmation.