What is the main goal of ln-403-task-rework?

To rework a single task marked To Rework, applying reviewer feedback only to that task, and hand it back to To Review without touching other tasks.

Are bulk updates allowed in this workflow?

No. It is strictly single-task focus; do not update multiple tasks or bulk changes, and do not commit.

What if a gap is found in documentation during rework?

Classify the root cause; if a doc/template gap is found, update the relevant file (guide, template, CLAUDE.md) to prevent recurrence and surface the fix in the Root Cause Analysis.

ln-403-task-rework

Scanned

npx machina-cli add skill levnikolaevich/claude-code-skills/ln-403-task-rework --openclaw

Files (1)

SKILL.md

3.3 KB

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.

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. 1b) Goal gate: MANDATORY READ: shared/references/goal_articulation_gate.md — State REAL GOAL of this rework (what was actually broken, not "apply feedback"). Combine with 5 Whys (shared/references/problem_solving.md) to ensure root cause is articulated alongside the rework goal. NOT THE GOAL: a superficial patch that addresses the symptom, not the cause.
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.
Root Cause Analysis: Ask "Why did the agent produce incorrect code?" Classify: missing context | wrong pattern | unclear AC | gap in docs/templates. If doc/template gap found → update the relevant file (guide, template, CLAUDE.md) to prevent recurrence.
Handoff: Set task to To Review (Linear: update_issue; File: Edit status line); move it in kanban; add summary comment referencing resolved feedback + root cause classification.

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.
Do NOT commit. Leave all changes uncommitted — ln-402 reviews and commits with task ID reference.

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).
Root cause classified (missing context | wrong pattern | unclear AC | doc gap); doc/template updated if gap found.
Status set to To Review; kanban updated; summary comment with fixed items + root cause.

Reference Files

[MANDATORY] Problem-solving approach: shared/references/problem_solving.md
Kanban format: docs/tasks/kanban_board.md

Version: 3.0.0 Last Updated: 2025-12-23

Source

git clone https://github.com/levnikolaevich/claude-code-skills/blob/master/ln-403-task-rework/SKILL.mdView on GitHub

Overview

ln-403-task-rework focuses on fixing a single task flagged To Rework, reloading the task, reviewer comments, and its parent Story. It applies feedback precisely to that task, keeping scope tight and avoiding bulk updates. The process moves the task through To Rework → In Progress → To Review with clear governance and mandatory goal articulation.

How This Skill Works

The engineer receives a task ID, loads the full task, reviewer notes, and parent Story, and then maps each comment to explicit actions. After implementing fixes and addressing docs/tests per the Affected Components, the task undergoes quality checks, root-cause classification, and is handed off by updating the status to To Review and refreshing the kanban. No cross-task updates are performed, and no commits are created during this flow.

When to Use It

A task labeled To Rework needs targeted fixes based on reviewer feedback.
You must update only the selected task and avoid touching other tasks.
Mandatory review of the goal articulation gate and 5 Whys for root cause context.
Documentation or test updates are required as per Affected Components and Existing Code Impact.
You are preparing the task for handoff back to To Review without marking it Done.

Quick Start

Step 1: Step 1: Receive task ID from the orchestrator (ln-400) and locate the task file.
Step 2: Step 2: Load the task, reviewer notes, and parent Story; read the mandatory goal articulation gate and 5 Whys.
Step 3: Step 3: Implement fixes for the selected task, run quality checks, classify root cause, set status to To Review, and update kanban.

Best Practices

Read the real goal via shared/references/goal_articulation_gate.md and connect it with 5 Whys before coding.
Map every comment to a concrete action; confirm no scope creep or new requirements.
Isolate changes to the single task; avoid touching other tasks, tests, or docs unnecessarily.
Run typecheck/lint or project equivalents and align fixes with guides, ADRs, and templates.
Document root cause classification (missing context, wrong pattern, unclear AC, or doc gap) and update guides/templates if needed.

Example Use Cases

Fix a task where missing context caused an incorrect implementation and return it with a precise root-cause note.
Address a wrong pattern identified in reviewer feedback and rework only that task without touching others.
Update a CLAUDE template in response to a documented gap discovered during rework.
Rework a task’s docs/tests impacted by the fix, keeping scope narrowly focused on this task.
Move the task to To Review after a successful rework, with a concise summary of fixed items and root cause.

Frequently Asked Questions

Add this skill to your agents