planning-review-fixes

Code review findings are converted into actionable FormalTask issues using a 3-phase process that distills feedback into concise tasks. This approach applies antirez-style prioritization, focusing on code deletion and high value over effort, while enforcing strict limits on task count and complexity to maintain focus.

Antirez-style prioritization is a developer workflow method that emphasizes code deletion and value delivery over raw effort. This Skill applies this lens to code review findings, categorizing issues by severity from P0 to P3 to ensure critical bugs and unnecessary code are addressed first.

To prioritize bug fixing and refactoring tasks from a large code review, this Skill distills findings into a maximum of 5 high-impact tasks. It enforces hard limits on task creation and complexity, ensuring focus remains on deleting unnecessary code or fixing critical bugs rather than patching minor issues.

Yes, this task generation approach works with existing markdown review files by processing the documented findings directly. It reads the review file, identifies critical issues, and outputs actionable FormalTask issues complete with file references and acceptance criteria for immediate developer workflow integration.

Yes, there are hard limits on task creation to enforce focus and efficiency when processing code review feedback. The Skill distills a large set of findings, such as 15 individual issues, into a maximum of 5 concise, high-impact tasks with strict acceptance criteria.