strategy-doc

Generate a five-part product strategy document using the Good Strategy Bad Strategy framework.

29|12|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/matteotitta/genesys-skills --skill strategy-doc-matteotitta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategy-doc
Source: https://github.com/matteotitta/genesys-skills/tree/main/skills/primitives/product-management/strategy/strategy-doc
Command: npx skills add https://github.com/matteotitta/genesys-skills --skill strategy-doc-matteotitta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of unfocused product development by forcing a rigorous, evidence-based strategy that prevents feature creep and ensures alignment with business goals.

Core Features & Use Cases

  • GSBS Framework: Structures strategy into the five essential components: target problem, approach, persona, metrics, and tracks.
  • Closed-Loop Integration: Anchors the product-pulse and ship-learnings feedback loops to ensure strategy remains actionable and iterative.
  • Use Case: Use this during a quarterly planning session to transform vague product goals into a locked, measurable strategy document that guides the entire engineering and design team.

Quick Start

Run the strategy-doc skill to initiate a guided interview for your new product strategy.

Frequently Asked Questions about strategy-doc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the Good Strategy Bad Strategy framework for product management?

The Good Strategy Bad Strategy (GSBS) framework structures product strategy into five components: target problem, approach, personas, SMART metrics, and capability tracks to prevent unfocused development and feature creep.

How do I create a measurable product strategy document for quarterly planning?

You can create a measurable product strategy document by running a guided interview that defines target problems, guiding policies, personas, metrics, and capability tracks to align engineering and design teams.

Can I use this approach to prevent feature creep and align product goals?

Yes, this approach prevents feature creep by forcing a rigorous, evidence-based strategy that ensures all product development remains strictly aligned with defined business goals.

How does the strategy document integrate with product-pulse and ship-learnings?

The strategy document anchors product-pulse and ship-learnings feedback loops to maintain a continuous product management cycle, ensuring your strategy remains actionable and iterative.

What are the limitations of using a locked product strategy document?

A locked product strategy document requires integration with continuous feedback loops like product-pulse and ship-learnings to remain actionable; without these, it may fail to adapt to iterative product management needs.