oneshot

To automate rapid code changes for small fixes, use an Explore → Code → Test workflow that minimizes scope and risk. It resolves inputs, locates edit targets deterministically, and executes focused edits quickly to ship isolated refactors or small feature tweaks without lengthy planning overhead.

To implement a small, well-defined feature tweak quickly, execute a focused workflow from input resolution to verified code and tests. It locates the edit target with deterministic steps, minimizes unnecessary exploration, and enforces complexity checks to ensure rapid, safe delivery within known codebase boundaries.

You need a circuit breaker for code editing workflows when a task proves more complex than initially anticipated. It acts as a guardrail by automatically suggesting alternative planning workflows, ensuring that rapid, focused changes do not proceed if the scope exceeds expected boundaries.

You cannot use this rapid change workflow for large, multi-concern features. It is designed strictly for clearly scoped tasks like small fixes or isolated refactors within a known codebase, and its circuit breaker will route complex tasks to more appropriate planning workflows.

Input resolution for automated code edits anchors a precise task by extracting requirements directly from user requests or issue references. This process ensures the workflow targets the exact edit location and scope needed before executing any code modifications or testing procedures.