product-strategy-session
by deanpetersproduct-strategy-session guides a structured product strategy session from positioning and discovery to prioritization and roadmap planning. It suits Product Management teams, founders, and cross-functional leads who need validated direction before execution, with a repeatable workflow that reduces guesswork.
This skill scores 83/100, which means it is a solid directory candidate for users who want a reusable product-strategy workflow instead of prompting from scratch. The repository shows enough end-to-end structure to help an agent trigger the skill, follow the process, and produce actionable outputs across positioning, discovery, and roadmap planning.
- Strong triggerability: the frontmatter clearly states when to use it and frames it as an end-to-end workflow for validated product direction.
- Good operational depth: the body is substantial (14k+ chars) with 13 H2s and 23 H3s, plus a template and example that show the intended outputs.
- Material agent leverage: it explicitly orchestrates positioning, problem framing, customer discovery, prioritization, and roadmap planning, reducing guesswork versus a generic prompt.
- No install command or supporting reference files are provided, so users must infer adoption and integration details from SKILL.md alone.
- The repository appears workflow-heavy but not tool-integrated; agents may still need judgment to adapt the process to their specific product context.
Overview of product-strategy-session skill
What product-strategy-session does
product-strategy-session is a workflow skill for running a product strategy session from ambiguity to a decision-ready plan. It helps product managers connect positioning, customer insight, problem framing, solution options, and roadmap sequencing in one structured process. If you need a better answer to “what should we build, for whom, and why now?”, this product-strategy-session skill is built for that job.
Who it fits best
This is strongest for Product Management teams, founders, and cross-functional leads who already have a product direction problem, but not a complete strategy. It is useful when stakeholders disagree, discovery is incomplete, or the roadmap is being forced too early. It is less useful if you only need a quick brainstorming prompt or a one-off PRD.
Why it is different
The main value is orchestration. Instead of asking a model to invent strategy in one pass, product-strategy-session guides a staged process that produces clearer inputs and more defensible outputs. That makes it a better install decision when you care about alignment, not just ideas. The output is also easier to hand off into product planning because the workflow is designed to end in priorities, sequencing, and next steps.
How to Use product-strategy-session skill
Install and locate the workflow
Install with:
npx skills add deanpeters/Product-Manager-Skills --skill product-strategy-session
For product-strategy-session install and setup review, start with skills/product-strategy-session/SKILL.md, then open template.md and examples/sample.md. Those three files show the core workflow, the expected output shape, and a realistic end-to-end example.
What input the skill needs
The skill works best when you give it a real strategy problem, not a blank “help me plan product” request. Strong inputs include company goals, market context, target users, current constraints, known customer evidence, and the decision you need by the end. Weak inputs usually lead to generic strategy talk.
A better prompt might look like:
- “Use
product-strategy-sessionto help us reposition an onboarding product for non-technical SMB owners. We have 60% drop-off in first-time use, a small research set, and need a 90-day roadmap.” - “Run a
product-strategy-session usageworkflow for our B2B analytics tool. We need to decide whether to prioritize reporting, alerts, or workflow automation.”
Suggested reading and working order
Read SKILL.md first to understand the sequence and intent. Then use template.md as the output checklist so you know what the session should produce. Finally, consult examples/sample.md to see how a completed strategy session translates into decisions. If you are adapting this for your own org, keep the workflow steps but replace the assumptions with your own market, customer, and operating constraints.
Practical workflow tips
Treat the session as a multi-step decision process, not a single answer request. Feed the model one phase at a time if your context is messy: positioning first, then problem framing, then opportunities, then prioritization. This usually improves the quality of the final roadmap because each step has better upstream evidence. Use the skill when you need a structured product-strategy-session guide for alignment before execution.
product-strategy-session skill FAQ
Is this only for Product Management?
No. It is explicitly useful for product-strategy-session for Product Management, but founders, design leads, and GTM teams can also use it when they need strategy alignment. The workflow is still product-centric, so it is less appropriate for pure marketing planning or engineering execution planning.
How is it different from a normal prompt?
A normal prompt can produce a strategy-shaped answer, but this skill gives you a repeatable process with intermediate artifacts. That matters when the real problem is not idea generation but decision quality. If you need a cleaner path from discovery to roadmap, the product-strategy-session skill is a better fit than ad hoc prompting.
When should I not use it?
Do not use it when the team already has a validated strategy and only needs implementation tasks. It is also a poor fit for very small, single-decision asks like “pick a tagline” or “rank these three UI ideas.” In those cases, a narrower prompt will be faster.
Is it beginner-friendly?
Yes, if you can provide a basic product context. Beginners often get the best results by starting with the template and filling in what they know, even if some sections are incomplete. The skill is most helpful when it can expose what is missing.
How to Improve product-strategy-session skill
Give the model decision-grade context
The fastest way to improve output is to provide constraints the skill can use: target segment, stage of the business, evidence available, hard deadlines, and what the team cannot do. For example, “We cannot add headcount this quarter” is more useful than “we want a better roadmap.” Better input produces sharper prioritization and fewer generic options.
Avoid vague strategy questions
Common failure mode: asking for “the best strategy” without naming the customer, problem, or objective. Another failure mode is skipping evidence and expecting the model to infer market reality. When using product-strategy-session, ask for one concrete decision at a time and include at least a rough hypothesis, such as a persona, JTBD, or current pain point.
Iterate from outputs, not from scratch
After the first pass, improve the session by challenging the weakest assumption. If positioning is weak, add customer segmentation or competitive context. If roadmap quality is weak, add effort limits, dependency constraints, or success metrics. The best product-strategy-session usage pattern is iterative: refine the target, then rerun the same workflow with better inputs.
Check the example against your own case
Use examples/sample.md as a calibration aid, not a template to copy blindly. Compare its phases to your own situation and ask whether your product needs the same sequence or a tighter version. That is the quickest way to decide whether the skill is solving the right problem and where your product-strategy-session install will pay off.