quick-development

A lightweight workflow handles small bug fixes and minor config updates by enforcing scope validation, integrating diagnostic tools, and applying lightweight code review gates for changes touching fewer than 5 files and requiring fewer than 3 implementation steps.

Fixing an unreproduced bug affecting a couple of files requires a dedicated workflow that integrates diagnostic and debugging tools to structure the process into reproduce, minimize, hypothesize, and fix stages for accurate resolution.

Yes, this lightweight workflow handles minor refactors and single-component edits via a known change path that manages pre-defined small changes with minimal overhead and built-in quality checks to deliver changes quickly without sacrificing correctness.

You should not use a quick development workflow for code changes when the task touches 5 or more files, requires 3 or more distinct implementation steps, or lacks a well-scoped definition, as scope validation routes larger work to a standard workflow.

Validating the scope of a small code change before starting development involves checking that the task touches fewer than 5 files and requires fewer than 3 distinct implementation steps, which automatically routes qualifying tasks into the lightweight workflow.