ln-403-task-rework
Fixes tasks in To Rework and returns them to To Review. Applies reviewer feedback only for the selected task.
When & Why to Use This Skill
The Task Rework Executor is a specialized Claude skill designed to automate the iterative cycle of task refinement within software development workflows. It streamlines the process of addressing reviewer feedback by intelligently loading task context, implementing requested changes—ranging from code fixes to documentation updates—and managing status transitions in Linear or file-based Kanban systems. By ensuring that feedback is systematically resolved and tasks are moved back to the review stage, it significantly reduces manual overhead and accelerates the development lifecycle.
Use Cases
- Automated Feedback Resolution: Automatically parse reviewer comments from Linear or Markdown files and apply the necessary code or configuration changes to satisfy requirements.
- Kanban Workflow Automation: Seamlessly manage task state transitions from 'To Rework' through 'In Progress' to 'To Review', ensuring project boards reflect real-time progress without manual updates.
- Technical Standard Alignment: Ensure that all reworks adhere to project-specific technical guides, ADRs, and 'Definition of Done' criteria through automated quality checks like linting and type-checking.
- Context-Aware Task Fixing: Load parent stories and related documentation to ensure that fixes applied during the rework phase remain consistent with the broader project scope and architecture.
| name | ln-403-task-rework |
|---|---|
| description | Fixes tasks in To Rework and returns them to To Review. Applies reviewer feedback only for the selected task. |
Task Rework Executor
Executes rework for a single task marked To Rework and hands it back for review.
Purpose & Scope
- Load full task, reviewer comments, and parent Story; understand requested changes.
- Apply fixes per feedback, keep KISS/YAGNI, and align with guides/Technical Approach.
- Update only this task: To Rework -> In Progress -> To Review; no other tasks touched.
Task Storage Mode
| Aspect | Linear Mode | File Mode |
|---|---|---|
| Load task | get_issue(task_id) |
Read("docs/tasks/epics/.../tasks/T{NNN}-*.md") |
| Load review notes | Linear comments | Review section in task file or kanban |
| Update status | update_issue(id, state) |
Edit the **Status:** line in file |
File Mode transitions: To Rework → In Progress → To Review
Workflow (concise)
- Receive task: Get task ID from orchestrator (ln-400); read task (Linear: get_issue; File: Read task file), review notes, parent Story.
- Plan fixes: Map each comment to an action; confirm no new scope added.
- Implement: Follow task plan/checkboxes; address config/hardcoded issues; update docs/tests noted in Affected Components and Existing Code Impact.
- Quality: Run typecheck/lint (or project equivalents); ensure fixes reflect guides/manuals/ADRs/research.
- Handoff: Set task to To Review (Linear: update_issue; File: Edit status line); move it in kanban; add summary comment referencing resolved feedback.
Critical Rules
- Single-task only; never bulk update.
- Do not mark Done; only To Review (ln-402 decides Done).
- Keep language (EN/RU) consistent with task.
- No new tests/tasks created here; only update existing tests if impacted.
Definition of Done
- Task and review feedback fully read; actions mapped.
- Fixes applied; docs/tests updated as required.
- Quality checks passed (typecheck/lint or project standards).
- Status set to To Review; kanban updated; summary comment added referencing fixed items.
Reference Files
- Kanban format:
docs/tasks/kanban_board.md
Version: 3.0.0 Last Updated: 2025-12-23