Follow these steps in order:

Check the output configuration. Look for skills.user-story.format in AGENTS.md. If not configured, see template files in format/ (relative to this skill) to present the available options and ask the user to choose before proceeding.
Understand the project context. Before writing anything, explore the repository to ground the story in the real codebase. Read the README, scan docs/ or any documentation folder, and skim relevant source files (routes, components, models, config). Look for the tech stack, existing terminology, domain language, feature boundaries, and naming conventions the team already uses. This prevents inventing features that already exist and ensures acceptance criteria reference actual UI labels, page names, and workflows.
Identify the user persona, their goal, and the ticket type (Story, Task, or Bug). Use what you learned from the codebase to pick the right persona and to align the story's scope with existing architecture.
Write the ticket following the standards below. Weave in project-specific details — reference real page names, existing components, and established terminology rather than generic placeholders.
Deliver the story using the configured output mode.
If the story covers more than one distinct user goal, ask whether to split it into multiple stories — large stories are harder to estimate and deliver incrementally.

<ticket_types> Story — contains a user story sentence ("As a … I want … so that …") with testable acceptance criteria.

user-story