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.
What this skill does
# 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 strategy - **Lumen input** — metrics, funnel data, retention curves cited in strategy - **Helm briefs** — which initiatives have formal briefs driving the roadmap ### Step 4: Identify Consistency Issues Flag where strategy is internally inconsistent: - OKRs that don't map to roadmap items - Roadmap items with no brief or user research backing - Competitive gaps not addressed in the roadmap - North Star metric undefined or unmeasured ### Step 5: Present Assessment ``` ## Strategic Reconnaissance **Planning horizon:** [current quarter/half/year] **North Star:** [metric or UNDEFINED] **Top OKR this period:** [objective or NONE SET] ### Strategic Artifacts | Artifact | Found | Age | Quality | |----------------|-------|--------|---------| | Roadmap | [✓/✗] | [date] | [solid/stale/absent] | | OKRs | [✓/✗] | [date] | [solid/stale/absent] | | Competitive | [✓/✗] | [date] | [solid/stale/absent] | | Vision doc | [✓/✗] | [date] | [solid/stale/absent] | | Bets | [✓/✗] | [date] | [solid/stale/absent] | ### Key Strategic Bets Currently Active [List top 2-3 bets from existing docs, or NONE DOCUMENTED] ### Consistency Issues - [RED] [critical gap or contradiction] - [YELLOW] [minor inconsistency] ### Recommended Focus [What to work on first given the strategic gaps] ``` ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.