agentsclimarketplace

Manage product lifecycle

Skill VRymarovich/product-launch-os/plugins/product-launch-os/skills/manage-product-lifecycle

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

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

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

Coordinate a software product across discovery, implementation, brand, distribution, SEO, content, launch, sales, and growth. Use when the user asks what to do next, requests a product roadmap or full-project assessment, wants several product disciplines coordinated, or invokes Product Launch OS without naming a narrower workflow.

SKILL.md

2.4 KB, 399 tokens by cl100k_base, as published. Nobody here has run it

Manage Product Lifecycle

Treat product work as a connected system. Preserve alignment between what is built, what is promised, how it is distributed, and how success is measured.

Workflow

  1. Locate the product context, preferring docs/product/. If it is missing, invoke or follow initialize-product.
  2. Inspect the repository, product documents, open work, release state, website, distribution assets, and available metrics.
  3. Classify the current bottleneck:
    • unclear problem or audience → validate-product-idea
    • Chrome extension implementation or architecture → build-chrome-extension
    • other implementation work → use the repository's native implementation workflow
    • store submission or update → prepare-cws-release
    • inconsistent identity or messaging → create-brand-system
    • discoverability or organic acquisition → plan-seo
    • editorial execution → create-content-plan
    • coordinated release → plan-product-launch
    • conversion or outreach → create-sales-materials
    • funnel measurement or experimentation → analyze-growth
  4. Rank candidate work by expected impact, evidence strength, urgency, effort, and reversibility.
  5. Select one primary workflow. Use additional workflows only when they are true dependencies.
  6. Update docs/product/roadmap.md and docs/product/decisions.md when priorities materially change.

Operating rules

  • Separate repository evidence, user-provided facts, assumptions, and unknowns.
  • Do not manufacture customer research, rankings, revenue, conversion rates, or store status.
  • Prefer the smallest experiment or deliverable that resolves the current uncertainty.
  • Keep project-specific facts outside the plugin.
  • Read references/lifecycle-map.md when assessing the whole product.

Output

Lead with the current bottleneck, recommended workflow, and concrete next deliverable. Include dependencies, evidence gaps, success criteria, and files that should be updated.

Gives 0 of the 12 instructions most product growth skills give in 399 tokens

Counted across 728 of the 1,010 authors here whose files we hold, read 2026-08-06

  • read product marketing context before asking questionsin 24 of 728, across 15 files
  • define the ideal customer profilein 21 of 728, across 3 files
  • document a rollback plan before deploymentin 21 of 728, across 12 files
  • analyze the codebase to understand the productin 19 of 728, across 1 file
  • ask clarifying questions about the value propositionin 19 of 728, across 1 file
  • search for companies matching the criteriain 19 of 728, across 1 file
  • look for signals of immediate needin 19 of 728, across 1 file
  • assign a fit score from one to tenin 19 of 728, across 1 file
  • identify the target decision maker rolein 19 of 728, across 1 file
  • suggest a personalized contact strategyin 19 of 728, across 1 file
  • provide conversation starters for outreachin 19 of 728, across 1 file
  • format results in a scannable markdown templatein 19 of 728, across 1 file

Said here and by no other author read

  • locate product context before proceeding
  • inspect repository documents assets and metrics
  • classify the current bottleneck
  • rank candidate work by impact effort and urgency
  • select one primary workflow
  • use additional workflows only as true dependencies

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

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.