orc-mini

Orchestrates lightweight feature implementation via a single subagent with a build-test smoke gate.

6|1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/azure-id/orc --skill orc-mini-azure-id
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orc-mini
Source: https://github.com/azure-id/orc/tree/main/templates/skills/orc-mini
Command: npx skills add https://github.com/azure-id/orc --skill orc-mini-azure-id

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Full multi-phase orchestration pipelines are overkill for small, well-scoped changes, adding review, verification, and scoring overhead that slows down simple feature work. This Skill provides a trimmed orchestration lane that keeps intake, planning, and dispatch discipline while skipping the heavyweight phases. ## Core Features & Use Cases - Single-subagent execution: Dispatches one Sonnet 5 high-effort executor for implementation instead of multi-wave parallel task scoring. - Smoke gate quality check: Runs a read-only build+test gate after execution that blocks shipping on red, with one automatic repair re-dispatch. - Lighter intake and planning: Asks only medium-tier intake questions with soft sign-off, plus a one-line complexity read that recommends switching to the full flow when a task is too large. - Use Case: You want to add a --json flag to a CLI command. Invoke the mini lane, answer four intake questions, and it plans, dispatches one executor, runs the test suite as a gate, optionally authors extra tests, and ships the commit. ## Quick Start Ask the assistant to use orc-mini to implement a small, well-scoped change such as adding a flag to an existing CLI command.

Frequently Asked Questions about orc-mini

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a small feature quickly with Claude Code?▼

Invoke the orc-mini lane with a scoped request such as adding a flag to one command. It runs a light intake, dispatches one Sonnet 5 high-effort executor, runs a build+test smoke gate, and ships the change without full review phases.

What is the difference between orc-mini and the full orc orchestrator?▼

orc-mini skips full code review, verification, and summary phases, uses one executor instead of scored parallel waves, and replaces the scoring table with a one-line complexity read. It adds a smoke gate that blocks shipping when build or tests fail.

When should I not use orc-mini for a task?▼

Avoid it for complex, high-risk work with many interdependencies, core or shared surfaces, or security-sensitive changes. The complexity read recommends switching to the full flow, and you can switch mid-run since both share the same run folder format.

Does orc-mini run tests before committing code?▼

Yes, the Phase M smoke gate runs build and tests read-only after execution. A red result blocks any commit offer, triggers one repair re-dispatch, and a second failure stops the run with an honest report.

Can orc-mini write tests for the changes it makes?▼

Yes, after a green smoke gate it optionally dispatches a test-authoring subagent that writes automated tests, a TEST-PLAN.md, and curl bundles for HTTP APIs into a test-generator folder. It never runs those tests itself.