/templates

{Feature Name} — Spec

Author this top to bottom. Requirements first, then design, then tasks. See the spec-authoring skill for guidance.

Requirements

Requirement 1: {short title}

User Story: As a {role}, I want {capability}, so that {benefit}.

Acceptance Criteria

1. THE {system} SHALL {behaviour}.
2. WHEN {trigger}, THE {system} SHALL {behaviour}.
3. IF {unwanted condition}, THEN THE {system} SHALL {behaviour}.

Requirement 2: {short title}

User Story: As a {role}, I want {capability}, so that {benefit}.

Acceptance Criteria

1. WHERE {condition}, THE {system} SHALL {behaviour}.

Design

Describe how the system meets the requirements. Each design element should trace back to at least one requirement.

• Components: ...
• Data & state: ...
• Screens / navigation: ...
• Key decisions: ...
• Traceability: Requirement 1 → ... ; Requirement 2 → ...

Tasks

Ordered, implementable tasks. Each task should trace back to a design element.

1. {task} (design: ...)
2. {task} (design: ...)
3. {task} (review: testing)