# Agent Skill Bundle — Scope & Acceptance Criteria

> Generated from the canonical public Skill source. This bundle is an invocation artifact, not a separate editable source.

## Agent instruction

Apply this Skill to the user’s actual task. Follow its inputs, behavior, guardrails, outputs, and verification criteria. Do not merely explain or summarize the Skill. If required task context is missing, ask only for the missing information that blocks correct execution.

## Skill identity

- source: skills/scope-acceptance-criteria
- canonical human page: https://wbeen-personal-kb.vercel.app/skills/scope-acceptance-criteria/
- version: 0.1.0
- workflow phase: clarify
- invocation: either

## Skill contract

Convert an intended outcome into explicit scope, exclusions, observable acceptance criteria, and a smallest safe next action.

### Inputs

- Desired outcome
- Known constraints and exclusions
- Stakeholders or intended users
- Available evidence and verification surfaces

### Outputs

- In-scope behavior
- Explicit non-goals
- Observable acceptance criteria
- Evidence plan and stop conditions

### Guardrails

- Do not turn assumptions into acceptance criteria without labeling them.
- Keep non-goals visible so scope cannot silently expand.
- Prefer observable evidence over subjective completion language.
- Stop when required authority or evidence is unavailable.

### Verification

- Another person can tell what is in scope and what is not.
- Each acceptance criterion has an observable check or explicit limitation.
- The next action is small enough to execute without reopening the whole request.

### Source instructions

## What it does

Scope & Acceptance Criteria turns an intention into a bounded, reviewable work packet. It makes the desired outcome, exclusions, evidence, and stop conditions explicit before implementation begins.

## When to reach for it

Use it when a request can be interpreted in several ways, when more than one agent or person will touch the work, or when approval depends on evidence rather than a persuasive summary.

## What one run does

1. Restate the desired outcome in user-observable terms.
2. Separate committed scope from assumptions and follow-up ideas.
3. Name explicit non-goals and boundaries.
4. Write acceptance criteria that can be checked.
5. Identify evidence, dependencies, and a stop condition.

## Common failure modes

- Writing implementation tasks before agreeing on the outcome.
- Hiding out-of-scope work in vague acceptance language.
- Using “looks good” as the only verification criterion.
- Continuing after a missing dependency or authority should have stopped the work.

## It’s working if

A different agent can execute or review the work packet without inventing missing scope, and every acceptance criterion points to an observable result.

## Where it fits

This is a **Clarify**-phase skill. It follows source extraction or a handoff when needed and creates the boundary that Execute and Verify work can rely on.

## Completion rule

Return the useful task result first. Then state briefly which verification criteria passed, which could not be checked, and any stop/escalation condition that remains.