本文へ移動
cccskills
無料GitHub で公開

crux-diagnosis

Identify the pivotal obstacle between current state and desired future. Use when developing strategy.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.0 KB
  • agents/openai.yaml179 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Strategic Crux Diagnosis

Identify the pivotal obstacle between current state and desired future.

When to Use

When developing strategy or facing complex strategic decisions.

The Concept

Crux: The smallest set of obstacles that, if solved, makes everything else tractable or unnecessary.

Required Inputs

Gather before analysis:

  • Current state (baseline metrics, capabilities)
  • Desired future (time-bound outcome, targets)
  • Constraints (budget, headcount, tech, compliance)
  • Available assets (data, channels, IP, partnerships)
  • Key risks and non-negotiables

The Process

1. Map Current to Future

Create a causal graph:

  • Start: Current state
  • End: Desired future
  • List all blockers in between

2. Score Each Blocker

Evaluate on:

  • Causal centrality: How much else depends on this?
  • Bottleneck severity: How much does it slow everything?
  • Solvability: Can we actually fix it?
  • Leverage potential: If solved, how much unlocks?
  • Time to impact: How fast could we see results?
  • Evidence strength: How sure are we this is the problem?

3. Identify the Crux

Find the blocker(s) where:

  • Solving it unlocks the most downstream progress
  • It's actually solvable given constraints
  • Time to impact is acceptable

4. Generate Strategic Options

Create 4-7 options aimed at the crux:

  • Include at least one non-obvious approach
  • Include at least one constraint-relaxation option
  • Evaluate against decision criteria

Output

  • Executive summary (situation, crux, approach)
  • Evidence pack (facts, assumptions, uncertainties)
  • Crux definition with scoring
  • Options comparison table
  • Chosen strategy with rationale
  • Strategic moves (3-5) with owners and timelines

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Surface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

Turn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

Check Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

itseffi のスキルをすべて見る

このスキルの問題を報告する