Results for “product-plan”

Create a minimalist marketing plan focused on building an audience through free, authentic content. Use when someone has product-market fit (~100 customers) and wants to scale through marketing or needs a content strategy.

Structures user research — planning sessions, synthesizing findings, and translating insights into product decisions. Use when planning user interviews, analyzing research data, creating personas or journey maps, or turning qualitative feedback into structured recommendations.

Write an implementation plan from an approved architecture and MVP scope. Use when the team needs milestones, workstreams, dependency ordering, acceptance criteria, and execution sequencing that connect product intent to shippable engineering work.

Turns a raw idea into four linked planning files through a five-phase pipeline: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with kill criteria.

Create a go-to-market strategy covering marketing channels, messaging, success metrics, and launch timeline for product launches or new market entry.

Use when the team needs pricing, packaging, free-tier, trial, usage metering, or business-model guidance for a software product. Trigger on requests to design how the product should make money or control value access.

Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

Prepare safe production launches — pre-launch checklist, monitoring, staged rollout, and rollback. Load when deploying to production, releasing a major change, opening beta access, or the user asks for a launch checklist, go-live plan, rollout strategy, or rollback plan. Not for local-only prototypes. Pairs with ci-cd-and-automation and app-security-hardening.

Plan the frontend application structure for a product or feature. Use when the team needs route structure, feature modules, state boundaries, design-system needs, and frontend delivery sequencing based on defined screens and flows.

Comprehensive go-to-market strategy and launch execution skill. Use when planning a product launch, feature announcement, market entry, or release strategy. Activates for: go to market, GTM, product launch, launch strategy, launch plan, launch execution, launch marketing, GTM playbook, launch readiness, technical launch, beta launch, early access, waitlist, Product Hunt, feature release, announcement, how do I launch this, launch checklist, we're about to ship, market entry, startup GTM, PLG vs sales-led, GTM motion, launch marketing pack, press outreach, developer product launch.

Takes a high-level feature from an Epic and generates a detailed Product Requirements Document (PRD) in Markdown, covering goals, user stories, requirements, and acceptance criteria.

Agent profile for prioritize product scope, user outcomes, MVP slices, roadmap tradeoffs, and launch criteria. Use when Codex needs a specialist agent perspective for planning, implementation, review, debugging, validation, or handoff in this domain.

Create a go-to-market strategy covering marketing channels, messaging, success metrics, and launch timeline. Use when planning a product launch, creating a GTM plan from scratch, or defining a launch strategy for a new market.

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

Plan customer discovery interviews with the right goal, segment, constraints, and method for problem validation, churn research, or new product ideas.

Use this skill for pricing pages, onboarding, activation flows, plan comparison, product-led growth UX. Trigger when the task involves ui/ux work related to Pricing Onboarding UX, production implementation, audits, debugging, strategy, or validation.

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. (gstack)

Create 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.

Design an application database schema from product flows and backend responsibilities. Use when the team needs core entities, relationships, lifecycle fields, indexes, audit needs, tenancy boundaries, and migration-minded schema planning for an MVP or production system.

Create 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.

Plan screens, views, and page responsibilities for a product flow. Use when user journeys already exist and the team needs a screen inventory, screen purpose, key states, and component-level responsibilities without jumping into visual styling too early.

Analyzes an app from video, screenshots, or description, then generates implementation stories in dependency order.

Shape a rough product or project idea into a scoped brief before customer discovery, market research, specifications, UX, UI, or implementation planning

Build the PRINCE2 Initiating a Project pack: project initiation documentation, business case, project plan, controls, management approaches, product descriptions, and baseline decisions.

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers.

COO planning lead. Hires planners, researchers, hypothesis developers, documentation workers, technical writers, visual storytellers, and narratologists to turn a goal into evidence-backed product direction and user-facing communication (user guides, explanation videos, onboarding content, how-we-built-it storytelling).

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

Creates an outcome-backed product strategy memo from an Ideal Customer Profile markdown file, pasted ICP notes, discovery artifacts, product context, or PRD context. Use when asked to create product strategy, convert an UX Discovery and ICP into strategy, define vision-to-outcome strategy, turn discovery into strategic bets, clarify target customer outcomes, evaluate roadmap strategy, or avoid feature-factory planning.

Prepare PRINCE2 Closing a Project material: product acceptance, end project report, lessons report, benefits review plan, handover, follow-on actions, and closure recommendation.

Use when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March notification, post-acceptance artifact evaluation, PACMPL production, and the June conference, with owners for each deliverable.

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

Design and improve product user onboarding (first-time user experience) to drive activation and early retention. Produces an Onboarding & Activation Pack (aha moment spec, first 30 seconds + first mile plan, onboarding journey map, experiment backlog, measurement plan). Use for Growth teams.

Expert product analytics advisor for Senior PMs. Use when defining success metrics for a PRD, designing an A/B experiment, setting up an analytics tracking plan, analyzing post-launch impact, or when data exists but there's no clarity on what to measure. Produces structured metrics frameworks that connect to product decisions, not dashboards.

Full-cycle AI coding skill: plans, builds, tests, lints, fixes bugs, and writes production-grade docs. Auto-detects project state and adapts its 8-phase pipeline.

Full-cycle AI coding skill: plans, builds, tests, lints, fixes bugs, and writes production-grade docs. Auto-detects project state and adapts its 8-phase pipeline.