Prepare Issue (deferred work)

Turn a "we want this eventually" brief into a single, actionable new tracker issue — without implementing anything. The issue must be good enough that a future run of om-auto-fix-issue (or a human) can pick it up cold: either it links a spec that defines the work, or it carries a concrete analysis with step-by-step guidance derived from the actual codebase — and it lands with the SDLC labels that classify it.

This skill only creates issues. To bring an issue that already exists up to standard — infer and apply missing SDLC labels, analyze an attached screenshot with a terse body, clarify the wording, and post the agent's understanding as a comment — run om-auto-manage-issues (single issue or a filtered batch). This skill mutates only tracker state (one issue, maybe comments — plus, on the step 3 path only, a design-only spec PR); it never edits repository source files. If the user wants a full spec written, hand off to om-spec-writing; if they want the work done now, hand off to om-auto-create-pr or om-auto-fix-issue.

Arguments

• {brief} (required) — free-form description of the feature, fix, or task to capture.
• --priority <low|medium|high|extreme> (optional) — override the inferred priority label.
• --risk <low|medium|high> (optional) — override the inferred risk label for the eventual change's blast radius.
• --assignee <login> (optional) — assign the issue. Default: unassigned.
• --title "<exact title>" (optional) — use this title verbatim instead of the Implement: / Fix: convention. om-backlog passes it so tree ids open every title.
• --no-spec (optional) — never author a spec (step 3 is skipped even for a substantial feature); link the covering document the brief names instead, such as ${SPECS_DIR}/product-brief.md. om-backlog passes it because the brief, not a per-story spec, is the design authority at that stage.
• --skip-dedupe (optional) — the caller has already deduplicated (om-backlog searches per story before filing); step 1 then checks only for an existing issue with the exact same title and reuses it, and runs no semantic search.
• {images} (optional) — screenshots or mockups the user pasted with the brief or gave as file paths; attached to the issue as 📸 evidence (see step 5).

Workflow