A few short questions, plain English, no jargon. Your answers become Claude's standing instructions.
The product or system these stories are written for.
Describe the feature or epic to break down. Include goals, known constraints, and what "done" looks like.
The main user type in the story statements, e.g. "project lead" or "enterprise admin."
Known edge cases, error states, or constraints that should appear as acceptance criteria.