leanbusqts Implement
Objective
- Apply the approved change precisely.
- Minimize blast radius and keep behavior aligned to requirements.
When to use
- Requirements or spec are clear and approved.
- A behavior change is expected.
Inputs
- User instructions, spec, and acceptance criteria.
- AGENTS.md, rules, and relevant code/tests.
- Any clarifications already answered.
Process
- Confirm scope and acceptance criteria; note exclusions.
- Plan minimal changes; avoid refactors outside scope.
- Implement with small, focused edits.
- Update/add tests if behavior changes.
- Self-review for correctness and unintended impact.
Outputs
- Files changed and intent.
- Notes on tests added/updated.
- Any residual risks or follow-ups.
Edge cases
- If scope is unclear, pause and ask before coding.
- Avoid drive-by refactors; defer to refactor skill if needed.