Auto Write Spec (brief/issue → spec PR)

Run unattended: the user starts you and comes back to a published spec PR — the spec document, resolved-assumptions comment, and (for UI-facing features) mockups and screenshots attached as PR evidence. Composition, not reinvention: om-spec-writing --autonomous writes the document, om-open-pr ships it, the browser-provider descriptor captures visuals.

Arguments

• {brief} or {issueId} (one required) — a free-form feature brief, or a tracker issue id to read the brief from (get-issue). With an issue, the run is issue-driven: claim protocol applies and the PR carries Refs #{issueId}.
• {repo} (optional) — owner/name; infer from git remote if omitted
• --slug <kebab-case> (optional) — override the slug used in branch and spec filenames
• --no-mockups (optional) — skip step 5 even for UI-facing specs
• --force (optional) — bypass the claim-conflict check

Chaining

The spec PR this skill opens is the natural input of om-auto-implement-spec (or om-auto-fix-issue's feature route), which keeps it design-only and ships the implementation on its own PR referencing it (Refs #{specPr}). Always end with the PR: / Spec: (and Issue: when issue-driven) reference lines. If an open PR already carries a spec for this brief/issue (via search-prs), stop and report it — never open a duplicate.

Companion skills (all optional, with fallbacks): om-spec-writing (required — the document engine), om-open-pr (PR opening; inline create-pr fallback per references/pr-finalize.md), om-prepare-test-env + browser provider (mockups/screenshots; degrade to text-only), om-auto-implement-spec (the follow-on).

Workflow