agentleFS
kinhluankinhluan/skills/skills/business-product-leadership/SKILL.md

business-product-leadership

Skill6 starsChanged 6 months agoMITView on GitHub

Frame product strategy and decisions across customer problems, Jobs-to-Be-Done, value propositions, MVP scope, product economics, experiments, pricing, go-to-market, and adoption. Use when a product owner or founder needs an evidence-based decision and accountable next step.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Use multiple evidence types:

    line 33
  2. Very specific:

    Use dora-core for current service-level delivery metrics and diffusion-release-tracking for calibrated adoption/rollout decisions.

    line 68
  3. Distinctive:

    Read references/detailed-guide.md only for a relevant framework or template.

    line 87

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Business and Product Leadership

Turn strategy into falsifiable choices. Frameworks organize evidence; they do not create universal thresholds or replace customer, financial, legal, and operational context.

Decision Workflow

  1. Define the decision, owner, deadline, target segment, and constraints.
  2. State the problem evidence and current alternatives.
  3. Frame the job:
When [situation], [actor] wants to [progress],
so they can [outcome], despite [constraint].
  1. Express a value proposition and the assumption most likely to invalidate it.
  2. Select the smallest solution/prototype that can test the assumption.
  3. Define success, guardrail, stop, and follow-up criteria from baseline data and risk.
  4. Evaluate delivery capability, economics, adoption, and organizational ownership.
  5. Decide build, buy, partner, adapt, defer, or stop.

Discovery and JTBD can iterate in either direction. Do not insist on a universal sequence when evidence already exists; maintain traceability from claims to observations.

Product Evidence

Use multiple evidence types:

  • observed customer behavior and qualitative research;
  • product/support/search data;
  • willingness and authority to switch or pay;
  • competitive alternatives and switching cost;
  • technical/operational feasibility;
  • unit economics and cash constraints;
  • legal, accessibility, privacy, and trust requirements.

Conversion, retention, CAC:LTV, NPS, sample sizes, or price points must be calibrated to the product, channel, usage cadence, margin, and uncertainty. Label illustrative numbers as examples.

MVP

An MVP is the smallest coherent way to test a value/risk hypothesis, not a low-quality version of every planned feature. Specify:

  • target segment and job;
  • hypothesis and evidence needed;
  • included/excluded scope;
  • manual/automated boundaries;
  • quality, safety, and support floor;
  • measurement and observation window;
  • kill/pivot criteria;
  • migration path if the test succeeds.

Build/Buy/Partner

Assess strategic differentiation, regulatory control, data locality, reliability, integration, customization, vendor health, switching/exit cost, and total lifecycle cost. Generic capability is not automatically “buy”; core capability is not automatically “build.”

Ship and Release

  • ship: deploy safely and reversibly.
  • release: expose a value proposition to a defined cohort.
  • adopt: users achieve and repeat the intended outcome.

Use dora-core for current service-level delivery metrics and diffusion-release-tracking for calibrated adoption/rollout decisions. Do not map historical DORA tiers or Rogers percentages directly to product gates.

Output

## Product Decision — [initiative]

**Decision:** [...]
**Owner/date:** [...]
**Segment and JTBD:** [...]
**Problem/value evidence:** [...]
**Riskiest assumption:** [...]
**Options considered:** [build/buy/partner/adapt/defer/stop]
**Experiment/MVP:** [...]
**Success, guardrail, stop criteria:** [...]
**Economics and constraints:** [...]
**Next action:** [owner, date, evidence]

Read references/detailed-guide.md only for a relevant framework or template. Recalibrate every numerical example and verify time-sensitive market/tool claims before use.

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.