jpskill.com
💬 コミュニケーション コミュニティ

goal-setter

目標達成に向けて、ユーザーの意図を具体的なゴール、サブゴール、マイルストーン、成功基準に分解し、計画的な行動へと導く支援をするSkill。

📜 元の英語説明(参考)

Transform objectives into structured goals with plans. Use when user declares intent ("I want to...", "Goal is to...", "Achieve X by Y"). Decomposes into subgoals, milestones, success criteria.

🇯🇵 日本人クリエイター向け解説

一言でいうと

目標達成に向けて、ユーザーの意図を具体的なゴール、サブゴール、マイルストーン、成功基準に分解し、計画的な行動へと導く支援をするSkill。

※ jpskill.com 編集部が日本のビジネス現場向けに補足した解説です。Skill本体の挙動とは独立した参考情報です。

⚡ おすすめ: コマンド1行でインストール(60秒)

下記のコマンドをコピーしてターミナル(Mac/Linux)または PowerShell(Windows)に貼り付けてください。 ダウンロード → 解凍 → 配置まで全自動。

🍎 Mac / 🐧 Linux
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -L -o goal-setter.zip https://jpskill.com/download/17491.zip && unzip -o goal-setter.zip && rm goal-setter.zip
🪟 Windows (PowerShell)
$d = "$env:USERPROFILE\.claude\skills"; ni -Force -ItemType Directory $d | Out-Null; iwr https://jpskill.com/download/17491.zip -OutFile "$d\goal-setter.zip"; Expand-Archive "$d\goal-setter.zip" -DestinationPath $d -Force; ri "$d\goal-setter.zip"

完了後、Claude Code を再起動 → 普通に「動画プロンプト作って」のように話しかけるだけで自動発動します。

💾 手動でダウンロードしたい(コマンドが難しい人向け)
  1. 1. 下の青いボタンを押して goal-setter.zip をダウンロード
  2. 2. ZIPファイルをダブルクリックで解凍 → goal-setter フォルダができる
  3. 3. そのフォルダを C:\Users\あなたの名前\.claude\skills\(Win)または ~/.claude/skills/(Mac)へ移動
  4. 4. Claude Code を再起動

⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。

🎯 このSkillでできること

下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。

📦 インストール方法 (3ステップ)

  1. 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
  2. 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
  3. 3. 展開してできたフォルダを、ホームフォルダの .claude/skills/ に置く
    • · macOS / Linux: ~/.claude/skills/
    • · Windows: %USERPROFILE%\.claude\skills\

Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。

詳しい使い方ガイドを見る →
最終更新
2026-05-18
取得日時
2026-05-18
同梱ファイル
1

📖 Skill本文(日本語訳)

※ 原文(英語/中国語)を Gemini で日本語化したものです。Claude 自身は原文を読みます。誤訳がある場合は原文をご確認ください。

ゴールセッター

曖昧な、または明確な目標を、構造化された、実行可能なゴールに変換します。

運用モデル

ゴールはLeanOSにおける主要な運用モードです。すべての作業はゴール主導であるべきです。

PROACTIVE (primary):  Goal → Plan → Threads → Artifacts → Learning → Canvas
REACTIVE (fallback):  Signal → Thread → Link to Goal (or create new goal)

Goal-setter が読むもの:

  • Canvas (strategy/canvas/*) - 戦略的コンテキスト、前提、制約
  • 既存のゴール (strategy/goals/active/*) - 競合を避け、関連性を見つける

Goal-setter が読まないもの:

  • Threads (実行結果であり、入力ではない)
  • Artifacts (成果物であり、コンテキストではない)

Canvas リファレンス

Goal-setter は、コンテキスト、制約、および成功基準の整合性のために Canvas のセクションを使用します。

Canvas セクション (15 ファイル)

セクション 目的 Goal-setter の使用
00.mode.md VENTURE/BOOTSTRAP モード 必須 - メトリクス、分解を決定
01.context.md 製品、市場のコンテキスト (KBOS) ゴールの整合性チェック
02.constraints.md 予算、時間、リソース ゴールの制約
03.opportunity.md TAM/SAM/SOM、タイミング ビジネスゴールの規模設定
04.segments.md 顧客セグメント ゴールのターゲットオーディエンス
05.problem.md 上位3つの問題 問題に焦点を当てたゴール
06.competitive.md 競合他社、ポジショニング 競争力のあるゴール
07.uvp.md Unique Value Proposition メッセージングの整合性
08.unfair.md 不当な優位性、参入障壁 戦略的なゴール
09.solution.md MVP 機能 プロダクトゴール
10.assumptions.md 仮説、検証ステータス 重要 - ゴールを仮説にリンク
11.channels.md 獲得チャネル チャネル戦略
12.revenue.md 収益モデル、階層 収益ゴールのターゲット
13.metrics.md 主要なメトリクス、ターゲット 成功基準のソース
14.costs.md コスト構造、バーン 収益性の制約
15.gtm.md GTM 戦略 マーケティング/セールスゴール

ゴールタイプ別の Canvas の読み込み

business goals:
  Required: 00-mode, 11-pricing, 12-costs, 13-metrics
  Context:  01-context, 03-opportunity, 04-segments
  Link to:  10-assumptions (revenue/growth hypotheses)

brand goals:
  Required: 01-context, 07-uvp
  Context:  04-segments, 14-growth
  Link to:  10-assumptions (audience/positioning hypotheses)

product goals:
  Required: 09-solution, 05-problem
  Context:  01-context, 02-constraints
  Link to:  10-assumptions (product/market fit hypotheses)

learning goals:
  Context:  01-context (what skills needed)
  Link to:  10-assumptions (capability hypotheses)

ゴールを Canvas の仮説にリンクする

すべてのゴールは Canvas の仮説 (10.assumptions.md) にリンクする必要があります。

## Canvas Links

**Validates assumptions:**
- A3: "Enterprise customers will pay $500/month" (10.assumptions.md)
- A7: "Content marketing drives qualified leads" (10.assumptions.md)

**Informs sections:**
- 13.metrics.md (success updates metrics)
- 12.revenue.md (if revenue assumption validated)

ゴールが完了したら:

  1. 10.assumptions.md でリンクされた仮説のステータスを更新します
  2. 仮説が検証/無効化された場合は、関連する Canvas セクションを更新します
  3. ゴールファイルに学習内容を記録します

型シグネチャ

GoalSetter : Objective × CanvasContext × Mode × ExistingGoals → Goal

Where:
  Objective     : string (ユーザーの表明された意図)
  CanvasContext : strategy/canvas/* (信念、制約、セグメント)
  Mode          : VENTURE | BOOTSTRAP (strategy/canvas/00.mode.md から)
  ExistingGoals : strategy/goals/active/* (競合を避ける)
  Goal          : Objective × SuccessCriteria × Plan × Autonomy × State
  Plan          : [Subgoal] × [Milestone] × [Dependency]
  Subgoal       : Objective × SuccessCriterion × ThreadType

いつ使用するか

  • ユーザーが意図を表明したとき: "I want to...", "Goal is to...", "Need to achieve..."
  • 明確な構造なしに新しいイニシアチブを開始するとき
  • 大きな目標を実行可能な部分に分解するとき
  • 既存のゴールを見直し/改善するとき

プロセス

1. 目標のキャプチャ

ユーザー入力から抽出:

  • What: 望ましい結果
  • Why: 動機/コンテキスト (オプションだが価値がある)
  • When: 締め切りまたはタイムライン (必須)
  • Constraints: 予算、リソース、依存関係

曖昧な場合は、以下を尋ねます:

What does success look like specifically?
By when do you need this achieved?
What resources/constraints should I know about?

2. ゴールタイプの決定

コンテキストから推測するか、尋ねます:

タイプ シグナル
business 収益、顧客、成長、市場 "Reach $50K MRR"
brand フォロワー、リーチ、権威、オーディエンス "Build LinkedIn presence"
product 機能、ローンチ、技術的なマイルストーン "Ship v2.0"
learning スキル、認定、知識 "Learn Rust"
custom その他すべて ユーザー定義

3. モードの適用 (ビジネスゴール)

business タイプのゴールの場合、strategy/canvas/00.mode.md からモードを読み取ります:

側面 VENTURE BOOTSTRAP
主要なメトリクス ARR, MAU, 市場シェア, ランウェイ MRR, 利益, キャッシュフロー, ペイバック
成功の焦点 成長率、スケール 収益性、持続可能性
分解 ユーザー → アクティベーション → マネタイズ 収益 → マージン → 再投資
タイムライン 7-10 年のエグジットホライズン 3ヶ月で収益化
リスク許容度 高い (成長のためのバーン) 低い (現金を維持)

モード固有のデフォルト:

VENTURE mode:
  Success criteria emphasize:
  - ARR growth rate (>100% YoY)
  - User/customer acquisition
  - Market share expansion
  - Acceptable burn for growth

  Subgoal order: Acquire → Activate → Retain → Monetize

  Autonomy default: hybrid (speed matters, but stakes high)

BOOTSTRAP mode:
  Success criteria emphasize:
  - MRR and monthly profit
  - Positive cash flow
  - LTV:CAC > 5:1
  - CAC payback < 6 months

  Subgoal order: First revenue → Unit economics → Scale

  Autonomy default: ask (cash preservation critical)

非ビジネスゴール: Mo

📜 原文 SKILL.md(Claudeが読む英語/中国語)を展開

Goal Setter

Transform vague or precise objectives into structured, actionable goals.

Operating Model

Goals are the primary operating mode for LeanOS. All work should be goal-driven.

PROACTIVE (primary):  Goal → Plan → Threads → Artifacts → Learning → Canvas
REACTIVE (fallback):  Signal → Thread → Link to Goal (or create new goal)

Goal-setter reads:

  • Canvas (strategy/canvas/*) - strategic context, assumptions, constraints
  • Existing goals (strategy/goals/active/*) - avoid conflicts, find linkages

Goal-setter does NOT read:

  • Threads (execution output, not input)
  • Artifacts (deliverables, not context)

Canvas Reference

Goal-setter uses Canvas sections for context, constraints, and success criteria alignment.

Canvas Sections (15 files)

Section Purpose Goal-setter Use
00.mode.md VENTURE/BOOTSTRAP mode Required - determines metrics, decomposition
01.context.md Product, market context (KBOS) Goal alignment check
02.constraints.md Budget, time, resources Goal constraints
03.opportunity.md TAM/SAM/SOM, timing Business goal sizing
04.segments.md Customer segments Target audience for goals
05.problem.md Top 3 problems Problem-focused goals
06.competitive.md Competitors, positioning Competitive goals
07.uvp.md Unique Value Proposition Messaging alignment
08.unfair.md Unfair advantages, moats Strategic goals
09.solution.md MVP features Product goals
10.assumptions.md Hypotheses, validation status Key - link goals to assumptions
11.channels.md Acquisition channels Channel strategy
12.revenue.md Revenue model, tiers Revenue goal targets
13.metrics.md Key metrics, targets Success criteria source
14.costs.md Cost structure, burn Profitability constraints
15.gtm.md GTM strategy Marketing/sales goals

Canvas Reading by Goal Type

business goals:
  Required: 00-mode, 11-pricing, 12-costs, 13-metrics
  Context:  01-context, 03-opportunity, 04-segments
  Link to:  10-assumptions (revenue/growth hypotheses)

brand goals:
  Required: 01-context, 07-uvp
  Context:  04-segments, 14-growth
  Link to:  10-assumptions (audience/positioning hypotheses)

product goals:
  Required: 09-solution, 05-problem
  Context:  01-context, 02-constraints
  Link to:  10-assumptions (product/market fit hypotheses)

learning goals:
  Context:  01-context (what skills needed)
  Link to:  10-assumptions (capability hypotheses)

Linking Goals to Canvas Assumptions

Every goal should link to Canvas assumptions (10.assumptions.md):

## Canvas Links

**Validates assumptions:**
- A3: "Enterprise customers will pay $500/month" (10.assumptions.md)
- A7: "Content marketing drives qualified leads" (10.assumptions.md)

**Informs sections:**
- 13.metrics.md (success updates metrics)
- 12.revenue.md (if revenue assumption validated)

When goal completes:

  1. Update linked assumption status in 10.assumptions.md
  2. Update relevant Canvas section if assumption validated/invalidated
  3. Log learning in goal file

Type Signature

GoalSetter : Objective × CanvasContext × Mode × ExistingGoals → Goal

Where:
  Objective     : string (user's stated intent)
  CanvasContext : strategy/canvas/* (beliefs, constraints, segments)
  Mode          : VENTURE | BOOTSTRAP (from strategy/canvas/00.mode.md)
  ExistingGoals : strategy/goals/active/* (avoid conflicts)
  Goal          : Objective × SuccessCriteria × Plan × Autonomy × State
  Plan          : [Subgoal] × [Milestone] × [Dependency]
  Subgoal       : Objective × SuccessCriterion × ThreadType

When to Use

  • User expresses intent: "I want to...", "Goal is to...", "Need to achieve..."
  • Starting a new initiative without clear structure
  • Breaking down a large objective into actionable pieces
  • Reviewing/refining existing goals

Process

1. Capture Objective

Extract from user input:

  • What: The desired outcome
  • Why: Motivation/context (optional but valuable)
  • When: Deadline or timeline (required)
  • Constraints: Budget, resources, dependencies

If vague, ask:

What does success look like specifically?
By when do you need this achieved?
What resources/constraints should I know about?

2. Determine Goal Type

Infer from context or ask:

Type Signals Example
business Revenue, customers, growth, market "Reach $50K MRR"
brand Followers, reach, authority, audience "Build LinkedIn presence"
product Features, launches, technical milestones "Ship v2.0"
learning Skills, certifications, knowledge "Learn Rust"
custom Anything else User-defined

3. Apply Mode (Business Goals)

For business type goals, read mode from strategy/canvas/00.mode.md:

Aspect VENTURE BOOTSTRAP
Primary metrics ARR, MAU, market share, runway MRR, profit, cash flow, payback
Success focus Growth rate, scale Profitability, sustainability
Decomposition Users → Activation → Monetization Revenue → Margin → Reinvest
Timeline 7-10 year exit horizon Profitable in 3 months
Risk tolerance Higher (burn for growth) Lower (preserve cash)

Mode-specific defaults:

VENTURE mode:
  Success criteria emphasize:
  - ARR growth rate (>100% YoY)
  - User/customer acquisition
  - Market share expansion
  - Acceptable burn for growth

  Subgoal order: Acquire → Activate → Retain → Monetize

  Autonomy default: hybrid (speed matters, but stakes high)

BOOTSTRAP mode:
  Success criteria emphasize:
  - MRR and monthly profit
  - Positive cash flow
  - LTV:CAC > 5:1
  - CAC payback < 6 months

  Subgoal order: First revenue → Unit economics → Scale

  Autonomy default: ask (cash preservation critical)

Non-business goals: Mode has minimal impact on brand, product, learning goals.

4. Define Success Criteria

Transform objective into measurable criteria:

Good criteria:

  • Specific number or state
  • Independently verifiable
  • Time-bound (inherits from goal deadline)

Examples:

Objective: "Grow revenue"
Criteria:
- [ ] MRR >= $50,000
- [ ] Customer count >= 10
- [ ] Net revenue retention >= 100%

Objective: "Build LinkedIn presence"
Criteria:
- [ ] Followers >= 10,000
- [ ] Average post impressions >= 5,000
- [ ] 2+ inbound leads/month from content

5. Decompose into Plan

Subgoals - intermediate objectives that lead to main goal:

  • Each subgoal has its own success criterion
  • Identify dependencies between subgoals
  • Link to thread types (business, sales, marketing, engineering)

Milestones - checkpoints with dates:

  • Evenly distributed toward deadline
  • Each milestone = measurable progress marker

Decomposition reasoning:

Goal: Achieve X by deadline D
  ↓
Ask: What must be true for X to happen?
  ↓
Identify 3-5 necessary conditions (subgoals)
  ↓
For each subgoal: What threads/actions achieve this?
  ↓
Order by dependencies
  ↓
Set milestones at 25%, 50%, 75%, 100% progress points

6. Set Autonomy Level

Mode When to Use Behavior
auto Low-risk, well-understood domain AI creates threads and executes without asking
ask High-risk, novel, or user preference AI recommends, waits for approval
hybrid Default Auto for impact <0.5, ask for impact ≥0.5

Default: hybrid unless user specifies otherwise.

7. Initialize State

Create initial state section:

  • All metrics start at current values (0 or baseline)
  • Gap = target - current
  • Trend = "→" (neutral, no data yet)
  • Trajectory = "Unknown" (insufficient data)

Output

Create file: strategy/goals/active/{goal-id}.md

Goal File Schema

---
id: g-{kebab-case-short-name}
type: business | brand | product | learning | custom
mode: VENTURE | BOOTSTRAP  # For business goals only
status: active
autonomy: auto | ask | hybrid
created: {YYYY-MM-DD}
deadline: {YYYY-MM-DD}
canvas_refs: ["{section}.md", ...]  # Optional Canvas links
---

# {Goal Title}

## Objective
{Single sentence describing desired outcome}

## Success Criteria
- [ ] {Measurable criterion 1}
- [ ] {Measurable criterion 2}
- [ ] {Measurable criterion 3}

## Plan

### Subgoals

#### SG1: {Subgoal Title}
- **Success:** {Specific criterion}
- **Depends on:** {None | SG#}
- **Thread type:** {business | sales | marketing | engineering}
- **Threads:** {None yet | thread-id, ...}
- **Status:** pending | in_progress | completed

#### SG2: {Subgoal Title}
- **Success:** {Specific criterion}
- **Depends on:** SG1
- **Thread type:** {type}
- **Threads:** {None yet}
- **Status:** pending

### Milestones
- [ ] M1: {25% progress marker} (by {date})
- [ ] M2: {50% progress marker} (by {date})
- [ ] M3: {75% progress marker} (by {date})
- [ ] M4: {Goal achieved} (by {deadline})

### Dependencies
{External dependencies, blockers, or prerequisites}

## State

### Metrics
| Metric | Current | Target | Gap | Trend |
|--------|---------|--------|-----|-------|
| {Primary metric} | {value} | {value} | {value} | → |
| {Secondary metric} | {value} | {value} | {value} | → |

### Execution
- **Active threads:** 0
- **Completed threads:** 0
- **Blocked:** 0

### Trajectory
- **On track:** Unknown (insufficient data)
- **Projected completion:** TBD
- **Risk level:** Low

## Canvas Links

**Validates assumptions:**
- {assumption-id}: "{assumption text}" (10.assumptions.md)

**Informs sections:**
- {section}.md (what updates on success)

## Log
- {created date}: Goal created

Integration

With Canvas

  • Read relevant sections before creating goal (see Canvas Reference)
  • Reference sections in canvas_refs frontmatter
  • Link to assumptions in Canvas Links section
  • Goal completion triggers Canvas updates (assumptions, metrics)

With Threads

  • Subgoals spawn threads when activated
  • Thread completion updates subgoal status
  • Thread Stage 6 (Learning) feeds back to goal state

With Reasoning Gateway

  • Complex decomposition may route through reasoning modes
  • Causal: For operational goals with clear cause-effect
  • Analogical: For novel goals ("this is like...")
  • Dialectical: For goals with competing priorities

Examples

Business Goal (BOOTSTRAP)

User: "I want to hit $50K MRR by end of Q2"

Canvas read:
- 00-mode: BOOTSTRAP
- 11-pricing: $500/mo average, 3 tiers
- 12-costs: $5K/mo burn, need profitability
- 13-metrics: Current MRR $8K, 16 customers
- 04-segments: SMB primary, Enterprise secondary

Goal created:
- id: g-mrr-50k
- type: business
- mode: BOOTSTRAP
- deadline: 2025-06-30
- canvas_refs: [00-mode, 11-pricing, 12-costs, 13-metrics]
- Success criteria: MRR >= $50K, Profit margin >= 30%, CAC payback < 6 months
- Subgoals (revenue-first order):
  - SG1: Close first 3 paying customers
  - SG2: Validate unit economics (LTV:CAC > 5:1)
  - SG3: Scale acquisition (pipeline of 20 leads)
- Canvas Links:
  - A2: "SMB customers convert at 5%" (validates)
  - A5: "$500/mo price point acceptable" (validates)
- Autonomy: ask (cash preservation)

Business Goal (VENTURE)

User: "I want to hit $500K ARR by end of year"

Canvas read:
- 00-mode: VENTURE
- 03-opportunity: TAM $2B, growing 40% YoY
- 13-metrics: Current ARR $50K, 500 MAU
- 14-growth: PLG primary, content secondary

Goal created:
- id: g-arr-500k
- type: business
- mode: VENTURE
- deadline: 2025-12-31
- canvas_refs: [00-mode, 03-opportunity, 13-metrics, 14-growth]
- Success criteria: ARR >= $500K, MAU >= 10K, Growth >= 100% YoY
- Subgoals (growth-first order):
  - SG1: Acquire 5K users (product-led)
  - SG2: Activate 50% to active usage
  - SG3: Convert 5% to paid
- Canvas Links:
  - A1: "PLG drives user acquisition" (validates)
  - A4: "5% free-to-paid conversion achievable" (validates)
- Autonomy: hybrid (speed matters)

Brand Goal

User: "Build my LinkedIn presence for thought leadership"

Canvas read:
- 01-context: B2B SaaS, technical audience
- 07-uvp: "AI-native operations for startups"
- 04-segments: Technical founders, solo operators
- 14-growth: Content marketing as key channel

Goal created:
- id: g-linkedin-authority
- type: brand
- deadline: 2025-06-30 (asked user)
- canvas_refs: [01-context, 07-uvp, 04-segments, 14-growth]
- Success criteria: 10K followers, 5K avg impressions, 2 leads/month
- Subgoals:
  - SG1: Define content pillars (aligned with 07-uvp)
  - SG2: Establish posting cadence (3x/week)
  - SG3: Build engagement network (04-segments audience)
- Canvas Links:
  - A8: "Content drives inbound leads" (validates)

Product Goal

User: "Ship the mobile app"

Canvas read:
- 09-solution: MVP = core workflow + notifications
- 05-problem: "Users need mobile access to approve decisions"
- 01-context: Web app exists, mobile requested by 60% of users
- 02-constraints: 2 developers, Q1 deadline

Goal created:
- id: g-mobile-app-launch
- type: product
- deadline: 2025-03-31 (asked user)
- canvas_refs: [09-solution, 05-problem, 01-context, 02-constraints]
- Success criteria: App in stores, 100 beta users, <1% crash rate
- Subgoals:
  - SG1: Core features complete (09-solution scope)
  - SG2: Beta testing (recruit from existing users)
  - SG3: Store submission
- Canvas Links:
  - A6: "Mobile increases engagement 2x" (validates)

Constraints

Must Have

  • Clear success criteria (measurable)
  • Deadline
  • At least 2 subgoals
  • Autonomy level set

Must Ask If Missing

  • Deadline not specified
  • Success criteria ambiguous
  • Type unclear from context

Must NOT

  • Create goals without user confirmation of structure
  • Set autonomy to auto for high-impact goals without asking
  • Create duplicate goals (check existing first)

Error Handling

Objective too vague:

Ask: "What does '{objective}' look like when achieved?
     Give me 2-3 specific outcomes I can measure."

No deadline:

Ask: "By when do you want to achieve this?
     Options: specific date, relative (3 months), or milestone-based"

Conflicting with existing goal:

Flag: "This overlaps with existing goal '{goal-id}'.
      Should I: (1) Merge as subgoal, (2) Replace existing, (3) Keep both?"