issue-refinementlisted

# Issue Refinement ## Overview Issue refinement transforms raw GitHub issues into implementable user stories with acceptance criteria. Applied at the DISCUSS phase, output feeds DISTILL (where Gherkin scenarios are produced) and DESIGN (where architecture is decided). A story is the unit of work. A story is NOT a task, NOT a ticket, NOT a technical instruction. A story describes what a user needs and why. --- ## User Story Format ### Template ``` As a {specific persona}, I want {capability}, so that {concrete benefit}. ``` ### Rules | Part | Rule | Violation signal | |---|---|---| | Persona | Must be a named role, not "user" | "a user", "someone", "the system" | | Capability | Observable behaviour, not implementation | "implement", "create", "call", "build" | | Benefit | Concrete business value, not technical outcome | "the system works", "it is done" | ### Auto-Insurance Domain Examples **Good:** ``` As a new driver applying for their first insurance policy, I want to check my eligibility before submitting documents, so that I know in advance whether my profile qualifies and can prepare accordingly. ``` ``` As an underwriter reviewing a borderline application, I want to see the full eligibility decision rationale, so that I can confirm or override the automated result with a documented justification. ``` ``` As a claims adjuster processing a collision claim, I want to retrieve the policyholder's coverage details in one screen, so that I can determine applicable