Product Agent

PRD Writing

Write a product requirements doc where the problem statement is so clear the solution feels inevitable — problem-first, with non-goals and success metrics. Use when user needs a PRD, feature spec, or product brief. Do not use when only user stories are needed — use @file:user-story-writing; or when the item isn't prioritized yet — use @file:feature-prioritization.

Feature Prioritization

Rank features with a framework that forces an honest trade-off conversation and a real cut list — not a tidy ranked spreadsheet. Use when user needs prioritization, backlog ranking, trade-off analysis, or a "what do we build next" call. Do not use when the next step is communicating the roadmap — use @file:roadmap-communication; or gathering signal first — use @file:customer-feedback-synthesis.

Roadmap Communication

Build a customer/exec-facing roadmap that inspires direction without becoming a delivery contract — Now/Next/Later, themes over dates. Use when user needs a roadmap deck, QBR roadmap section, or strategic direction communication. Do not use when the need is shipped-feature notes — use @file:release-notes; or internal status — use @file:stakeholder-update.

Release Notes

Write release notes customers actually read — telling the story of a problem solved, sized to how big the release really is, with the breaking changes and required actions impossible to miss. Use when user needs release notes, a changelog, a "what's new," or patch notes. Do not use when the need is an internal status update (use @file:stakeholder-update), a full spec (use @file:prd-writing), or measuring how the release performed (use @file:metrics-analysis).

Customer Feedback Synthesis

Turn feedback noise into ranked signal by finding the problem under the request and weighting by segment, not volume. Use when user needs feedback synthesis, VOC insights, or theme identification. Do not use when the next step is choosing what to build — use @file:feature-prioritization; or competitive gaps — use @file:competitive-feature-analysis.

User Story Writing

Write user stories whose acceptance criteria QA can execute without asking a single question — Given/When/Then, INVEST-sized. Use when user needs user stories, acceptance criteria, or epic decomposition. Do not use when a full problem-framed PRD is needed — use @file:prd-writing; or when reviewing eng's spec — use @file:technical-spec-review.

Stakeholder Update

Write an internal status update that builds confidence by surfacing risks early and answering questions before they're asked — a trust instrument, not a reporting chore. Use when user needs an exec/board product update or project status. Do not use when the audience is customers — use @file:roadmap-communication; or it's a shipped-feature note — use @file:release-notes.

Competitive Feature Analysis

Find the feature gaps that actually lose deals and ignore the rest — not a parity spreadsheet. Use when user needs a feature comparison, competitive gap analysis, or capability mapping. Do not use when prioritizing which gaps to close — use @file:feature-prioritization; or pricing comparison — use @file:pricing-packaging.

Pricing Packaging

Design pricing and packaging that captures value and signals who the product is for — packaging is the hard part, not the number. Use when user needs a pricing model, tier design, or monetization analysis. Do not use when communicating pricing in a roadmap — use @file:roadmap-communication; or measuring pricing impact — use @file:metrics-analysis.

Beta Program

Design a beta as a learning program with falsifiable hypotheses and exit criteria that can say "don't ship" — not early access with a bug excuse. Use when user needs beta design, participant selection, or pre-GA validation. Do not use when the need is feedback analysis only — use @file:customer-feedback-synthesis; or GA notes — use @file:release-notes.

Metrics Analysis

Turn product metrics into a decision — start from "what would we change?" not "what happened?" Use when user needs metrics interpretation, feature performance review, or a product-health read. Do not use when synthesizing qualitative feedback — use @file:customer-feedback-synthesis; or marketing attribution — marketing owns that.

Technical Spec Review

Review an engineering spec through a product lens — answer one question, does this solve the PRD's problem? — without rubber-stamping or nitpicking. Use when user needs a spec review or PM perspective on a technical approach. Do not use when the need is code review (engineering's domain) or writing the spec's stories — use @file:user-story-writing.

Customer Persona

Build actionable customer and buyer personas that change targeting, messaging, and sales discovery — not posters for the office wall. Use when user needs ICP definition, named buyer-role persona, persona-based message variations, or segmentation that drives behavior. Do not use when broad market research is the need — use market-research instead.

Launch Planning

Orchestrate a product, feature, or pricing launch across every team — matching effort to market impact, translating capability into buyer value, and driving adoption, gated on product readiness and field enablement. Use when user needs launch strategy, GTM coordination, a launch timeline, go/no-go criteria, tier classification, or a cross-functional launch checklist. Do not use when positioning definition is the need — the launch plan consumes positioning, it doesn't author it.

Pricing Communication

Communicate pricing changes effectively across customers, sales, CSMs, and internal stakeholders — value-first, adequate notice, named escalation paths, no panic. Use when user needs to communicate a pricing change, sales talk tracks for pricing discussions, customer-facing pricing announcements, or pricing FAQ. Do not use when the need is pricing strategy definition or deal-specific negotiation.