Arc Creating User Stories

Create a tracked backlog of independently deliverable user stories. The leading word is verifiable: every acceptance criterion must name the concrete method that proves it.

This skill owns the canonical story format for the arc skill family. For the story-body template, numbering, and acceptance-criteria rules, load STORY_FORMAT.md. For gh commands, labels, Projects, and auth details, load GITHUB.md when you are ready to create issues.

Steps

1. Inspect the request and repo.

   • Identify whether the user wants story creation, not just implementation planning or generic brainstorming.
   • Read enough repo files, PRD/specs, existing issues, and project context to avoid duplicate or imaginary work.

   Completion criterion: every proposed epic is grounded in a user request, existing artifact, or observed codebase gap.

2. Draft the backlog before creating issues.

   • Group stories into epics/themes.
   • Make each story independently deliverable and small enough to be implemented by one agent or developer.
   • Assign priority (P0/P1/P2) and size (S/M/L/XL).
   • Use sequential W-000001 IDs; inspect existing issues first and increment from the highest existing W- number.