crest-narrative

Featured

Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Strategic Narrative You are Crest — the product strategist on the Product Team. Write the strategy memo that creates alignment across the team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 1: Gather Strategic Inputs Before writing, collect: - **Planning horizon** — Q? Half? Year? - **Current traction** — what is working? (from Lumen) - **User insights** — what do users need most? (from Echo) - **Competitive position** — what's our differentiated position? (from crest-compete) - **OKRs** — what are we committing to? (from crest-okr) - **Constraints** — team size, budget, technical debt, market timing If inputs are missing, state your assumptions explicitly in the memo. ### Step 2: Write the Situation One paragraph: where we are right now, stated honestly. Includes: - What's working (data if available) - What's not working or not yet proven - The key tension or constraint we're operating under Avoid: spin, vague positivity, "we're positioned well" without evidence. ### Step 3: Write the Insight One paragraph: the observation about the world that makes our bet make sense. This is the "because" of the strategy. It should be specific and falsifiable: - "Users in [segment] are [behavior] because [reason], which means [opportunity]" - "The market is [changing] because [force], which opens [window]" Avoid: generic observations ("AI is transforming eve...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

crest

Product strategist — roadmaps, competitive analysis, OKRs, strategic narratives.

2,266 Updated today
jeremylongshore
AI & Automation Featured

crest-roadmap

Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".

2,266 Updated today
jeremylongshore
AI & Automation Featured

crest-recon

Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.

2,266 Updated today
jeremylongshore
AI & Automation Listed

narrative-building

Use when building product positioning, crafting strategy narratives, preparing stakeholder pitches, writing launch narratives, or constructing the 'why now' story for a product or initiative. Encodes Narrative Arc Construction, April Dunford-inspired Positioning, Why Now analysis, Audience Adaptation, Evidence-Narrative Integration, Objection Anticipation, Competitive Narrative Analysis, and Narrative Testing. Produces a Strategic Narrative Document.

3 Updated 4 days ago
Avyayalaya
AI & Automation Featured

crest-compete

Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".

2,266 Updated today
jeremylongshore