mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-06-14 04:01:30 +08:00

Files

T

David W Miller 90dfd9505d feat: add orch-* orchestrator skill family (#2153 )

* 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>

2026-06-07 16:15:31 +08:00

1.7 KiB

Raw Blame History

name, description, origin

name	description	origin
orch-change-feature	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.	ECC

orch-change-feature

Actor · action · target: orch · change · feature. Thin wrapper over the shared engine in orch-pipeline.

When to Use

An existing feature works, but the desired behavior is different ("change", "adjust", "make it also …", "instead of X do Y").
Distinguish from siblings:
- not broken → not orch-fix-defect (no bug to reproduce).
- not new → not orch-add-feature (the capability already exists).

Operation settings

Default size floor: small — most tweaks are a function or two.
Phase mask: 0 → (1 only if the new behavior needs research) → light 2 → 4 → 5 → 6.
First move (phase 4): update the existing tests to express the new desired behavior, then change the implementation until they pass. Changing the tests first is what separates a tweak from a fix.

How It Works

Run the orch-pipeline engine with the settings above.
Keep the plan light — only standard+ size warrants the full planner pass.
Stop at Gate 1 (plan / changed-test approval) and Gate 2 (pre-commit).
Add security-reviewer if the change touches a security trigger.

Example

orch-change-feature: make nws-poller alert at 2 warnings instead of 3
→ update threshold tests to new spec → change impl to green
→ code-review → commit  [GATE 2: confirm]

1.7 KiB Raw Blame History