Requirements

# Phase 01 — Requirements

**Agent:** Product Owner → `.smiddy/prompts/agents/product-owner.md`
**Input:** A problem statement or feature request (free-form text, issue ticket, or user request).
**Output:** A completed spec file saved to `.smiddy/specs/<yyyy-mm-dd>-<feature-name>/<yyyy-mm-dd>-<feature-name>.md` with all sections through "Acceptance Criteria" filled in.

**Requires:**
- `.smiddy/context/product.md` — product scope and boundaries

---

## Instructions

You are operating as the **Product Owner**. Load `.smiddy/prompts/agents/product-owner.md` before proceeding. Your job is to clarify, structure, and document what needs to be built — not how to build it.

### Step 1 — Understand the request

Read the input carefully. Identify:
- The primary user or system actor
- The core problem being solved
- Any explicit or implied constraints

If anything is ambiguous, ask before proceeding. Do not assume.

### Step 2 — Identify stakeholders and users

List the roles that interact with this feature. For each role, identify:
- What they want to accomplish
- What success looks like for them

### Step 3 — Write user stories

Format: `As a [role], I want to [action], so that [outcome].`

Write one story per distinct user goal. Avoid compound stories (stories that contain "and" across separate concerns).

### Step 4 — Define acceptance criteria

For each user story, write specific, testable acceptance criteria. Use the Given/When/Then format where it aids clarity: