ln-413-task-rework

Apply reviewer feedback to a single Linear task and return it to To Review.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-413-task-rework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-413-task-rework
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-413-task-rework
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-413-task-rework

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Fixes a single task marked To Rework, applies reviewer feedback, and returns it to To Review without touching other tasks.

Core Features & Use Cases

  • Apply reviewer feedback to a single To Rework task only
  • Preserve task order and existing workflow context
  • Move task: To Rework -> In Progress -> To Review; no bulk updates

Quick Start

Command the agent to rework task with ID US123: ln-413-task-rework --task-id US123 --feedback "Address edge-case handling in validation"

Frequently Asked Questions about ln-413-task-rework

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply reviewer feedback to a single task in Linear?

Task rework applies reviewer feedback to a single task marked To Rework, maps each comment to a concrete action, and returns it to To Review status in Linear without modifying other tasks or expanding scope.

Can I rework a task without affecting other items in my workflow?

Yes. Task rework enforces single-task scope, moving only the specified task from To Rework through In Progress back to To Review while preserving task order and existing workflow context on the Kanban board.

What happens to task documentation and tests when reworking?

Task rework updates documentation and tests only when required by the feedback. It runs typecheck and lint validation on changes, preserves Foundation-First ordering, and maintains project conventions without unnecessary modifications.

How do I ensure no new scope gets added during task rework?

Task rework follows a plan-driven implementation that maps reviewer comments to concrete actions within the original task scope, explicitly blocking bulk updates or scope expansion while processing feedback.

What's the fastest way to move a task from To Rework back to review?

Specify the task ID and reviewer feedback to task rework, which applies comments, validates changes, updates Linear status and the Kanban board, and returns the task to To Review in a single operation.