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".
Permissions
Files
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".
Select the multi-optimized profile without duplicating the base workflow.
--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.
Version history
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.
ALWAYS check first: Apply .ai/skills/om-implement-feature-multi-optimized/SKILL.md when present; safety rules still win.
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.
Read and execute om-implement-feature in full with --profile multi-optimized.
Preserve its worker packets, spec and final councils, same-family independence rule, stage-only boundary, and report.
Shared communication, marker, label, and safety rules: references/rules.md. They always apply.
Do not restate or replace any base workflow phase.
Treat review from the implementation worker's family as a self-check, not an independent vote.
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 — an optimized profile needs an audited implementation worker; adding a reviewer alone cannot unblock it — 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.
In these kits
More from @openmercato
Works with
Claude, Codex, Cursor & more