Launch Readiness
Run a go/no-go launch-readiness review for a product or feature release across all functions (product, eng, QA, design, docs, support, marketing, legal, ops). Use when the user says "launch readiness", "go/no-go", "are we ready to ship/launch", "release checklist", or needs a cross-functional sign-off before shipping.
Stakeholder Comms Plan
Build a stakeholder map and a communication plan — who needs what information, at what cadence, through which channel. Use when the user says "stakeholder map", "communication plan", "comms plan", "who do we need to keep informed", "RACI for comms", or needs to plan how to keep stakeholders aligned across a program.
Roadmap Planning
Turn goals, themes, and initiatives into a structured product roadmap — now/next/later or quarterly — with outcomes, rough sizing, dependencies, and confidence. Use when the user says "build a roadmap", "plan the quarter/half/year", "prioritize our initiatives", "what should we work on next", or needs to sequence work against objectives.
Estimation Sizing
Facilitate estimation and turn sizes into a credible delivery forecast — T-shirt sizes or story points, assumptions, and a range rather than a false-precision date. Use when the user says "estimate this", "size these stories", "how long will this take", "story points", "give me a delivery range", or needs to convert scope into a defensible timeline.
Dependency Mapping
Map cross-team and external dependencies for a project — what's needed, from whom, by when — and identify the critical path and at-risk handoffs. Use when the user says "map dependencies", "what are we blocked on", "cross-team dependencies", "critical path", or needs to coordinate handoffs across teams or vendors.
Sprint Planning
Plan a sprint or iteration — sprint goal, available capacity, committed scope, and risks — from a backlog. Use when the user says "plan the sprint", "sprint planning", "what should we commit to this iteration", "groom the backlog into a sprint", or needs to turn priorities + capacity into a realistic commitment.
Status Report
Write a concise project or program status report with an overall RAG (red/amber/green) health rating, progress since last update, what's next, risks/blockers, and explicit asks. Use when the user says "write a status report", "weekly update", "status update", "where are we on X", or needs a stakeholder-ready progress summary.
Prd Review
Review a product requirements document (PRD) or spec against a quality checklist and surface gaps, ambiguities, and risks before engineering starts. Use when the user says "review this PRD", "is this spec ready", "critique my requirements", "PRD checklist", or shares a doc and wants it pressure-tested before build.
Exec Summary
Distill a detailed program update, document, or set of notes into a one-screen executive summary written for leadership — headline, status, key points, and decisions needed. Use when the user says "exec summary", "summarize for leadership", "TL;DR for the VP", "make this executive-ready", or needs to compress detail into a decision-focused brief.
Okr Tracking
Draft and track OKRs — objectives with measurable key results, current values, and confidence/health. Use when the user says "write OKRs", "set objectives and key results", "track our OKRs", "quarterly goals", "are we on track for our KRs", or needs to define or check progress on measurable goals.
Raid Log
Create and maintain a RAID log — Risks, Assumptions, Issues, and Dependencies — for a project or program. Use when the user says "RAID log", "risk register", "track our risks/assumptions/issues/dependencies", "log a new risk", or needs a structured way to track and review threats and open items.
Retrospective
Facilitate and write up a team retrospective — what went well, what didn't, and owned, time-bound action items. Use when the user says "run a retro", "retrospective", "sprint retro", "project post-completion review", "lessons learned", or wants to turn raw retro notes into a structured summary with follow-ups.
Program Health Dashboard
Assemble a one-page program health snapshot across multiple workstreams — RAG status, milestones, top risks, dependencies, and metrics in a single scannable view. Use when the user says "program dashboard", "program health", "portfolio status", "one-pager across workstreams", "roll up all the projects", or needs an at-a-glance view of a multi-stream program.
Decision Log
Capture decisions in a durable, searchable log — the decision, context, options considered, rationale, owner, and date. Use when the user says "log this decision", "decision record", "ADR", "document what we decided", "decision log", or wants to record why a choice was made so it isn't relitigated later.
Capacity Planning
Model team capacity against committed and planned demand to spot over-allocation and forecast what can realistically be delivered. Use when the user says "capacity planning", "do we have bandwidth", "are we over-allocated", "headcount vs. demand", "can we take on X", or needs to balance workload against available people.
Escalation
Draft a clear, professional, unemotional escalation — the problem, impact, what's been tried, and a specific ask with a deadline. Use when the user says "escalate this", "write an escalation", "I need to raise this to leadership", "we're blocked and need help", or needs to ask for intervention without sounding alarmist or blaming.
Release Notes
Write audience-appropriate release notes from a changelog, list of merged PRs, or feature list — grouped by type, in user-benefit language. Use when the user says "write release notes", "changelog", "what's new", "announce this release", or wants to turn a list of changes into customer- or internal-facing notes.
Project Charter
Draft a project or program charter for a kickoff — problem statement, goals, scope (in/out), success metrics, stakeholders, milestones, and risks. Use when the user says "write a charter", "kick off a project", "create a project brief", "we're starting a new initiative", or needs a one-page alignment doc before work begins.
Postmortem
Run a blameless postmortem / incident review — timeline, impact, root cause analysis, and corrective actions. Use when the user says "postmortem", "incident review", "RCA", "root cause analysis", "what happened with the outage", or wants to turn an incident into a structured, blameless writeup with preventive actions.