orch-add-feature

Topics in the source

• orch-add-feature
• When to Use
• Operation settings
• How It Works
• Example

Actor · action · target: orch · add · feature. Thin wrapper over the shared engine in orch-pipeline. 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). 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. 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.