define-task

What it does and when to use it

Define a task before work starts -- interview the user about it, agree on a goal, and agree on how to verify the goal is met. Use when the user wants to develop a new feature or start any non-trivial task, says "let's define the task", "let's brainstorm", "what should the goal be", or invokes /define-task.

Triggers from the description

How it works

1. 1. Interview
2. 2. Goal
3. 3. Verification
4. Output

---
name: define-task
description: Define a task before work starts -- interview the user about it, agree on a goal, and agree on how to verify the goal is met. Use when the user wants to develop a new feature or start any non-trivial task, says "let's define the task", "let's brainstorm", "what should the goal be", or invokes /define-task.
license: MIT
---

# Define Task

Before anything gets built, settle three things with the user, in order.

## 1. Interview

Ask about the task until you understand what the user wants and why. Ask one question per message, and wait for the answer before you ask the next one. A compound question ("A? Also, B?") or a follow-up tacked onto the main question counts as two, so pick the most important one and save the rest. Read the project first (code, diary, docs), so you don't ask what it already answers. Push back on vague answers and unnecessary scope.

## 2. Goal

Propose a goal: a short statement of the outcome, not the implementation. Name what is out of scope if that isn't obvious. Refine it with the user until they explicitly agree.

## 3. Verification

Propose how to check that the goal is met. Prefer checks an agent can run, like tests, commands, or measurements. Where a check needs a human, write it as concrete steps. Every part of the goal needs at least one check, and each check must be able to fail. Refine it with the user until they explicitly agree.

## Output

End with the agreed **Goal** and **Verification**. If a diary entry is being started for the task, put both at the top of it, before the first step, so builders can work from them.

Versions

The database has no other skills named define-task.

Database snapshot: 13.11.2026 · package version cd8050b4153f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100goal
  Use when the user says 'goal', 'set a goal', 'define the goal', 'plan this properly', or starts a task that needs a clear finish line and verification. Structures work into TASK / WHY / OUTCOME / CONSTRAINTS / VERIFICATION before execution begins.
• 100define
  Use when a new feature request, bug report, or work request needs requirements defined before implementation
• 100agree-acceptance
  Agrees what done looks like before work starts: concrete checks, who accepts, what the agent must not do, plus examples (one failing) for variable output. Use when starting any task whose result someone else will rely on.
• 95define-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…
• 100verifying-outcomes
  Use when the user asks to 'verify', 'did this actually work', 'is X really done' — or before you claim a task is complete and before closing an issue or merging a PR. Goal-backward verification — checks whether the desired outcome was achieved, not whether tasks were marked done.
• 100sdf-requirements
  Co-write a requirements document with the user: dig into the why behind a request, check the as-is system, and agree on the experience, scope, and acceptance examples before any design starts. Use when the user brings a feature request, says "let's define requirements", or…