Orch Add Feature
- 2 installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
orch-add-feature is a Claude Code skill that orchestrates building a brand-new feature end to end by delegating research, plan, TDD, review, and gated commit to matching ECC agents.
About
orch-add-feature is a Claude Code skill that orchestrates building a net-new feature end to end. A developer uses it when adding a capability that does not exist yet, delegating research, planning, TDD implementation, review, and gated commit to the matching ECC agents. It is a thin wrapper over the shared orch-pipeline engine and stops at a plan-approval gate and a pre-commit gate.
- Orchestrates building a brand-new feature end to end by delegating each phase to the matching ECC agent
- Runs a research, plan, TDD, review, and gated-commit pipeline with two human gates
- Right-sizes trivial features to skip research and planning, and pulls in a security reviewer on security triggers
Orch Add Feature by the numbers
- 2 all-time installs (skills.sh)
- Ranked #13,958 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
orch-add-feature capabilities & compatibility
- Capabilities
- agent orchestration · feature development · tdd workflow · code review
- Works with
- github
- Use cases
- orchestration · code review · testing
What orch-add-feature says it does
Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent.
It is net-new behavior — not a correction (`orch-fix-defect`) and not an alteration of existing behavior (`orch-change-feature`).
Stop at **Gate 1** (plan approval) and **Gate 2** (pre-commit).
npx skills add https://github.com/affaan-m/ecc --skill orch-add-featureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
What it does
Orchestrate a net-new feature through research, plan, TDD, review, and gated commit by delegating each phase to ECC agents.
Who is it for?
Adding a capability that does not exist yet through a gated, delegated development pipeline.
Skip if: Fixing a broken behavior (orch-fix-defect) or altering existing behavior (orch-change-feature).
When should I use this skill?
The user wants a capability that does not exist yet, phrased as add, build, implement, or support.
What you get
A new feature implemented via TDD and reviewed, committed only after plan approval (Gate 1) and pre-commit confirmation (Gate 2).
- Plan / task_list for the new feature
- TDD-implemented feature
- Reviewed conventional feat: commit
By the numbers
- Phase mask 0-1-2-4-5-6
- 2 human gates (plan approval, pre-commit)
Files
orch-add-feature
Actor · action · target: orch · add · feature. Thin wrapper over the shared engine in `orch-pipeline`.
When to Use
- The user wants a capability that does not exist yet ("add", "build",
"implement", "support …").
- It is net-new behavior — not a correction (
orch-fix-defect) and not an
alteration of existing behavior (orch-change-feature).
Operation settings
- Default size floor: standard — run Research + Plan unless clearly small.
- Phase mask: 0 → 1 → 2 → 4 → 5 → 6 (skip 3 Scaffold; that is MVP-only).
- First move (phase 4): write new failing tests for the new behavior, then
implement to green.
How It Works
1. Run the orch-pipeline engine with the settings above. 2. Classify size first; small / trivial features collapse toward 4 → 5 → 6. 3. Stop at Gate 1 (plan approval) and Gate 2 (pre-commit). 4. Add security-reviewer if the feature touches a security trigger.
Related:/feature-devis a standalone version of this flow.orch-add-feature
differs by sharing the orch-pipeline engine — the size classifier and the twogates — with the rest of the family, so it right-sizes trivial features to 4 → 5 → 6.
Example
orch-add-feature: add OAuth2 login to nws-poller
→ research existing auth libs → plan task_list [GATE 1: approve]
→ TDD each task → code-review (+ security-reviewer: auth path)
→ commit [GATE 2: confirm]Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10FAQ
How is it different from orch-change-feature?
orch-add-feature is for net-new behavior that does not exist yet, while orch-change-feature alters an existing, working feature.
What phases does it run?
Phase mask 0 to 1 to 2 to 4 to 5 to 6, skipping Scaffold (phase 3), which is MVP-only.