agentleFS
LOSTTEMPERLOSTTEMPER/agent-skill/shape-product-strategy/SKILL.md

shape-product-strategy

Skill0 starsChanged 3 months agoMITView on GitHub

Develop evidence-backed product strategy across industry structure, market selection, positioning, competition, differentiation, business models, strategic moats, and staged investment. Use for product strategy, market or industry analysis, competitor analysis, positioning, blue-ocean questions, business-model design, monetization, platform strategy, strategic roadmaps, or deciding where a product should compete and why.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat industry frameworks as lenses, not conclusions.

    line 33
  2. Distinctive:

    Read references/strategy-toolkit.md for the comparison matrix, industry lenses, and business-model tests.

    line 60
  3. Distinctive:

    Do not assume free, platform, long-tail, subscription, advertising, or cross-subsidy models are superior.

    line 77
  4. Very specific:

    Use elimination-reduction-increase-creation or cost/differentiation/focus only as prompts for option generation.

    line 92
  5. Distinctive:

    Use lawful public information, authorized product access, disclosed interviews, and legitimate expert engagement.

    line 111
  6. Distinctive:

    Keep examples and market analogies subordinate to the actual decision.

    line 128

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Shape Product Strategy

Turn market material into a bounded strategic choice. Do not produce a broad catalogue when the decision requires a focused recommendation.

Frame the strategic decision

State:

  • the decision owner and deadline;
  • the product, geography, customer, and time horizon;
  • the company objective and non-goals;
  • the current product and market stage;
  • hard constraints, distinctive assets, and missing capabilities;
  • what choosing one direction prevents or delays.

Separate user-confirmed facts from external market material. Verify current product, price, policy, and market claims using primary sources when possible.

Model the system from first principles

Describe the market as a value system:

  1. Actors: users, buyers, payers, operators, suppliers, regulators, partners, and substitutes.
  2. Value carrier: product, service, capability, data, access, risk transfer, or outcome.
  3. Context: trigger, workflow, channel, frequency, urgency, and switching environment.
  4. Enablers: technology, infrastructure, distribution, standards, policy, and capital.
  5. Exchange: who gives what, who receives value, who bears cost and risk.

Treat industry frameworks as lenses, not conclusions. Rebuild the logic when the category boundary or market structure does not fit the framework.

Choose a market and customer

Segment using variables tied to the strategic objective, such as:

  • problem intensity and frequency;
  • willingness and ability to pay;
  • acquisition and service cost;
  • workflow or scenario;
  • risk and compliance requirements;
  • switching cost and incumbent alternative;
  • strategic fit and reachable distribution.

Require a segment to be meaningful, measurable enough, reachable, actionable, and large or valuable enough for the intended model. For concentrated B2B markets, map decision makers, users, payers, evaluators, implementers, veto holders, and affected parties.

Analyze competition by purpose

Define why competition is being studied before selecting competitors:

  • industry entry and market selection;
  • positioning and long-term direction;
  • feature, experience, or technical decisions;
  • pricing, distribution, growth, or go-to-market.

Include direct competitors, different solutions to the same need, alternatives competing for the same budget or behavior, and useful reference products. Compare the mechanism behind results, not only visible features.

Read references/strategy-toolkit.md for the comparison matrix, industry lenses, and business-model tests.

Design the business model

Make the model explicit:

  • target customer and underserved condition;
  • value proposition and proof;
  • product or service offered;
  • key capabilities, resources, data, and partners;
  • acquisition, delivery, support, and retention;
  • payer, price metric, revenue timing, and incentives;
  • fixed, variable, operational, risk, and exit costs;
  • unit economics and cash-flow timing;
  • stakeholder benefit and harm;
  • conditions required for the model to become self-sustaining.

Do not assume free, platform, long-tail, subscription, advertising, or cross-subsidy models are superior. Test whether each side receives enough value, whether the subsidy is fundable, and whether the model survives without misleading users or trapping them.

Build strategic options

Develop a small set of materially different options, including “do nothing” or “delay” when relevant. For each option, show:

  • target segment and problem;
  • unique value mechanism;
  • required capabilities and missing resources;
  • revenue, cost, and operational model;
  • differentiation and likely response from competitors;
  • major assumptions and failure modes;
  • time to learn, time to value, and reversibility;
  • minimum credible proof.

Use elimination-reduction-increase-creation or cost/differentiation/focus only as prompts for option generation. Do not label an option a blue ocean without evidence of new demand and a credible value-cost change.

Select and stage the strategy

Recommend an option only after comparing:

  • customer value;
  • business value and economics;
  • strategic fit;
  • feasibility and operating burden;
  • risk, regulation, and ecosystem dependence;
  • defensibility;
  • speed and cost of validation;
  • opportunity cost.

Define the first liquidity unit, wedge, or minimum strategic loop. Name the phase-one proof, expansion trigger, stop condition, and capabilities that must be built before scaling.

Apply research and ethics boundaries

Use lawful public information, authorized product access, disclosed interviews, and legitimate expert engagement. Never use fake recruitment, sham procurement, impersonation, unauthorized system access, confidential-information solicitation, product backdoors, or deceptive pretexts to obtain competitor information.

Reject business models that depend on hidden fees, false scarcity, fabricated authority or social proof, involuntary continuity, unauthorized data use, artificial lock-in, or harm shifted to a less visible stakeholder.

Deliver the decision

Provide:

  1. strategic decision and scope;
  2. current facts, market material, and unresolved conflicts;
  3. system and competition model;
  4. options and explicit assumptions;
  5. selected position and business model;
  6. capabilities, costs, and high-cost compromises;
  7. staged validation and decision gates;
  8. invalidation conditions and monitoring signals.

Keep examples and market analogies subordinate to the actual decision.

Download now (ZIP)

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.