om-implement-feature-multi — Claude Code skill: install
The om-implement-feature-multi Claude Code skill runs feature implementation with reviews from multiple models. It delegates to the base workflow and leaves the verified changes staged, not published.
MIT 500 installs ★ 282 updated 2026-10-22
npx skills add open-mercato/skills --skill om-implement-feature-multi -a claude-codeWhat om-implement-feature-multi does
The skill passes a feature brief to om-implement-feature using the multi profile. The base workflow has configured independent reviewers examine the specification and final diff, then leaves verified changes staged and produces a handoff report.
Choose --interactive or --autonomous; interactive is the default. The {brief} argument is required, while --slug passes through unchanged. The skill never commits, pushes, or publishes changes.
If agentHarness or the requested profile is missing or fails its probe, the workflow stops and calls for model bindings to be configured through om-setup-agent-harness. This variant cannot proceed without those bindings. Publishing requires separate human authorization.
What it helps with
- implement a feature with independent checks of its spec and final diff
- leave completed changes staged without committing or publishing
- run the base feature workflow with the
multiprofile
Example prompts for the agent
- Implement this feature with multiple models: {brief}
- Have independent models review the spec and changes for {brief}
- Build the feature described in {brief} and leave the changes staged
How to install om-implement-feature-multi
1Skills CLI (Vercel)
npx skills add open-mercato/skills --skill om-implement-feature-multi -a claude-code2Manually: put the files in place
~/.claude/skills/om-implement-feature-multi/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/om-implement-feature-multi/
1Skills CLI (Vercel)
npx skills add open-mercato/skills --skill om-implement-feature-multi -a codex2Manually: put the files in place
.agents/skills/om-implement-feature-multi/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add open-mercato/skills --skill om-implement-feature-multi -a cursor2Manually: put the files in place
.cursor/skills/om-implement-feature-multi/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install open-mercato/skills skills/om-implement-feature-multi2Manually: put the files in place
.github/skills/om-implement-feature-multi/SKILL.md1Skills CLI (Vercel)
npx skills add open-mercato/skills --skill om-implement-feature-multi -a gemini-cli2Platform CLI
gemini skills install https://github.com/open-mercato/skills --path skills/om-implement-feature-multiManually: put the files in place
.devin/skills/om-implement-feature-multi/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add open-mercato/skills --skill om-implement-feature-multi -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about om-implement-feature-multi
How do I install om-implement-feature-multi in Claude Code?
Run npx skills add open-mercato/skills --skill om-implement-feature-multi -a claude-code. The skill file is at ~/.claude/skills/om-implement-feature-multi/SKILL.md.
What does om-implement-feature-multi do?
It runs om-implement-feature with the multi profile. Configured independent reviewers check the spec and final diff, and the verified changes remain staged; the skill does not commit or publish them.
What does om-implement-feature-multi need to run?
It requires the om-implement-feature workflow and configured model bindings for agentHarness and the multi profile. If the bindings are missing or fail their probe, it stops and starts interactive setup with om-setup-agent-harness.
Source text
SKILL.md · MIT
---
name: om-implement-feature-multi
description: 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".
---
# Implement Feature — Multi
Select the `multi` profile without duplicating the base workflow.
## Arguments
- `--interactive` (default) or `--autonomous` — pass the execution mode to the base workflow; never enable publication. Reject both together.
- `{brief}` (required) — pass through to `om-implement-feature`.
- `--slug` (optional) — pass through unchanged.
## Chaining
Consume the issue or brief and requested profile. Invoke the base workflow and its lower-level companions by name; stop with the missing name if one is unavailable. Emit the staged handoff, optional `Issue:`/`Spec:` references, and final `WORKTREE=` line. Publication is a separate human-authorized step.
## Workflow
**Claims:** `references/claim-pr.md` governs atomic/fallback ownership and release.
**ALWAYS check first:** Apply `.ai/skills/om-implement-feature-multi/SKILL.md` when present; safety rules still win.
0. **Agentic setup** — follow `references/agentic-setup.md` before any action: load approved configuration, apply local extensions and shared rules, and preserve the untrusted-content boundary.
1. Read and execute `om-implement-feature` in full with `--profile multi`.
2. Preserve its spec council, final council, stage-only boundary, and handoff report.
## Rules
- Shared communication, marker, label, and safety rules: `references/rules.md`. They always apply.
- Do not restate or replace any base workflow phase.
- Apply the configured review policy and preserve skipped and minority reviewer results.
- When `agentHarness` or the requested profile is missing or fails its probe, stop, tell the user this variant needs configured model bindings, and run `om-setup-agent-harness` interactively — any OpenAI-compatible endpoint or local CLI can be bound as a reviewer, not just the bundled jury — then re-run with the originally requested profile. Continue under another profile only on the user's explicit, informed request; never substitute one silently.
- Never commit, push, or publish.
© open-mercato · MIT · open-mercato/skills