agentsclimarketplace

Write product strategy doc

Skill alexe-ev/product-plugins/leadership-communication/skills/write-product-strategy-doc

Skill library for AI agents — 15 product domains, 121 skills. Tells the agent what to ask, how to reason, and what to output.

Install
npx -y skills add alexe-ev/product-plugins --skill write-product-strategy-doc

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 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

Write a clear, concise product strategy document that aligns teams on direction, priorities, and trade-offs. Use this skill when a team needs a written strategy artifact that can serve as a decision-making anchor.

SKILL.md

2.6 KB, 505 tokens by cl100k_base, as published. Nobody here has run it

Write Product Strategy Doc

Purpose

Help teams produce a written product strategy document that articulates direction clearly enough to align teams, guide prioritization, and reduce repeated strategic debates.

Skill type

Conceptual skill

Use this skill when

  • A team lacks a written product strategy and relies on oral tradition
  • Strategic debates keep recurring because direction isn't documented
  • A new leader or team member needs to understand product direction quickly
  • A planning cycle requires a strategy anchor document

Do not use this skill when

  • The goal is executive presentation (use build-executive-narrative)
  • The goal is roadmap creation (use build-roadmap-prioritization)

Required inputs

  • Product area or scope
  • Strategic direction, goals, and key decisions to document

Optional inputs

  • Existing strategy artifacts
  • OKRs or portfolio decisions
  • Competitive context
  • Product-market fit assessment

Upstream context

Works best when:

  • Vision and positioning are defined
  • Strategic bets are prioritized
  • Goals are set

Downstream handoff

Output can feed:

  • build-executive-narrative (strategy doc → executive narrative)
  • communicate-decisions-tradeoffs (strategy doc surfaces decisions to communicate)
  • build-roadmap-prioritization (strategy doc anchors roadmap)

Instructions

  1. Define the scope: what product area or initiative is this strategy for?
  2. Write a problem and opportunity statement.
  3. Define the strategic approach: what choices are being made and why?
  4. Articulate what's in scope vs. out of scope (explicit trade-offs).
  5. Define success: what does winning look like in 12 months?
  6. Anticipate objections and address them.
  7. Keep it to 2–4 pages — strategy docs that aren't read aren't strategies.

Output

Provide:

  • Context: product area, current state, opportunity
  • Strategic approach and key choices
  • Explicit trade-offs and what's out of scope
  • Success definition (12-month horizon)
  • Key risks and mitigations
  • Open decisions requiring alignment
  • Document length: 2–4 pages max

Risks / caveats

  • Strategy docs that describe everything are strategy docs about nothing — be specific about trade-offs
  • "We will do X and Y and Z" is not strategy — strategy requires saying no to things
  • A strategy doc with no clear author has no owner — assign responsibility

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.