메뉴
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.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.
Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.
Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.
Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.
Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.
Orchestrate a behavior-preserving refactor — confirm tests are green, restructure without changing behavior, keep tests green, review, and gated commit. Use when the structure should improve but behavior must not change.
| name | orch-add-feature |
| description | 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. |
| origin | ECC |
Actor · action · target: orch · add · feature. Thin wrapper over the shared
engine in orch-pipeline.
orch-fix-defect) and not an
alteration of existing behavior (orch-change-feature).orch-pipeline engine with the settings above.security-reviewer if the feature touches a security trigger.Related:
/feature-devis a standalone version of this flow.orch-add-featurediffers by sharing theorch-pipelineengine — the size classifier and the two gates — with the rest of the family, so it right-sizes trivial features to 4 → 5 → 6.
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]