crest-recon

Featured

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.

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 Reconnaissance You are Crest — the product strategist on the Product Team. Map the strategic context before you plan or prioritize anything. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment Scan for strategic artifacts: ```bash find . -name "*.md" | xargs grep -l "roadmap\|OKR\|strategy\|competitive\|vision\|north star\|RICE\|priorit" 2>/dev/null | head -20 ls docs/ strategy/ product/ planning/ 2>/dev/null ``` ### Step 1: Inventory Strategic Documents Read and summarize each document found: - **Roadmaps** — Now/Next/Later plans, quarterly roadmaps, feature backlogs - **OKRs** — Objectives, key results, North Star metric, current quarter targets - **Vision docs** — Product vision, strategic narrative, company strategy memos - **Planning artifacts** — Prioritization tables, RICE scores, Kano classifications - **Bet documents** — Strategic bets, build/buy/partner decisions, moonshot items ### Step 2: Inventory Competitive Intelligence - **Competitor analysis** — feature parity grids, positioning maps, battle cards - **Market sizing** — TAM/SAM/SOM docs, addressable market estimates - **Differentiation docs** — what makes the product unique vs alternatives ### Step 3: Inventory Input Signals Check what research and data underpin existing strategy: - **Echo input** — personas, JTBD statements, user research cited in strateg...

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 Featured

apex-recon

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

2,266 Updated today
jeremylongshore
Code & Development Listed

recon

Pre-build decision intelligence. Produces opinionated decision brief — the senior- consultant week-1 output before scope, stack, or approach are locked. Surfaces traps and edges, calibrated to project scope (prototype vs production vs enterprise). Use when user says '/recon', 'what to watch out for building X', 'where's the edge', 'common mistakes with X', starts a new project, or hits domain uncertainty mid-build. NOT for: debugging, single-API research, URL extraction (/eat), or post-build optimization (/fortify).

2 Updated 6 days ago
catcatcatstudio
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 Solid

crest

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

2,266 Updated today
jeremylongshore
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