メニュー
This skill should be used when the user asks to "select measures for these objectives," "what should we measure for this," or needs each strategy-map objective assigned 1-3 measures with an explicit lead/lag classification and a check on the overall measure portfolio.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Check installed community skills for updates. Shows a diff and requires explicit approval before applying. Use when the user says "check for updates", "update my skills", "anything new for my installed skills", or when invoked from the registry-sync agent.
Engagement-profile interview that recommends and installs a starter pack of community strategy skills. This IS the practice setup for the whole ecosystem — it asks what kind of strategist you are and recommends what to install first. Use on fresh install, when the user says "get me started" or "what should I install", or to re-run the integration-availability check after adding or removing an MCP connector.
Install a community skill from a watched registry. Reads the allowlist first, fetches, shows the RAW SKILL.md (not just a summary), runs structural trust checks, runs skills-qa, and only writes files after explicit user approval. Use when the user says "install [skill]", picks install from browse, or provides a direct skill URL.
Evaluate a skill against the Strategy Skill Design Framework — thirteen design parameters (including trust-surface, freshness, schema validation, and conflict detection), three strategy-specific failure modes, and a three-band verdict (Ready / Some Concern / Material Concerns). Use when deciding whether to trust a community skill before installing it, before deploying a first-party skill to your team, or whenever the user asks "should I trust this?" or "is this skill well-designed?". Runs automatically as part of /strategy-builder-hub:skill-installer.
This skill should be used when the user asks to "review our resource allocation," "are we funding the right things," "build a portfolio allocation view," or needs current spend, headcount, or management attention checked against strategic priority for misallocation.
This skill should be used when the user asks to "stress-test these synergies," "is this deal's synergy case realistic," or has a deal or partnership's projected synergies that need cost/revenue separation, evidence checks, and a base-rate haircut.
| name | select-measures |
| description | This skill should be used when the user asks to "select measures for these objectives," "what should we measure for this," or needs each strategy-map objective assigned 1-3 measures with an explicit lead/lag classification and a check on the overall measure portfolio. |
| allowed-tools | Read, Grep, Glob |
| metadata | {"version":"0.3.0","owner":"balanced-scorecard practice","review_cadence":"quarterly","work_shape":"structured-aggregation","permission_tier":"advisory","output_class":"draft-for-review","sourcing_policy":"volatile-facts-must-be-sourced"} |
For strategy office or FP&A practitioners assigning measures to strategy-map objectives. The discipline most scorecards skip: explicit lead/lag classification per measure and a portfolio mix check per perspective — not just attaching a number to each objective.
build-strategy-map objectives as input./balanced-scorecard:set-targets-and-initiatives.performance is installed — hands off to /performance:metrics-glossary (same seam as okr:instrument-metrics)./balanced-scorecard:review-and-validate.| Input | If missing |
|---|---|
| Strategy map with objectives per perspective | Halt — route to build-strategy-map |
| Practice profile measure-count ceiling | Use default ~20–25; tag [PROVISIONAL] |
| Perspective causal roles (from map / define-perspectives) | Read profile; flag [review] if top perspective unclear |
When objectives exist but measure data sources are unknown:
TBD — [verify] inline (when performance not installed).structured-aggregation):
[verify], [review], [PROVISIONAL] on defaults.build-strategy-map.Read the practice profile for target total measure count (default ~20–25) and whether performance is installed.
For each strategy-map objective, propose 1–3 measures. More than 3 → flag objective too broad.
Classify every measure as leading or lagging. Be honest about borderline cases.
Check lead/lag mix per perspective against causal role: top perspective mostly lagging; L&G and Internal Process majority leading. Flag misfits.
Check total measure count against ceiling. If over, identify weakest removal candidates (no clear decision attached, duplicate signal).
If performance is installed, hand off formal metric definition to performance:metrics-glossary — this skill owns objective-to-measure mapping and lead/lag only.
Completeness check: every proposed measure has classification and source/formula path before output.
OBJECTIVE: [text] — Perspective: [name]
Measure: [name] — [Leading | Lagging] — [if performance installed: "defined in
performance:metrics-glossary"; else: formula/source/owner/cadence inline]
Measure: ... (max 3)
[repeat per objective]
LEAD/LAG MIX CHECK:
[Perspective]: [N leading, N lagging] — [fits causal role / flag: needs more leading
indicators, this perspective has no early warning]
TOTAL MEASURE COUNT: [N] vs. ceiling [N] — [within / over; if over, removal candidates: ...]
Input: Customer perspective objective "Improve onboarding NPS." Ceiling 22 measures; 18 already assigned elsewhere.
Expected output (excerpt):
OBJECTIVE: Improve onboarding NPS — Perspective: Customer
Measure: Onboarding NPS (post-day-14 survey) — Leading — formula: avg score 0–100, source: Qualtrics, weekly
Measure: 90-day logo churn rate — Lagging — defined in performance:metrics-glossary
LEAD/LAG MIX CHECK:
Customer: 2 leading, 3 lagging — fits causal role
TOTAL MEASURE COUNT: 20 vs. ceiling 22 — within
When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/balanced-scorecard/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /balanced-scorecard:practice-setup auto-applies a full profile write.
Follows plugin CLAUDE.md § Outputs. Natural next branches: /balanced-scorecard:set-targets-and-initiatives, /performance:metrics-glossary for formal definitions, or /balanced-scorecard:review-and-validate once actuals exist.