adrDocument architecture and product decisions using the Nygard ADR format — captures context, alternatives considered, and consequences so the team never asks 'why did we do it this way?' again. Use when making architecture decisions, choosing between technical approaches, selecting vendors, or any de
brainstorm-okrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
create-prdCreate a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
edge-casesSystematically identify error states, boundary conditions, and recovery paths for a feature using the BOUNDARY method — reduces post-launch defects by surfacing what specs miss. Use after writing a PRD, before sprint planning, during QA planning, or when reviewing acceptance criteria for completenes
job-storiesCreate job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.
meeting-prepPrepare for any PM meeting — 1:1s, stakeholder alignments, leadership reviews, and cross-functional planning sessions with structured talking points, anticipated questions, and success criteria. Use when preparing for a meeting, building an agenda, or anticipating stakeholder questions.
outcome-roadmapTransform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
pre-mortemRun a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identi
prioritizationUnified prioritization skill that adapts to what you're prioritizing: features (ICE/RICE/Opportunity Score), assumptions (Impact × Risk matrix + experiment design), backlog items (strategic alignment + effort), or general trade-offs. Includes reference to all 9 prioritization frameworks. Use when pr
release-notesGenerate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retroFacilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
solution-briefCreate a lightweight one-page solution pitch that summarizes the problem, proposed approach, alternatives considered, risks, success metrics, and effort estimate with a clear next-step recommendation (PRD / spike / kill / pivot). Serves as the decision gate between discovery and full requirements. U
sprint-planPlan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
stakeholder-mapBuild a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
stakeholder-updateCreate structured stakeholder updates, status reports, and executive summaries — weekly updates, quarterly reviews, and quick status messages with audience-calibrated detail. Use when writing a status update, preparing a progress report, creating an executive summary, or sharing project status.
summarize-meetingSummarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.
test-scenariosCreate comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
user-storiesCreate user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.
writerGeneral-purpose PM writing assistant for briefs, emails, status updates, Slack messages, proposals, and presentations — adapts tone and structure to audience. Use when drafting any PM communication, writing an email, preparing a brief, or polishing a message.
wwasCreate product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.