implement-one-feature

Implement a single feature by enforcing one TASK_ID per session with minimal, targeted code changes. Draft a plan, update tests, run quality gates, record evidence in a progress log, and commit using the tagged task ID.

When implementing small API bugfixes or UI tweaks, run baseline smoke tests first, add or adjust tests, execute quality gates, and perform optional end-to-end verification before marking the task as passing.

Maintain traceability by standardizing evidence capture, appending entries to the progress log, and using commit messages tagged with the specific TASK_ID for complete auditability of the implemented feature.

Yes, passing baseline smoke tests are required before starting. This workflow applies only when the baseline is stable, the selected task is small, well-scoped, and requires minimal code changes.

The best way to structure a single-task plan is to draft it in a dedicated task file, implement the change with corresponding tests, run checks, record evidence in the progress log, and commit with the task ID.

Avoid this workflow if the baseline smoke tests are failing, or if the feature is not small and well-scoped, because this process enforces minimal code changes and strictly prevents scope creep.