agentleFS
Sign inStart free
AymanShamsAymanShams/codex-coding-os/.agents/skills/product-strategy/SKILL.md

product-strategy

Skill1 starsChanged 2 months agoMPL-2.0View on GitHub

Use when the user asks to create, define, update, sharpen, compare, or review product strategy, product direction, product positioning, product vision, strategic choices, product focus, product bets, target segments, value propositions, trade-offs, north-star metrics, growth logic, required capabilities, defensibility, or what the product should become. Use for prompts like build a product strategy, define product direction, create a strategy canvas, clarify who we serve first, choose what not to build, align features to strategy, evaluate product bets, define the product moat, or decide where the product should compete. Use when the output needs the 9-section Product Strategy Canvas covering vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Do not use for detailed product requirements, feature specs, PRDs, serious written approval memos, PR/FAQ artifacts, go-to-market launch planning, pricing model design, market sizing, delivery sequencing, issue trees, or customer support documentation. If the primary task is requirements or feature scope, use create-prd. If the primary task is a serious decision memo or PR/FAQ, use working-backwards. If the primary task is launch channels, messaging, timeline, or GTM plan, use gtm-strategy. If the primary task is pricing, packaging, willingness to pay, or monetization mechanics, use pricing-strategy. If the primary task is TAM, SAM, SOM, addressable market, or market-entry sizing, use market-sizing. If the primary task is roadmap, dependency tree, work packages, or execution sequencing, use wbs-artifact-planner.

27 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use competitor-analysis, market-research and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LangChainSkill

    competitor-analysis

    Analyze competitors in a given market segment. Trigger on: competitive landscape, competitor analysis, market comparison, competitive positioning.

    Also in 3 projects that use this

  • birne-skSkill

    market-research

    Professional market research and competitive analysis using McKinsey/BCG/Bain consulting methodologies. Use when analyzing markets, competitive landscapes, customer insights, or strategic positioning. Generates hypothesis-driven research with PPTX presentation deliverables.

    Also in 3 projects that use this

  • SentrySkill

    marketing-psychology

    When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.

    Also in 3 projects that use this

  • SupabaseSkill

    copywriting

    Write or audit UI copy (buttons, labels, empty states, error messages, tooltips, form text) anywhere in the monorepo. Load it before shipping or reviewing any user-facing text — including when copy is incidental to the task, like a new feature that adds buttons, toasts, dialogs, or validation messages.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free