om-implement-feature-multi
/om-implement-feature-multi
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".
- Author
- open-mercato ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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".
Triggers from the description
Original author 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".
How it works
- Arguments
- Chaining
- Workflow
- Rules
SKILL.md preview
---
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.
Files in this package (5)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
- references/agentic-setup.md 3 KB
- references/claim-pr.md 14 KB
- references/rules.md 7 KB
Versions
The database has no other skills named om-implement-feature-multi.
Database snapshot: 13.11.2026 · package version 09b80bd1af00 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90om-fix-issue-multi
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… - 90om-implement-feature-multi-optimized
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… - 96skill-staged-review
Use when a PR or feature needs both specification and code-quality review - 100implement-feature
End-to-end feature implementation workflow. Use when the user says "implement", "build feature", "work on task", "start implementation", or any feature development work. Covers plan review, test writing, implementation, verification, and delivery. - 100implement-feature
Use when the user says "implement", "build feature", "work on task", or once a plan or story is approved and you're about to start building. The end-to-end feature-implementation workflow; delegates the final handoff to completing-a-task. - 90implement
Implement one phase of a feature from its AI-SPEC. Use when the user asks to implement, build or code a feature phase that already has an AI-SPEC in docs/features/<Feature>/.