storyline-synthesislisted
Install: claude install-skill sarbak/strategy-skills
# Storyline Synthesis
Write a clean, McKinsey-style synthesis document from analysis work in the current project.
**This process has 10 steps. Complete every step in order. Do not skip steps. When reporting progress, label each step as shown (e.g., "Step 3/10").**
---
## Step 1/10 -- Read all analysis documents
Read every document in the project's strategy/analysis subfolder. Identify:
- All findings with supporting data
- Any contradictions between documents
- Gaps where claims lack supporting evidence
## Step 2/10 -- Identify the governing thought
Write one sentence that captures the core recommendation. This is the single most important sentence in the document. Everything else supports it.
## Step 3/10 -- Plan the storyline structure
Outline BEFORE writing:
- Governing thought (from Step 2/10)
- 3-7 supporting arguments as **action sentences** (not topic labels)
- Verify the logical chain: each finding must lead to the next
**Test**: Read only the supporting argument headers in sequence. Do they tell the story by themselves?
## Step 4/10 -- Check data backing
For every claim in the outline: does it have a number or source? If not, flag it. Do NOT write the synthesis with unsourced claims -- flag them for research first.
## Step 5/10 -- Write the header
- Title
- Version number + date (e.g., "v3.0 -- March 20, 2026")
- Increment version on each meaningful update
## Step 6/10 -- Write the storyline
- **Section headers are action sentences**, not topic labels