AGENT SKILL

define-goal

Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.

License 许可
Apache-2.0
所属仓库
mintuz/.dotfiles
最近更新
2026-11-13
Stars
★ 3
Forks
1

01 前言 Front Matter

name
define-goal
description
Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.

02 资源文件 2

03 SKILL.md 正文

Define Goal

Overview

Shape the user's intent into an objective an agent can pursue honestly. Prefer measurable outcomes, explicit evidence, and bounded scope over activity descriptions.

This skill covers goal definition and goal-tool creation only. Do not create intermediate planning artifacts, durable snapshots, ledgers, decision logs, or resume files from this skill.

Workflow

  1. Confirm that goal definition is actually needed.

    • Use this skill when the user asks for $define-goal, asks to create or set a goal, asks for the goal tool, or wants help turning an intention into a clear objective.
    • If the user only asks for ordinary implementation work, do the work directly instead of forcing goal creation.
  2. Restate the likely goal in concrete terms. A usable goal names:

    • the specific outcome that will be true
    • the main artifact, system, repo, environment, or user-facing behavior involved
    • how completion will be verified
    • what is in scope
    • what is out of scope when ambiguity would matter
    • the stop condition for asking the user instead of grinding
  3. Make it quantitative when the domain supports it. Prefer numbers that represent real success, not decorative precision:

    • pass/fail validators: exact tests, checks, CI jobs, evals, commands, or acceptance criteria
    • quality thresholds: latency, error rate, cost, accuracy, recall, precision, coverage, flake rate, bundle size, memory, uptime, completion rate, or manual review criteria
    • artifact constraints: file paths, affected modules, allowed commands, output formats, target environments, deadlines, or maximum blast radius
    • evidence counts: number of reproduced failures, successful reruns, reviewed examples, migrated records, addressed comments, or verified cases
  4. Repair weak goals before setting them.

    • Rewrite vague goals into measurable objectives when local context makes the rewrite safe.
    • Ask one concise clarification question when the missing detail changes the intended outcome or validation.
    • Reject pure activity goals such as "make progress," "keep investigating," "improve things," or "work on X" unless they are sharpened into a verifiable outcome.
  5. Check active goal state before creating a goal.

    • Call get_goal.
    • If there is no active goal and the objective meets the quality bar, call create_goal.
    • If there is an active goal that still matches the user's intent, continue using it instead of creating a duplicate.
    • If there is an active goal that conflicts with the new request, ask whether to finish the current goal, mark it complete if done, or start a separate goal-backed thread.
  6. Create the goal only after it passes the quality bar.

    • Use a single concise objective string.
    • Include the verification evidence in the objective itself.
    • Include scope bounds when they constrain the work.
    • Include a token budget only when the user explicitly requested one.
    • Do not call create_goal for an ordinary multi-step task unless the user explicitly asked for goal-backed work.

Goal Quality Bar

Before create_goal, the objective should answer:

  • What concrete thing will be true when this is done?
  • What evidence will prove it?
  • What quantitative or binary threshold defines success?
  • What scope boundaries matter?
  • What should cause the agent to stop and ask?

Good:

Reduce checkout API p95 latency below 250 ms for the documented slow path by making the smallest safe server-side change, then verify with npm run test:checkout and the existing local latency benchmark showing p95 under 250 ms across 3 consecutive runs.

Good:

Resolve the open review comments on PR 123 that request code changes, update only the affected auth files and tests, and verify with the targeted auth test command plus gh pr view 123 showing no unresolved change-request threads.

Weak:

Make checkout faster.

Weak:

Keep investigating the PR comments.

Quantification Heuristics

  • For bugs, define success as reproduction first, fix second, and a failing-then-passing validator when possible.
  • For tests, name the exact command and required pass condition.
  • For performance, name the metric, target threshold, measurement method, and number of runs.
  • For quality work, define an observable acceptance bar such as reviewed examples, lint/typecheck/test pass, or user-approved artifact.
  • For research, define the decision the research must enable, the sources or systems in scope, and the evidence standard.
  • For operations, define healthy state, monitoring window, failure threshold, and rollback or escalation trigger.

Clarifying Questions

Ask only when a reasonable rewrite would risk pursuing the wrong outcome. Keep the question short and oriented around the missing validator or scope boundary.

Useful question shapes:

  • "What metric should define success here: latency, cost, accuracy, or user-visible behavior?"
  • "Which environment should I verify against: local, staging, or production?"
  • "What is the minimum evidence you want before I mark this goal complete?"

If the user cannot provide a metric, propose the most honest binary validator available and ask for confirmation.

04 同仓库更多 Skills

mintuz
mintuz/.dotfiles

no-ai-slop

Edit drafts into sharper, more human writing while preserving the writer's personal voice, or detect AI-slop patterns without rewriting. Use when the user wants a draft clearer, more direct, more opinionated, or less AI-sounding, or asks whether writing reads as AI.

★ 3
mintuz
mintuz/.dotfiles

codebase-design

Design and evaluate deep modules: cohesive responsibility behind a small, stable caller-facing contract, with information hiding, justified seams, explicit effects, dependency strategy, and behavior-focused tests. Use when designing or changing an in-process module or package contract, consolidating shallow pass-through modules, deciding what to hide, comparing alternative interfaces, or asking whether code should be combined or split for leverage and locality. For physical layout use structure-codebase; for public compatibility use api-design; for a repository-wide scan use improve-codebase-architecture. For an already-selected whole-path requirement to support a calibrated net-mechanism-reduction claim, use reduce-system-complexity.

开发工程师设计师视觉设计
★ 3
mintuz
mintuz/.dotfiles

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

前端开发
★ 3
mintuz
mintuz/.dotfiles

vercel-composition-patterns

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

前端开发
★ 3
mintuz
mintuz/.dotfiles

gpt-image-2

Generate images with GPT Image 2 (ChatGPT Images 2.0) inside Claude Code, using your existing ChatGPT Plus or Pro subscription — no separate OpenAI access, no per-image billing. Supports text-to-image, image-to-image editing, style transfer, and multi-reference composition via the local Codex CLI. Triggers on "gpt image 2", "gpt-image-2", "ChatGPT Images 2.0", "image 2", or any explicit ask to generate or edit an image through the user's ChatGPT plan.

图像与多媒体
★ 3
mintuz
mintuz/.dotfiles

clarity

Draft, rewrite, or review reader-facing prose so it is specific, useful, and recognizably the author's without inventing facts or performing humanness. Use for essays, articles, newsletters, documentation, talks, launch copy, and other important prose that feels generic, hollow, or AI-shaped. Supports co-write, rewrite, review, and lint modes.

★ 3