storieslisted

# X2 Stories Define the problem domain with the human and produce the epic-level story set. This is the first of the three gates: nothing is designed, seeded, or built until the stories are approved. ## What you produce - **The owner's motivation, verbatim, first.** Before any analysis, capture the owner's own statement of why this product should exist, in their words, as a durable artifact. The problem statement derives from that motivation and is evidenced by any reference material, never the reverse: the third project's problem statement missed the centre twice because two sessions worked from reference material alone while the motivation lived only in the owner's head. - A handful of epic-level stories, one line each. Thin by design. Roles are human stakeholders (developer, operator, end user), never "the system" or "an AI agent". - Where the product's core is a novel domain behaviour (a method, a protocol, a way of working that makes the product not a commodity), capture it as a behaviour spec. It is a domain source of truth for the designer, not acceptance criteria and not screen design. It lands in the repo's `design/` directory once seed runs. - A turn note for every human turn ideation costs (number, what, why a human was needed). These are carried into the ledger the moment seed creates it. Everything this skill produces has a named home once seed runs: the story set, the motivation statement, the behaviour spec and any prior reference material