product-strategy-session

Stress-test product artifacts through coherence checks, premortems, and a decision log.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill product-strategy-session-brunol28
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-strategy-session
Source: https://github.com/BrunoL28/product-onboarding-skill/tree/main/skills/product-strategy-session
Command: npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill product-strategy-session-brunol28

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product strategies often fail at the seams: positioning, problem statements, PRDs, backlogs, and roadmaps can each look defensible while contradicting one another. This Skill runs a closing strategy session that stress-tests the existing artifact set, surfaces contradictions, runs a premortem, tests the biggest bet, and records every open thread in an owned, dated decision log. ## Core Features & Use Cases - Coherence check across seven seams: Walks joins like positioning vs problem statement and backlog P0s vs PRD scope, recording each seam as holding or contradictory. - Structured premortem and biggest-bet test: Facilitates silent-writing premortems across five cause categories and tests what would have to be true for the biggest bet, labeling conditions as Fact, Inference, or Assumption. - Decision log with owners and dates: Emits a stable-column decision log in STRATEGY_SESSION.md so no open thread leaks without a named owner and a date. - Use Case: After running a product onboarding pipeline that produced a PRD, roadmap, and epic breakdown, use this Skill as Phase 5 to verify the roadmap still serves the problem statement and to log unresolved contradictions before committing to delivery. ## Quick Start Run a closing product strategy session over the positioning, PRD, roadmap, and backlog artifacts in my working folder and produce a decision log of open questions with owners and dates.

Frequently Asked Questions about product-strategy-session

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

FAQPage Schema
How do I run a product strategy session over existing artifacts?▼

Use closing-session mode, the default. The Skill inventories your positioning, problem statement, PRD, breakdown, and roadmap files, walks seven coherence seams, runs a premortem and biggest-bet test, and emits one STRATEGY_SESSION.md file ending in a decision log.

What is a premortem in product strategy?▼

A premortem imagines the product has already failed and asks the room to write causes in silence before discussion. This Skill requires causes in five categories including self-inflicted, ranks the top five by likelihood times damage, and converts each into an owned risk with an early-warning signal.

Can I use this without running the earlier product-onboarding phases?▼

Yes, standalone mode runs six phases from positioning to execution planning by invoking the earlier skills by name, then applies the closing-session steps over what they produced. It never reimplements positioning, discovery, or roadmapping itself.

What artifacts does the strategy session produce?▼

It produces one STRATEGY_SESSION.md file containing the artifact inventory, coherence check report, premortem, biggest-bet test, and decision log, closing with Assumptions to Validate. The decision log column order is a stability contract for diffing across sessions.

When should I not run a product strategy session?▼

Skip it when there is no executive sponsor who can decide scope, budget, or headcount, or when fewer than three roles can attend. Without a sponsor it becomes a preparation session, and below three participants it is a review, not a session.