Best fit
- An existing feature works, but the desired behavior is different ("change",
- Distinguish from siblings:
- not broken → not orch-fix-defect (no bug to reproduce).
affaan-m/ECC
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.
80Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "skills/orch-change-feature"Automated source guide
Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Turn orch-change-feature's source instructions into a guide you can follow
According to the pinned SKILL.md from affaan-m/ECC: Actor · action · target: orch · change · feature. Thin wrapper over the shared engine in orch-pipeline.
npx skills add https://github.com/affaan-m/ECC --skill "skills/orch-change-feature"Bring this context
- A concrete task that matches the documented purpose of orch-change-feature.
- The files, examples, or context the task depends on.
- Your constraints, target environment, and definition of done.
Expected outputs
- A result that follows the pinned orch-change-feature instructions.
- A concise record of assumptions, inputs used, and unresolved questions.
- A final check against the source workflow and relevant permission signals.
Key source sections
Read orch-change-feature through these 4 source sections
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
When to Use
An existing feature works, but the desired behavior is different ("change",
An existing feature works, but the desired behavior is different ("change",Distinguish from siblings:not broken → not orch-fix-defect (no bug to reproduce).
Operation settings
Default size floor: small — most tweaks are a function or two.
Default size floor: small — most tweaks are a function or two.Phase mask: 0 → (1 only if the new behavior needs research) → light 2 →First move (phase 4): update the existing tests to express the new
How It Works
1. Run the orch-pipeline engine with the settings above. 2. Keep the plan light — only standard+ size warrants the full planner pass. 3. Stop at Gate 1 (plan / changed-test approval) and Gate 2 (pre-commit). 4. Add security-reviewer if the change touches a security trigger.
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).
Example
Review the “Example” section in the pinned source before continuing.
Review and apply the “Example” source section.
SkillSignal prompt templates
Provide the task, context, and acceptance criteria
These prompts were written by SkillSignal from the source structure; they are not upstream text.
Task-start prompt
Confirm source fit, inputs, and outputs before acting.
Use orch-change-feature to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.
Source-guided execution
Make the Agent explicitly follow the key extracted sections.
Apply the pinned orch-change-feature source to [task]. Pay particular attention to these source sections: “When to Use”, “Operation settings”, “How It Works”, “Example”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].
Result-review prompt
Check omissions, permissions, and source drift before delivery.
Review the current orch-change-feature result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.
Output checklist
Verify each item before delivery
The task matches the purpose documented in the SKILL.md.
The source section “When to Use” has been checked.
The source section “Operation settings” has been checked.
The source section “How It Works” has been checked.
The source section “Example” has been checked.
Inputs, constraints, and acceptance criteria are explicit.
Unverified facts, compatibility, and outcome claims are clearly marked.
Any file, command, network, or data action has been reviewed.
Choose a different workflow
When another Skill is the better fit
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailchurn-prevention
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detaildesign-intelligence
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
What does orch-change-feature do?
Actor · action · target: orch · change · feature. Thin wrapper over the shared engine in orch-pipeline.
How do I start using orch-change-feature?
The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "skills/orch-change-feature". Inspect the command and pinned source before running it.
Which Agent platforms does it declare?
No dedicated Agent platform is declared in the pinned source record.
Repository stars
234,327
Repository forks
35,711
Quality
80/100
Source repository last pushed
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Documentation19/30
Specificity21/25
Maintenance20/20
Trust signals20/25
Compare before choosing
Related Agent Skills and source variants
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
ab-testing by coreyhaines31
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
churn-prevention by coreyhaines31
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
design-intelligence by event4u-app
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
design-system-capture by event4u-app
Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.
existing-ui-audit by event4u-app
Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.
View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min
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).
- not broken → not
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-pipelineengine with the settings above. - Keep the plan light — only
standard+ size warrants the fullplannerpass. - Stop at Gate 1 (plan / changed-test approval) and Gate 2 (pre-commit).
- Add
security-reviewerif 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]
- Source repo
- affaan-m/ECC
- Skill path
- skills/orch-change-feature/SKILL.md
- Commit SHA
- 4e973d3eaf92
- Repository license
- MIT
- Data collected