Turn a free-form brief into an execution plan, implement it **one commit per Step** in an isolated worktree, batch verification proofs at checkpoints, keep a live handoff doc and append-only notification log, and open a labeled PR against the configured base branch.

Take a tracker issue end to end without disturbing the user's active worktree. This skill classifies the issue, then handles both shapes of work itself: a **bug** drives the autofix chain (`om-verify-in-repo` → `om-root-cause` → `om-fix` → `om-open-pr` → `om-auto-review-pr` → `om-auto-qa-p

Take one open PR by number and make it mergeable without merging it: bring it up to date with the base branch, then iterate review-autofix, CI stabilization, and UI verification until it is approvable, green, and QA-evidenced. Non-blocking review findings (nits, low-severity, out-of-scope) become tr

Run unattended: the user starts you with a spec reference and comes back to an **implemented, code-reviewed, UI-verified, ready PR** with screenshots of the working app in its comments. This skill is deliberately thin — resolution + routing; `om-auto-create-pr` / `om-auto-continue-pr` own the impl

Raise the quality of issues that **already exist**, in bulk or one at a time, without touching repository source. For each issue in scope this skill: applies the SDLC labels it is missing (one category, one priority, one risk — inferred per `SDLC.md`); and, when the issue is **laconic** (a near-em

Work the queue of open PRs a human labeled `automerge` until each one is provably ready to merge — and, in `prepare-and-merge` mode, merged. Readiness requires **no human veto**, protected-area human approval when applicable, and **three signals**, each recorded as a label this skill alone writes:

Run the app locally, exercise the changed surfaces through a real browser, and produce concrete visual evidence — screenshots plus a pass/fail report. When a tracker is configured and a PR number is given, hand that evidence to reviewers as a PR comment (and, opt-in, sign the PR off). When there i

Translate a window of merged pull requests into a practical manual verification plan a human tester can follow: PRs grouped into a handful of testing areas, a recommended testing order, and per area **where to click**, **what to verify**, and **what can go wrong**, with a full PR-by-PR appendix for

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 f

PR: #27

Run an arbitrary autonomous task end-to-end and ship it as a PR against the configured base branch. Drafts a Progress-tracked execution plan, commits on a fresh worktree branch, implements phase-by-phase, runs the configured validation gate, applies pipeline labels. Long plans hand off to om-auto-create-pr-loop automatically. Resumable via om-auto-continue-pr.

Draft a CHANGELOG.md release entry in an emoji-driven format for every PR merged since the last release, then delegate to om-auto-create-pr so it lands as a docs PR against the configured base branch. Honors the Supersede Credit Rule and verifies every credit against commit authorship, so carry-forwards and umbrella merges credit the contributor rather than the merger. Use at release time.

Verify that the current branch is ready to publish by running every configured validation command in order, fix straightforward failures (including locale-file drift when the repo checks it), and once everything passes commit and push the current branch. Use when the user asks to check the branch, make CI-style verification pass, then commit and push.

> 🧑‍💻 Interactive — acts once, may ask questions, hands control back

Thin cross-model alias for om-fix-issue that reviews the diagnosis and final diff with configured independent advisors, then leaves the verified fix staged and unpublished. Use when the user says "fix with multiple models", "cross-model staged fix", "multi review this issue", or "napraw issue z wieloma modelami".

Thin combined alias for om-fix-issue that uses configured implementation workers and independent review advisors, then leaves the verified fix staged and unpublished. Use when the user says "multi optimized issue fix", "workers plus model council", "cheap cross-model staged fix", or "napraw issue multi optimized".

Shared internal runtime for configurable staged-only implementation workers, evidence-gated work packets, and multi-model review councils. Use indirectly through om-fix-issue, om-implement-feature, or om-setup-agent-harness; do not use it to publish, commit, push, or open a pull request.

Thin cross-model alias for om-implement-feature that reviews the spec and final diff with configured independent advisors, then leaves the verified feature staged and unpublished. Use when the user says "implement with multiple models", "cross-model staged feature", "multi review this feature", or "zaimplementuj z wieloma modelami".

Thin combined alias for om-implement-feature that uses configured implementation workers and independent review advisors, then leaves the verified feature staged and unpublished. Use when the user says "multi optimized feature", "workers plus model council", "cheap cross-model staged feature", or "zaimplementuj feature multi optimized".

Build a neutral clickable low-fi prototype from a product brief during discovery, after the first synthetic panel and before refreshing the brief or drafting a backlog. Preserve business rules and explicit assumptions, simulate the chosen flow locally, and verify navigation and relevant states in a browser. Use for discovery wireframes or testing a flow before detailed design.