Backlog (epics, stories, tasks from a brief or a spec)

The step between a product brief and Intake. om-discover leaves product-brief.md; om-spec-writing leaves a spec with Phasing; this skill turns either into a tree of tracker issues that om-auto-fix-issue can pick up one by one: epics for the Scope's Now items or the spec's Phases, stories for the user-facing outcomes inside them with acceptance criteria, tasks only where a story needs decomposition. Every issue is filed through om-prepare-issue with --title, --no-spec, and --skip-dedupe, so the labels, the rationale comment, and the body template are its, while this skill owns the tree ids, the one dedupe pass, the acceptance criteria, and the epic checklists.

Arguments

• {source} (required) — a repo-relative path to product-brief.md or to a spec with a ## 📋 Phasing / ## 📋 Implementation Plan section.
• --epic <id> (optional) — file only this epic (E02) and its children.
• --prefix <letters> (optional) — the id prefix in titles. Default E (E01, E01-S02, E01-S02-T01).
• --assignee <login> (optional) — passed through to om-prepare-issue for every issue.
• --dry-run (optional) — draft and show the tree, write nothing; runs without a tracker (no setup, no dedupe) and never triggers om-setup-agent-pipeline.

Workflow

ALWAYS check first: Apply .ai/skills/om-backlog/SKILL.md when present; safety rules still win.