Guide product managers through structured PRD creation across eight phases.
npx skills add https://github.com/ch-m-n/dotfile --skill prd-development-ch-m-n
Please help me install this Agent Skill. Skill: prd-development Source: https://github.com/ch-m-n/dotfile/tree/main/opencode/skills/prd-development Command: npx skills add https://github.com/ch-m-n/dotfile --skill prd-development-ch-m-n
This workflow helps product managers stop collecting scattered discovery notes and Slack threads and instead generate a comprehensive PRD that aligns stakeholders, provides engineering context, and keeps scope transparent.
Start by using this workflow to outline the executive summary, problem statement, personas, success metrics, and user stories for the next major initiative.
High-intent search queries and answers about installing and using this skill.
To turn scattered discovery notes into a unified PRD, use a structured workflow that synthesizes research, personas, and strategy into a comprehensive requirements document for engineering handoff. It orchestrates problem framing, solution overviews, and user stories across eight phases.
A product requirements document for engineering handoff should include an executive summary, problem framing, personas, strategy, solution overview, success metrics, requirements, and scope controls. This ensures stakeholders align and engineering receives necessary context.
Yes, you can use this PRD workflow for a major AI recommendation feature. It guides product managers to document evidence, strategy, solution intent, metrics, user stories, dependencies, and risks before engineering handoff across eight structured phases.
To define success metrics and user stories for a new product initiative, follow a structured PRD creation process that orchestrates metric definition and user-story breakdowns. This ensures requirements align with strategic context and transparent scope controls.
Yes, this product management workflow supports component orchestration by pointing to supporting skills like problem-statement templates, persona templates, epic hypotheses, and user-story breakdowns to enrich each PRD section.
The best way to keep scope transparent when creating a product requirements document is to define out-of-scope items explicitly during the workflow. This structured approach ensures stakeholders understand boundaries and prevents scope creep during engineering handoff.
Prorise-coolGuide product managers through structured PRD creation using a 10-section template.
cassioalexandreValidate implementation readiness by checking PRD completeness and epic/story coverage.
tabooesArticulate user-centered problem statements from persona and template inputs.
jayhjenkinsGuide an interactive eight-phase session to create and validate Product Requirements Documents.
