pm-os-marketplace

The Problem Framer is the first specialist to engage on any product work at Headout. Use this skill whenever a PM has a vague idea, a half-formed brief, a Slack thread to untangle, or a gut feeling that something should be built. It transforms fuzzy inputs into a sharp, structured problem frame that every other specialist (Spec Writer, Data Analyst, Prototype Builder) can work from. Trigger this skill for inputs like: "we should improve X", "users are dropping off at Y", "can we do something about Z", "here's a thread from Atish", "I want to build a feature for...", or any product idea that hasn't yet been turned into a problem statement. Also trigger when a PM is stuck on how to frame a problem or wants a gut-check on whether they're solving the right thing. Output: A structured Problem Frame doc saved to the working folder.

The Idea Generator is the brainstorming specialist for Headout's PM OS. Engage after a Problem Frame is complete — or directly when a PM has a clear problem statement and wants to explore the solution space rigorously before committing to a direction. Acts as a high-fidelity thought partner: builds deep context through a multi-round interview (current state, constraints, prior attempts, platform nuances), maps the solution space into 2-4 strategic themes before generating any ideas, then produces specific ideas within each theme. Trigger for: "what are the ways we could solve this", "brainstorm approaches to X", "what should we build for this problem", "explore the solution space", "I have a problem frame and want ideas", "ideate on this", "what directions could we go", or any request to generate solution directions after a problem has been framed. Output: a structured Idea Brief.

The Data Analyst specialist for Headout's PM OS. Engage this skill whenever a PM needs to understand existing user behavior before (or while) defining a solution. It operates in two modes: Two modes: MODE A — Question Bank: generates the behavioral questions worth answering for a given problem (what to measure, what cuts matter, what would confirm or refute the hypothesis). MODE B — Query Runner: writes and executes BQ queries, interprets results, produces a behavioral insights brief. Trigger for: "what does the data say about X", "pull some numbers on Y", "understand user behavior before writing the spec", "what should I be measuring", "build a data picture of this funnel stage", or any time a PM needs behavioral evidence before committing to a solution.

The L1 Reviewer is the quality gate for all product specs at Headout before they reach Atish. Use this skill to review any PRD, spec, or requirements document for completeness, logical soundness, scenario coverage, metric clarity, and design coherence. Structured critique, not a polish pass. Rejects incomplete specs with specific, actionable failure reasons. A passing spec is ready for Atish. A failing spec returns to the PM with exactly what needs fixing. Trigger for: "review this PRD", "is this spec good enough", "L1 check", "review before I send to Atish", or whenever the Spec Writer finishes a draft. Checks both the LOGIC layer (scenario coverage, metric rigor, AC quality) and the DESIGN layer (design coherence, prototype alignment).

The Experiment Designer specialist for Headout's PM OS. Use this skill when a feature or change needs to be validated via an A/B test or controlled experiment before full rollout. It designs the experiment end-to-end: hypothesis, variants, user assignment, sample size, guardrails, measurement window, and the BigQuery/Statsig setup needed to track results. This skill is conditional — not every feature needs a formal experiment design. Use it when the PM says "we want to A/B test this", "how do we measure if this works", "design an experiment for X", "what's our holdout strategy", "help me think through the experiment setup", or when a spec includes an experiment as its validation method. The Experiment Designer works with Headout's experimentation infrastructure: Statsig for assignment and feature flags, BigQuery for outcome measurement, Mixpanel for behavioral signals, and Delphi (#ask-delphi) for ad hoc queries.

The PM Orchestrator is the central brain of Headout's PM OS. Use this skill when a PM has any product work to do and isn't sure which specialist to engage, wants a recommended workflow for their specific problem, or wants the full product cycle run end-to-end. Reads the problem, assesses what stage the PM is at, recommends which specialists to engage and in what order, and manages context passing between each stage. Trigger for: "where do I start with X", "run the full product cycle", "what should I do with this idea", "help me figure out the process", any vague brief needing routing, or any request that spans multiple specialists. When in doubt about which specialist to call, call the Orchestrator first.

The Prototype Builder specialist for Headout's PM OS. Use this skill whenever a product change involves a user-facing experience update — a new flow, a redesigned page, a new component, a changed interaction — and the PM or team needs to visualize what it should look and feel like before writing a full spec or handing to design. Two sequenced modes: MODE A — Journey Map (annotated user journey: every screen state, decision point, edge case, interaction). MODE B — HTML Prototype (working, clickable prototype from the journey map). Always run A before B. Trigger for: "what should this flow look like", "mock up the UX", "I want to see how this works before writing the spec", "build a prototype of X", "walk me through the user journey", "something to show the design team", or any feature involving a user-facing experience change.

The Spec Writer specialist for Headout's PM OS. Use this skill to write a full, production-ready PRD for any feature, experiment, or product change at Headout. This is not a template filler — it is a deliberate, scenario-forcing, hypothesis-anchored spec writer that produces documents detailed enough for an engineering agent (Cursor / Plato) to implement from and rigorous enough to pass Atish's L1 review gate. Trigger this skill whenever a PM needs to write a spec, PRD, or requirements doc. Also trigger when a PM says "I want to document this feature", "can you write up the requirements for X", "help me write a PRD", or when a Problem Frame + any additional inputs (data insights, prototype) are ready to be turned into a formal spec. The Spec Writer prefers a Problem Frame as input. If none exists, the skill will run a compressed problem-framing pass before writing — it never writes a spec without first establishing why we're doing this, what the objective is, and how success will be measured. The output follows Headout's standard PRD template (Problem Alignment → Solution → Execution Plan → Open Questions → Working Log → Change Log).

The Implementation Planner specialist for Headout's PM OS. Use this skill to convert an approved PRD and design into a detailed, engineer-ready (and coding-agent-ready) implementation plan. It produces a structured task breakdown with clear sequencing, per-task acceptance criteria, API contracts, state transitions, dependencies, and rollout strategy. The output of this skill is designed to be directly usable by Cursor (or any AI coding agent) as the authoritative source of truth for what to build and in what order. Trigger this skill when a PM says "write the implementation plan for this", "break this into engineering tasks", "create the tech breakdown", "what's the build plan", "prepare this for engineering handoff", or when a spec has passed L1 review and is ready for engineering pickup. The Implementation Planner requires a spec (ideally post-L1 review) as input. It can also incorporate a prototype and data insights brief if available.