Analyze requirements, prioritize work and roadmaps, and record product decisions.
The PM's four daily crafts, each with a re-runnable procedure. Prioritization: feed support tickets, sales blockers, technical debt and strategy into one input sheet, score with RICE, then read the portfolio — quick wins versus big bets, effort piled onto a few items, strategic gaps — and draft the roadmap from it. Interviews: transcripts in, theme-clustered findings out, every conclusion carrying quotes you can point back to. PRDs: start from the bundled templates and fill goals, scope, non-goals and metrics from your discovery work.
Input templates and scoring formulas ship in the package, so identical inputs produce identical scores — ranking disputes settle back into the numbers instead of into volume.
Outputs are reviewable workspace documents: score tables, interview syntheses, roadmaps and PRD drafts. For writing specs of systems that already exist, its companion Code→PRD covers the reverse direction.
Examples describe the request and the shape of the expected deliverable; they are not completed run results.
Score these 22 requests from support tickets and CRM on the RICE template; cite the basis for every reach number, then give me a quick-wins list and flag any XL pile-up.
A sourced score table, the ranking, and a portfolio-analysis summary.
Synthesize these four interview transcripts: per theme show occurrence count, a representative quote, and which roadmap items it touches.
A synthesis document: a theme-by-evidence matrix with quotes pointing back to transcript locations.
iOS · Android
iOS
Android
MIT
MIT (root LICENSE)
The pinned skill subtree and shipped references were audited; full applicable license and per-file adaptation/asset notes are preserved under references/licenses/ and references/PROVENANCE.md.
Publication commit 25e07dbeeb, audited source 84c524b6fb; catalog digest iOS 46196ba57ed7… · Android 16de89d019e2….
Version records ship with the signed catalog; the target and released versions are shown below.
