agentsclimarketplace

Product growth audit

Skill bglglzd/agent-workflows/plugins/agent-workflows/skills/product-growth-audit

Portable Markdown workflows for AI coding agents — session handoffs, project audits, and product discovery.

Install
npx -y skills add bglglzd/agent-workflows --skill product-growth-audit

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

  • 24 days oldThe repository was created 24 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.
  • 1 stars1 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

Audit an existing application to discover and prioritize its best product, UI/UX, business, growth, reliability, and technical improvements. Use when Codex must turn an unclear improvement backlog into an evidence-based opportunity map and 30/60/90-day plan without assuming a mass-market strategy or inventing metrics.

SKILL.md

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

Product Growth Audit

Find the strongest next improvements for an existing product. Produce a roadmap based on evidence, not a generic feature list.

Workflow

  1. Inspect the repository, docs, current UI, tests, issues, release notes, feedback, and data that are actually available. Record verified facts, assumptions, and unknowns.
  2. Map users, jobs to be done, product promise, key workflows, platform, maturity, constraints, and the journey from first touch through repeat use and support.
  3. Evaluate the relevant lenses: positioning; UX/UI; core value and features; activation, retention, distribution, and business model; trust and reliability; technical leverage; and AI quality when AI is part of the product.
  4. Evaluate niche, internal, B2B, open-source, and mass-market paths from the available evidence. Do not assume broad distribution is the goal.
  5. Create a non-duplicative opportunity map. For every item, provide evidence, user problem, improvement hypothesis, expected outcome, success signal, impact/confidence/effort rationale, dependencies, risks, and a smallest safe validation step.
  6. Separate quick quality wins, strategic bets, growth or business options, and technical enablers.
  7. Write or update product documentation. When no convention exists, use docs/product/PRODUCT_GROWTH_AUDIT.md.
  8. Deliver a 30/60/90-day roadmap split into Now, Next, and Later. Include scope, acceptance criteria, measurement plan, dependencies, and an owner type for every recommended item.

Guardrails

  • Do not invent metrics, users, competitor claims, market demand, revenue, or evidence. Mark missing data clearly.
  • Do not recommend trendy features, AI, gamification, paywalls, or growth hacks without a product-specific rationale.
  • Use external research only with authorization and cite it.
  • Do not implement, redesign, alter production, publish marketing, or contact users before approval.
  • Preserve real differentiators and prioritize feasible work for the actual team, codebase, budget, and privacy posture.

What ships with it: 1 file

210 B alongside SKILL.md

agents/

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.