A product team does more than build. Meetings need capturing, priorities shift, things break, new people join. This is the other half of the 51skills - the ones that don't map to a phase, because the work they cover doesn't happen in phases either.
/pm-stripeAlways names the one next thing to build, so nobody stalls waiting for direction./pm-feature-designTurns one backlog item into a build-ready spec the day before you code it./pm-feature-viabilityCatches a feature that isn't worth building before you spend a sprint on it./pm-meetingTurns a meeting into a written decision, not a memory everyone half-remembers differently./pm-onboardingHands a new hire the project's context instead of three days of Slack archaeology./pm-comms-charterSettles who needs to know what, before the miscommunication happens./pm-root-causeFinds the real reason a metric dropped, not the first plausible guess./pm-stress-testGrills your pitch like a hostile investor would, while a wrong answer still costs nothing./pm-auditCatches drift between what the docs say and what the product actually does./pm-prioritizeRe-scores the backlog the moment priorities shift, without starting over./pm-glossaryOne definition per term, so "active user" means the same thing in every meeting./pm-reconcile-statusShows exactly how far a reconciliation got, so nobody re-starts work already done./pm-prototypeA clickable mock before a single line of production code, for the moment an idea needs to be seen, not described./pm-diagramsTurns a tangled explanation into a diagram everyone reads the same way.Seven phases get you from idea to shipped. These skills are what you reach for after - and sometimes instead, the moment something outside the phase sequence is what's actually on fire.
Full skill catalog in the docs →