product-owner

Behaviorally testable acceptance criteria define observable inputs and expected outcomes for each user story. The product-owner skill drafts these criteria alongside explicit out-of-scope constraints to ensure every story is independently shippable and verifiable during sprint planning.

Translating sprint goals into shippable user stories requires breaking objectives into atomic units with consistent templates. This skill generates structured sprint documentation in `/docs/sprint/{name}/user-stories.md`, enforcing domain glossary alignment and logging each story for team review.

Defining out-of-scope boundaries involves explicitly listing what the team will not deliver in the sprint. This skill produces out-of-scope lists within each user story to reduce ambiguity, prevent rework, and keep sprint planning focused on independently shippable units.

A project glossary is optional but recommended for consistent domain terms. This skill enforces glossary alignment from `/docs/project_memory.md` when available and flags any missing terms for the Architect to add during the downstream workflow.

Yes, user story drafting works independently, but the skill is designed to hand off to an Architect for missing glossary terms. It produces structured sprint documentation after the interview phase and before architectural planning, logging each story via `task_log_append`.

User stories often lack testable criteria when sprint goals remain vague. This skill solves that by translating objectives into stories with behaviorally testable acceptance criteria, ensuring each item can be verified through observable inputs and outcomes before sprint execution.