Write User Story

Turn source material into user story (or multiple stories). Acceptance criteria on each story are the requirements — testable, atomic rules the story must satisfy.

If the source of data is a PR, use qa-pr-requirements-analyzer skill. If the source is a ticket in issue tracking system, ask for MCP connection.

Rules

User story must be (at least, but not limited to):

• Atomic — one actor, one capability.
• Clear — no vague words (fast, relevant, user-friendly, should work, as needed).
• Complete — actor, trigger, outcome, business rules; empty, error, and permission paths covered in AC.
• Consistent — same terms throughout; no contradictions.
• Testable — every story has acceptance criteria with a measurable pass/fail.

Follow these rules: