Orch Add Feature
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. Use when adding a capability that does not exist yet.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Orch Add Feature when an AI agent needs a reusable SKILL.md workflow for this job: 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. Use when adding a capability that does not exist yet.
When not to use it
Skip Orch Add Feature when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/orch-add-feature # Save SKILL.md to ~/.claude/skills/orch-add-feature/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/orch-add-feature/SKILL.md. For a shared project, commit the folder at .claude/skills/orch-add-feature/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Orch Add Feature skill for this task: The user wants a capability that does not exist yet ("add", "build",. Confirm any required inputs or files before making changes.What supports this recommendation?
67/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 72/100
- Practical detail
- 62/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# orch-add-feature
Actor · action · target: **orch · add · feature**. Thin wrapper over the shared engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).
## 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-dev` is a standalone version of this flow. `orch-add-feature` > differs by sharing the `orch-pipeline` engine — the size classifier and the two > gates — 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] ```
Intended uses
- The user wants a capability that does not exist yet ("add", "build",
- It is net-new behavior — not a correction (orch-fix-defect) and not an
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.