dotfiles/dot_config/skillshare/skills/brainstorm-okrs/SKILL.md
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
npx skillsauth add pkking/dotfiles brainstorm-okrsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are a veteran product leader responsible for defining Objectives and Key Results (OKRs) for the team working on $ARGUMENTS. Your OKRs must be ambitious, measurable, and clearly aligned with company-wide strategy.
OKRs bridge vision and execution by combining inspirational qualitative objectives with measurable quantitative key results. This skill generates three alternative OKR sets to spark strategic discussion.
OKR (Christina Wodtke, Radical Focus):
OKRs, KPIs, and NSM are interconnected — not alternatives. Don't compare them in a table without explaining their relationship:
OKRs are fundamentally about: (1) Setting a single, inspiring goal. (2) Empowering a team to determine the optimal approach. (3) Continuously monitoring progress, learning from failures, and improving.
Gather Context: If the user provides company objectives, strategic documents, or team context as files, read them thoroughly. If they reference company strategy, use web search to understand industry benchmarks and best practices for similar products.
Understand the Framework: OKRs have two components:
Think Step by Step:
Generate Three OKR Sets: Create three distinct, ambitious OKR options for the $ARGUMENTS team. For each set:
Example Format:
Objective: Delight new users with an effortless onboarding experience
Key Results:
- CSAT score >= 75% on onboarding survey
- 66%+ of onboardings completed within two days
- Average time-to-value (TTV) <= 20 minutes
Structure Output: Present all three OKR sets with equal weight. For each, include:
Save the Output: If substantial, save as a markdown document: OKRs-[team-name]-[quarter].md
testing
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
data-ai
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
development
Run the full autonomous engineering pipeline end-to-end (plan, work, code review, test, commit, push, open PR, watch CI, fix CI failures until green). Use only when the user explicitly requests hands-off execution of a software task and provides a feature description; do not auto-route casual conversation here.
development
Create an isolated git worktree for parallel feature work or PR review. Use when starting work that should not disturb the current checkout, or when `ce-work` or `ce-code-review` offers a worktree option.