mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-06-14 04:01:30 +08:00
David W Miller
90dfd9505d
* feat: add orch-* orchestrator skill family Lightweight wrappers that orchestrate existing ECC agents through a gated Research -> Plan -> TDD -> Review -> Commit pipeline, right-sized per task. - orch-pipeline: shared engine (phases, size classifier, two gates, agent map) - orch-add-feature/change-feature/fix-defect/refine-code/build-mvp: thin wrappers delegating to the engine * chore: register orch-* family in catalog, command registry, and agent.yaml (post-rebase onto green main) --------- Co-authored-by: ECC Test <ecc@example.test>
1.7 KiB
1.7 KiB
name, description, origin
| name | description | origin |
|---|---|---|
| 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. | ECC |
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
- Run the
orch-pipelineengine with the settings above. - Classify size first; small / trivial features collapse toward 4 → 5 → 6.
- Stop at Gate 1 (plan approval) and Gate 2 (pre-commit).
- Add
security-reviewerif 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.
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]