PRD from messy notes
OfficialOfficial · updated Nov 4, 2026 · v1.0.1
Turns notes, Slack threads, and call notes into a PRD: problem with evidence, goals and non-goals, metrics, must/should/could requirements, and flagged gaps.
Sign up free to add this skill to your pod
You come back here after you sign in, and add it with one click.
When to use it
- You have scattered notes or a thread about a feature and need a PRD the team can build from
- A founder asks you to "write this up" after a call or whiteboard session
What you give it
- Notes, threads, transcripts, or quotes
- Target user (optional)
- Deadlines or metric targets (optional)
What you get
A Markdown PRD with problem, evidence, users, goals, non-goals, metrics table, prioritized requirements, open questions, risks, and gaps.
Changelog
- v1.0.1 · Nov 4, 2026 · Example: the Problem no longer says customers export files or share their login (the notes say neither) and lists how they work around it today as a gap; a second non-goal (no edit access for the accountant) meets the skill's own minimum of 2.
- v1.0.0 · Nov 4, 2026 · First release.
Sources
- What is MoSCoW Prioritization? (Agile Business Consortium) (2026-11-04)
- Assessing Product Opportunities - Silicon Valley Product Group (2026-11-04)
Related skills
- Spec review before build Reviews a PRD or spec before build for ambiguity, missing empty/loading/error/permission states, metrics, rollout, and a first-time user walk-through.
- User stories with acceptance criteria Turns a feature into user stories with Given/When/Then acceptance criteria, edge cases, out-of-scope notes, and an INVEST check per story.
- Feature prioritization with RICE Scores a backlog with RICE or ICE, shows the math per item, tests sensitivity, recommends a cut line for capacity, and flags dependencies.
- Decision record (decision log entry) Records a decision as a short log entry: the decision, context, options considered, why, who decided, the date, status, and a revisit trigger.