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.
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]
docker-patternsaffaan-mDocker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.4,8004,800 instalaciones en skills.sh0
security-reviewaffaan-mUse this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.4,8004,800 instalaciones en skills.sh0
backend-patternsaffaan-mBackend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.4,7004,700 instalaciones en skills.sh0
frontend-patternsaffaan-mFrontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance.4,7004,700 instalaciones en skills.sh0
coding-standardsaffaan-mBaseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.4,5004,500 instalaciones en skills.sh0
