Sheldon Finlay
60ce0fef54
- Remove blanket "write tests" instructions; tests only when acceptance criteria require them - Replace arbitrary "30-50% rejection rate" with clear directive - Replace "4/5 threshold" with "majority of claims" rule - List concrete quality gate commands instead of "whatever project uses" - Remove "learnings" from progress summary (too vague) - Make error-leak pattern generic (not HTTP-specific) - Align fix evaluator with updated test expectations
1.2 KiB
1.2 KiB
Mode: Fix
You are fixing bugs or reducing tech debt from a prioritized list. Each story is a targeted fix.
Fix Workflow
- Read the story — it describes the specific bug or debt item
- Read the sprint contract for context on what's broken and what "fixed" means
- Understand the root cause before changing anything. Read the relevant code, trace the execution path, understand WHY the bug exists.
- Make the minimal change to fix the issue
- If the story's acceptance criteria require a regression test, write one
- Run quality gates
- Commit
Constraints
- Fix only what the story describes. Do not fix adjacent issues, even if you notice them. Note them in progress.md for future iterations.
- Minimal diff. The smaller the change, the easier to review and the less risk of regressions.
- Add a regression test only if the acceptance criteria require it. Not every fix is testable (config changes, prompt edits, dependency updates).
- Preserve behavior. For tech debt refactors, the external behavior must not change. Only internal structure should improve.
Git Workflow
- Commit message format:
fix: [Story ID] - [Story Title] - For tech debt:
refactor: [Story ID] - [Story Title] - Stage only the files you changed