agentsclimarketplace

Plan product launch

Skill VRymarovich/product-launch-os/plugins/product-launch-os/skills/plan-product-launch

Codex plugin with reusable agent skills for product discovery, launch, SEO, sales, and growth

Install
npx -y skills add VRymarovich/product-launch-os --skill plan-product-launch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Plan a staged product or feature launch across readiness, audience, channels, assets, owners, timing, risks, support, rollback, and measurement. Use for launch plans, release campaigns, coordinated announcements, beta releases, feature launches, or go-to-market checklists.

SKILL.md

1.6 KB, 267 tokens by cl100k_base, as published. Nobody here has run it

Plan Product Launch

Coordinate a release as a sequence of evidence-producing stages rather than a single announcement day.

Workflow

  1. Read product context, release scope, technical readiness, store status, brand, SEO, content, sales, and metrics.
  2. Define the launch outcome and audience behavior, not just shipment.
  3. Choose the stage: internal, design-partner, beta, soft launch, public launch, or expansion.
  4. Build a readiness matrix covering product, QA, privacy, analytics, onboarding, support, store, website, messaging, content, sales, and rollback.
  5. Assign owner, deadline, dependency, status, and acceptance criteria to launch-critical items.
  6. Create channel-specific messages derived from one canonical launch narrative.
  7. Define launch-day monitoring, incident thresholds, rollback, and customer response.
  8. Define 24-hour, 7-day, and 30-day review points.
  9. Update docs/product/launch-plan.md and docs/product/roadmap.md.

Read references/launch-system.md for the staged checklist.

Guardrails

  • Do not schedule a public launch before distribution and support blockers are explicit.
  • Do not treat vanity reach as product success.
  • Never perform external posting or publication without authorization.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.