full-cycle-fast

Automate a lightweight development workflow by running an Analyze, Plan, Build, Test, and Ship sequence. This process applies to small feature work like 3-10 file changes, bug fixes, and config updates, delivering changes quickly without ceremony overhead.

The best workflow for shipping small code changes without ceremony overhead is a minimal end-to-end sequence that skips mandatory research or review gates. It provides a predictable path to deployment for 3-10 file changes that follow existing patterns.

You can use a full development pipeline for simple bug fixes and config updates, but it is often overkill. A minimal workflow provides the necessary structure through an Analyze to Ship sequence without slowing down delivery for 3-10 file changes.

Start the build and test cycle by invoking the workflow with a task description. This triggers the automated Analyze, Plan, Build, Test, and Ship sequence to handle your quick code changes end-to-end with minimal ceremony.

You should avoid using a minimal workflow when your task requires extensive research or mandatory review agents. This approach is designed for clear requirements and 3-10 file changes, making it unsuitable for complex features needing full pipeline gates.