skill by

OM Prepare Issue

Create one well-formed tracker issue from a brief without implementing it — dedupes against existing issues and PRs, links a covering spec (authoring one via om-auto-write-spec on a design-only PR when a feature needs it), attaches user-provided images as tracker evidence, otherwise embeds step-by-step guidance, and applies SDLC labels on creation. For existing issues use om-auto-manage-issues. Use for "file an issue for X", "park this idea".

Add skill

Follow @openmercato

Permissions

Files

SKILL.md

om-prepare-issue

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 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 (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 ; if they want the work done now, hand off to or .

5 files · 25 KB12 KB

Install

It’s free, and every skill you add syncs into every AI tool on your computer, instantly.

Get the Skillet appor

npx skilletmd add @openmercato/om-prepare-issue -y

Version history

## Summary - {one-line goal from the brief} ## Spec - Implementation spec: `{spec path}` ({link})  ## Analysis  - Affected areas: {modules/files} - {expected vs actual, root-cause hypothesis for bugs} ## How to implement 1. {concrete step — file/function level} 2. {concrete step} 3. {tests to add and where} ## Compatibility notes - {None | protected surfaces touched and the required migration path per BACKWARD_COMPATIBILITY.md} ## How to pick this up - Run `om-auto-fix-issue {thisIssueNumber}` (it handles both bugs and features), or hand the spec/analysis to `om-auto-create-pr` as the brief. When step 3 authored a spec PR, implement with `om-auto-implement-spec {specPrNumber}` or `om-auto-fix-issue {thisIssueNumber}` — the spec PR stays design-only; implementation ships on its own PR referencing it. ## Out of scope - {non-goals, so the implementer does not gold-plate}

OM Prepare Issue

Prepare Issue (deferred work)

Arguments

Workflow

Rules

Security boundaries