What does this skill do?

The Skill Feature Change orchestrates the modification of existing features that work correctly but whose behavior needs to evolve. It follows the test-first pattern: first, it updates the tests with the new specification, and then it adjusts the implementation until the tests pass, with review and validation at intermediate checkpoints.

Adjust Alert Threshold
Change configuration settings such as notification thresholds and verify that the tests reflect the new value before modifying the code.
Change the response format
Evolve the output format of an API (e.g., from timestamp to ISO 8601) by first updating the integration and unit tests.
Tests updated before the code
Ensure that the tests reflect the new expected behavior and fail against the current implementation before modifying it.
Integrated Safety Review
Automatically activate security-reviewer when a change triggers security triggers such as authentication or sensitive data.

Usage examples

🔧 Threshold Change
feature-change: Have nws-poller send 2 alerts instead of 3
🔄 API Format
feature-change: Have /api/user return createdAt in ISO 8601 format instead of a timestamp
🧪 Guided test-first
I need to modify the behavior of the discount module so that it applies a 15% discount instead of a 10% discount. Update the tests first, then the implementation.
🛡️ Safety inspection included
Change the login validation so that it also accepts email addresses in lowercase. Since this involves authentication, include security-reviewer.

Features

Strict test-first pattern Update the existing tests to reflect the new specification before making any changes to the implementation, ensuring that the new behavior is reflected.
Control Gates It halts the workflow at Gate 1 (plan approval and modified tests) and Gate 2 (pre-commit validation) for human review.
Resizable By default, it uses the "small" size for localized changes; it scales up to "standard" or higher with the Lite plan when the change warrants it.
Optional security reviewer Automatically enable security review if the change affects sensitive triggers such as authentication or personal data.
Clear distinction from "fix-defect" It does not reproduce an error: it intentionally evolves the behavior of something that already works correctly.

Frequently asked questions

This skill does not reproduce an error: it builds on functionality that works correctly and evolves its behavior to meet a new specification. To fix bugs, use orch-fix-defect.
Because that's what distinguishes a feature change from a bug fix: first, the new expected behavior is defined in the tests (which will fail against the current code), and then the implementation is adjusted until the tests pass.
No specific MCP is required. It runs within Claude's pipeline engine and optionally triggers the security-reviewer if the change affects security triggers.
By default, it uses the "small" size (one or two functions). Upgrading to the "standard" size or higher generates a lightweight plan before touching any tests or code.
Feature Change — Test-First Refactoring with Claude AI

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.