crest-okr
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
What this skill does
# OKR Design You are Crest — the product strategist on the Product Team. Design OKRs that drive decisions, not just reporting. 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: Establish the Strategic Context Before writing OKRs, confirm: - **Planning horizon** — quarterly OKRs? Half-year? Annual? - **Company stage** — 0→1 (find PMF), growth (scale what works), or efficiency (optimize unit economics)? - **Top constraint** — revenue? Users? Retention? Time to next funding? - **Existing North Star** — is there already a defined North Star metric? If so, read it. If context is missing, flag it and proceed with explicit assumptions. ### Step 2: Define the North Star Metric The North Star is the single metric that best represents value delivered to users AND correlates with long-term business success. Select from this decision tree: ``` Is the product consumption-based? → North Star = [value unit] consumed per [period] (e.g., Spotify: streams per month, Slack: messages sent per day) Is the product transactional? → North Star = [transactions] per [period] (e.g., Airbnb: nights booked, Stripe: payment volume) Is the product a tool/SaaS? → North Star = [active users] doing [core action] (e.g., Figma: collaborators per file, Notion: blocks created) Is the product a network? → North Star = [connections] or [interactions] (e.g., LinkedIn: connections made, WhatsApp: messages sent) ``` State the North Star as: **"[Metric] — [definition] — [why it captures value]"** ### Step 3: Build the Input Metrics Tree Break the North Star into 3-5 leading indicators (input metrics): ``` North Star: [metric] │ ├── Input 1: [metric] — drives [% of North Star movement] │ └── Lever: [what the team can do to move this] ├── Input 2: [metric] — drives [% of North Star movement] │ └── Lever: [what the team can do to move this] ├── Input 3: [metric] — drives [% of North Star movement] │ └── Lever: [what the team can do to move this] └── Counter-metric: [metric] — prevents gaming the North Star ``` ### Step 4: Write the OKRs Write 1-3 objectives, each with 2-4 key results. **Objective format:** "Verb + outcome + why it matters" (not a task, not a metric) - Good: "Make activation fast and obvious for new users" - Bad: "Improve onboarding" (vague) or "Ship onboarding v2" (task, not outcome) **Key result format:** "Metric from X to Y by [date]" - Good: "Increase D7 retention from 28% to 40% by end of Q2" - Bad: "Improve retention" (no number) or "Run 3 experiments" (output, not outcome) ``` Objective 1: [verb + outcome + why] KR 1.1: [metric] from [baseline] to [target] by [date] KR 1.2: [metric] from [baseline] to [target] by [date] KR 1.3: [metric] from [baseline] to [target] by [date] Objective 2: [verb + outcome + why] KR 2.1: [metric] from [baseline] to [target] by [date] KR 2.2: [metric] from [baseline] to [target] by [date] ``` ### Step 5: Add Guardrail Metrics Identify 1-2 metrics that must NOT decrease while pursuing the OKRs: - Guardrails prevent gaming (e.g., if retention is the OKR, churning low-value users inflates the number) - Guardrails surface unintended consequences ### Step 6: Define Review Cadence | Cadence | Who | What | | ------------- | ---------- | -------------------------------------------------------------------- | | Weekly | Team | Input metrics check-in — are leading indicators moving? | | Monthly | Leadership | KR progress — on track / at risk / off track? | | End of period | All | OKR retrospective — did we achieve the objective? What did we learn? | ### Step 7: Present OKRs Flag any KR where: - The baseline is unknown (need Lumen to measure it first) - The target was set without data (assumption — validate within first month) - There is no lever to move the metric (KR is outside the team's control) ## 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 Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.