spec-to-stories
Translate a Markdown spec (a Zethus spec or any spec-shaped Markdown) into a set of Jira-ready stories, one Markdown file per story plus an index — each with a user-value title, a user story statement where it fits, 2-4 sentences of context, testable acceptance criteria, out-of-scope, dependencies, a traceability link back to the spec section, and optional sizing notes with no invented story points. Every story carries an explicit INVEST self-check and a flag on any criterion it fails; epics group stories when the spec has phases. Produces drafts only — nothing is created in Jira without explicit human approval in this session. Use when a spec is signed off, or far enough along, and needs to become a batch of stories, or when asked to turn a spec into stories or tickets.
Pinned to revision 1364613d64bc, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/spec-to-stories/SKILL.md
- skills/spec-to-stories/example/0001-toggle-email-independently-of-push.md
- skills/spec-to-stories/example/0002-expose-per-channel-setting-in-the-api.md
- skills/spec-to-stories/example/0003-backfill-existing-users-settings.md
- skills/spec-to-stories/example/index.md
- skills/spec-to-stories/example/spec.md
Every link opens the file at its source, pinned to the revision this page describes.