Workflow
1. Parse Reviewer Notes
- Split numbered lists and bullets
- Extract distinct change requests
- Clarify ambiguous items BEFORE starting
2. Create Todo List
Use TodoWrite for each feedback item:
- One todo per change
- Mark first as
in_progressbefore starting - Only ONE
in_progressat any time
3. Implement Systematically
For each todo:
Locate:
- Grep for functions/classes
- Glob for files by pattern
- Read current implementation
Change:
- Use Edit tool
- Follow CLAUDE.md conventions
- Preserve existing functionality
Verify:
- Check syntax
- Run relevant tests
- Confirm reviewer's intent addressed
Update:
- Mark todo
completedIMMEDIATELY - Move to next (one
in_progressonly)
4. Validate
After all changes:
ruff check --fix && ruff format
pytest {affected_tests}
5. Commit and Push (if requested)
git add -A
git commit -m "fix: Address review feedback for task-{id}
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>"
git push
6. Task Completion (if --auto-complete)
# Without review bypass
ft task complete {task_id}
# With review bypass
ft task complete {task_id} --skip-review
| Exit Code | Meaning | Action |
|---|---|---|
| 0 | Completed | Success |
| 1 | Blocked by reviews | Run required reviews |
| 2 | PR created, review started | Wait for review |
Edge Cases
| Case | Action |
|---|---|
| Conflicting feedback | Ask user for guidance |
| Breaking changes | Notify before implementing |
| Tests fail after changes | Fix before marking complete |
| Code doesn't exist | Ask for clarification |
Find the Stupid
| Stupid | Why |
|---|---|
| Batching completions | Lose track of progress |
| Multiple in_progress | Confusion about what's active |
| Skipping validation | Breaks build |
| No TodoWrite | Progress invisible |
Converted and distributed by TomeVault — claim your Tome and manage your conversions.