Shokunin strategy
Skill vstakhovsky/shokunin-review/.claude/skills/shokunin-strategy
Terminal-first validation harness for reviewing PRDs, RFCs, strategy docs, and experiment plans.
npx -y skills add vstakhovsky/shokunin-review --skill shokunin-strategyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 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.
SKILL.md
1.6 KB, 378 tokens by cl100k_base, as published. Nobody here has run it
Shokunin Strategy Skill
Reviews and improves product strategy documents.
Purpose
Ensures strategy documents have clear thesis, evidence, and trade-offs.
When to Use
Use this skill when reviewing:
- Product Strategy documents
- Strategic memos
- Strategic bets
- Go-to-market strategies
Workflow
- Analyze thesis — Is strategic choice clear?
- Check segment — Is target customer defined?
- Verify evidence — Is opportunity sized?
- Review trade-offs — Are trade-offs acknowledged?
- Assess sequencing — Is phasing logical?
- Validate metrics — Are success metrics defined?
Inputs
- Strategy document
- Market context (optional)
Output Contract
Returns strategy-specific findings:
- Strategic thesis clarity
- Target segment definition
- Opportunity sizing (TAM, SAM, SOM)
- Trade-offs acknowledgment
- Sequencing logic
- Success metrics
Strategy-Specific Checks
Strategic Thesis
- Is choice explicit?
- Is it actionable?
- Is it differentiated?
Target Segment
- Is ICP defined?
- Is segment size estimated?
- Are characteristics clear?
Opportunity Sizing
- Is TAM quantified?
- Is SAM defined?
- Is SOM calculated?
- Is revenue potential estimated?
Trade-offs
- Are trade-offs explicit?
- Is rationale provided?
- Are mitigation strategies included?
Example
# Input: docs/strategy.md
# Output:
🟠 Needs major fixes — 64/100
Blockers:
1. [opportunity-fog] Market opportunity not quantified
2. [tradeoff-gap] No trade-offs acknowledged
3. [segment-fog] Target segment not clearly defined
Recommend: Add TAM/SAM/SOM sizing, acknowledge trade-offs
Gives 0 of the 12 instructions most roadmap strategy skills give in 378 tokens
Counted across 591 of the 672 authors here whose files we hold, read 2026-08-06
- read product marketing context before asking questionsin 21 of 591, across 10 files
- base price on perceived value, not costin 15 of 591, across 4 files
- compact after finalizing a planin 14 of 591, across 9 files
- differentiate tiers using features, limits, or supportin 14 of 591, across 3 files
- use Van Westendorp to find acceptable price rangein 13 of 591, across 2 files
- use MaxDiff to identify highly valued featuresin 13 of 591, across 2 files
- map topics to buyer journey stagesin 12 of 591, across 6 files
- Extract domain capabilities and classify subdomainsin 11 of 591, across 1 file
- Define bounded contexts around consistency and ownershipin 11 of 591, across 1 file
- Establish a ubiquitous language glossary and anti-termsin 11 of 591, across 1 file
- Capture context boundaries in ADRs before implementationin 11 of 591, across 1 file
- Open the strategic design template if neededin 11 of 591, across 1 file
Said here and by no other author read
- analyze thesis clarity
- check target segment definition
- verify opportunity sizing evidence
- review acknowledged trade-offs
- assess sequencing logic
- validate success metrics
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.