42 lines
1.5 KiB
Markdown
42 lines
1.5 KiB
Markdown
---
|
|
name: bugfix
|
|
depth: Minimal
|
|
keywords:
|
|
- fix
|
|
- bug
|
|
- broken
|
|
description: Fix a specific bug
|
|
skeleton: off
|
|
runner: true
|
|
review_cap: advisory
|
|
change_control: relaxed
|
|
---
|
|
|
|
# bugfix scope
|
|
|
|
Minimal depth for fixing one specific bug in an existing codebase. It
|
|
skips ideation entirely (there is no new product to discover), runs
|
|
reverse-engineering to understand the current code, pulls requirements for
|
|
the fix, then generates, tests, and deploys it.
|
|
|
|
Change Control defaults to relaxed: an input that changes after approval is recorded and announced in one line rather than reopening the approval.
|
|
|
|
## Why these stages, why skip those
|
|
|
|
A bug fix is incremental work on a known system. It needs to understand
|
|
what exists (reverse-engineering), state what "fixed" means
|
|
(requirements-analysis), and change-plus-verify (code-generation,
|
|
build-and-test). It does not need market-research, user-stories,
|
|
domain-design, environment provisioning, or broader operational readiness,
|
|
but it retains deployment-pipeline and deployment-execution so the verified
|
|
fix can ship. This scope is one of the three incremental scopes that skip the
|
|
walking-skeleton ceremony (alongside `refactor` and `security-patch`), since
|
|
there is nothing to bootstrap.
|
|
|
|
## Membership
|
|
|
|
Keyword triggers: `fix`, `bug`, `broken` (word-boundary matched, so
|
|
"debug" and "fixture" do not trigger it). Initialization,
|
|
reverse-engineering, requirements-analysis, code-generation, build-and-test,
|
|
deployment-pipeline, and deployment-execution execute; the rest is SKIP.
|