mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-06-11 02:33:10 +08:00
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.4 KiB
1.4 KiB
description
| description |
|---|
| Orchestrate altering an existing, working feature to new desired behavior — update tests to the new spec, change impl, review, gated commit. Wrapper for the orch-change-feature skill. |
/orch-change-feature
Manually launch the orch-change-feature orchestrator: change behavior that already works to a new desired spec, tests-first.
Usage
/orch-change-feature <the new desired behavior>
Examples:
/orch-change-feature make nws-poller alert at 2 warnings instead of 3
/orch-change-feature instead of sorting by date, sort by priority
What It Does
Invoke the orch-change-feature skill with $ARGUMENTS as the request. The skill
(via the shared orch-pipeline engine) will:
- Classify size (default floor: small) and state the tier.
- Light plan only if the new behavior needs research. → GATE 1 (approve changed-test plan).
- Update the existing tests to express the new behavior, then change the implementation until green. (Changing the tests first is what makes this a tweak, not a fix.)
code-reviewer(+security-revieweron a security trigger), then commit. → GATE 2.
Use this only when the feature works but should behave differently — not for
bugs (/orch-fix-defect) or net-new capability (/orch-add-feature).
If $ARGUMENTS is empty, ask the user what behavior should change.