For PMs: turn strategy into roadmaps, specs, sprints, and the metrics to prove it shipped.
Reach for this when you own a product line and need to move from strategy to shipped, measurable outcomes without switching tools for every artifact. It carries you across the full PM loop: set OKRs, build a roadmap leadership trusts, ground decisions in personas and user flows, hand engineering crisp specs and tickets, run the sprint, then read the analytics to see if it worked. The result is a product org aligned on outcomes instead of a feature list - and a paper trail that survives the next reorg.
Click to play with sound.
Arranged in the author's recommended order. Walk through them in sequence, or open any one on its own.
Turns product strategy into a themed Now/Next/Later roadmap with explicit trade-offs, confidence levels, and no committed dates beyond one quarter. Use when someone asks "build our product roadmap", "turn these priorities into a roadmap", "execs want committed ship dates for next year", or needs to communicate direction without over-promising. Do NOT use for company-wide annual operating plans - use annual-plan instead; for defining the goals a roadmap serves, use okr-builder; for scheduling work inside a sprint, use sprint-planning.
View skillWrites engineering design docs and RFCs that align a team before code - TL;DR, background, goals and explicit non-goals, quantified requirements, a concrete end-to-end design with failure modes, alternatives considered, rollout plan, and open questions surfaced at the top for reviewers. Use when an engineer asks "write a design doc for this feature", "turn my approach into an RFC", "reviewers keep asking why didn't you just X", or a project needs alignment before implementation. Do NOT use for designing the API contract itself - use api-design instead; for user-facing product documentation, use help-documentation.
View skill