Spec

Overview

Use this skill to turn a feature, API, refactor, or product idea into a clear specification that can feed planning and implementation. The output should reduce ambiguity before code is written.

Workflow

1. Identify the problem, goal, users, constraints, and non-goals.
2. Capture the current behavior or system context when relevant.
3. Define user stories or use cases with acceptance criteria.
4. Specify functional requirements, edge cases, error states, permissions, and data handling.
5. Include API, UI, migration, observability, performance, or rollout requirements when applicable.
6. List open decisions and assumptions explicitly.
7. Keep the spec implementation-aware but avoid over-prescribing internal code structure unless required.

Output Pattern

Use this structure by default: