goal-setter

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.

242 stars

Best use case

goal-setter is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. 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.

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.

Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.

Practical example

Example input

Use the "goal-setter" skill to help with this workflow task. Context: 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.

Example output

A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.

When to use this skill

  • Use this skill when you want a reusable workflow rather than writing the same prompt again and again.

When not to use this skill

  • Do not use this when you only need a one-off answer and do not need a reusable workflow.
  • Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/goal-setter/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/bellabe/goal-setter/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/goal-setter/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How goal-setter Compares

Feature / Agentgoal-setterStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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`):

```markdown
## 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

```markdown
---
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?"
```

Related Skills

goal-tracker

242
from aiskillstore/marketplace

Track goal progress, derive state from execution, identify gaps, trigger actions. Use for goal status checks, progress reviews, and operational goal management.

azure-quotas

242
from aiskillstore/marketplace

Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: "check quotas", "service limits", "current usage", "request quota increase", "quota exceeded", "validate capacity", "regional availability", "provisioning limits", "vCPU limit", "how many vCPUs available in my subscription".

DevOps & Infrastructure

raindrop-io

242
from aiskillstore/marketplace

Manage Raindrop.io bookmarks with AI assistance. Save and organize bookmarks, search your collection, manage reading lists, and organize research materials. Use when working with bookmarks, web research, reading lists, or when user mentions Raindrop.io.

Data & Research

zlibrary-to-notebooklm

242
from aiskillstore/marketplace

自动从 Z-Library 下载书籍并上传到 Google NotebookLM。支持 PDF/EPUB 格式,自动转换,一键创建知识库。

discover-skills

242
from aiskillstore/marketplace

当你发现当前可用的技能都不够合适(或用户明确要求你寻找技能)时使用。本技能会基于任务目标和约束,给出一份精简的候选技能清单,帮助你选出最适配当前任务的技能。

web-performance-seo

242
from aiskillstore/marketplace

Fix PageSpeed Insights/Lighthouse accessibility "!" errors caused by contrast audit failures (CSS filters, OKLCH/OKLAB, low opacity, gradient text, image backgrounds). Use for accessibility-driven SEO/performance debugging and remediation.

project-to-obsidian

242
from aiskillstore/marketplace

将代码项目转换为 Obsidian 知识库。当用户提到 obsidian、项目文档、知识库、分析项目、转换项目 时激活。 【激活后必须执行】: 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入规则(默认到 00_Inbox/AI/、追加式、统一 Schema) 3. 执行 STEP 0: 使用 AskUserQuestion 询问用户确认 4. 用户确认后才开始 STEP 1 项目扫描 5. 严格按 STEP 0 → 1 → 2 → 3 → 4 顺序执行 【禁止行为】: - 禁止不读 SKILL.md 就开始分析项目 - 禁止跳过 STEP 0 用户确认 - 禁止直接在 30_Resources 创建(先到 00_Inbox/AI/) - 禁止自作主张决定输出位置

obsidian-helper

242
from aiskillstore/marketplace

Obsidian 智能笔记助手。当用户提到 obsidian、日记、笔记、知识库、capture、review 时激活。 【激活后必须执行】: 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入三条硬规矩(00_Inbox/AI/、追加式、白名单字段) 3. 按 STEP 0 → STEP 1 → ... 顺序执行 4. 不要跳过任何步骤,不要自作主张 【禁止行为】: - 禁止不读 SKILL.md 就开始工作 - 禁止跳过用户确认步骤 - 禁止在非 00_Inbox/AI/ 位置创建新笔记(除非用户明确指定)

internationalizing-websites

242
from aiskillstore/marketplace

Adds multi-language support to Next.js websites with proper SEO configuration including hreflang tags, localized sitemaps, and language-specific content. Use when adding new languages, setting up i18n, optimizing for international SEO, or when user mentions localization, translation, multi-language, or specific languages like Japanese, Korean, Chinese.

google-official-seo-guide

242
from aiskillstore/marketplace

Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation

github-release-assistant

242
from aiskillstore/marketplace

Generate bilingual GitHub release documentation (README.md + README.zh.md) from repo metadata and user input, and guide release prep with git add/commit/push. Use when the user asks to write or polish README files, create bilingual docs, prepare a GitHub release, or mentions release assistant/README generation.

doc-sync-tool

242
from aiskillstore/marketplace

自动同步项目中的 Agents.md、claude.md 和 gemini.md 文件,保持内容一致性。支持自动监听和手动触发。