Claude-skill-registry ln-302-task-replanner
Updates ALL task types (implementation/refactoring/test). Compares IDEAL plan vs existing tasks, categorizes KEEP/UPDATE/OBSOLETE/CREATE, applies changes in Linear and kanban.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/ln-302-task-replanner" ~/.claude/skills/majiayu000-claude-skill-registry-ln-302-task-replanner-27ae6d && rm -rf "$T"
manifest:
skills/data/ln-302-task-replanner/SKILL.mdsource content
Universal Task Replanner
Worker that re-syncs existing tasks to the latest requirements for any task type.
Purpose & Scope
- Load full existing task descriptions from Linear
- Compare them with orchestrator-provided IDEAL plan (implementation/refactoring/test)
- Decide operations (KEEP/UPDATE/OBSOLETE/CREATE) and execute
- Drop NFR items; only functional scope remains
- Update Linear issues and kanban_board.md accordingly
Task Storage Mode
| Aspect | Linear Mode | File Mode |
|---|---|---|
| Load existing | per task | per task |
| Update task | | task file content |
| Cancel task | | status to Canceled |
| Create new | | new |
File Mode replan:
- Load existing task files via Glob
- Compare with IDEAL plan
- Edit/Write/Update files as needed
- Update
to reflect changeskanban_board.md
Invocation (who/when)
- ln-300-task-coordinator: REPLAN mode when implementation tasks already exist.
- Orchestrators (other groups): Replan refactoring or test tasks as needed.
- Not user-invoked directly.
Inputs
- Common:
, teamId, Story data (id/title/description with AC, Technical Notes, Context), existingTaskIds.taskType - Implementation: idealPlan (1-6 tasks), guideLinks.
- Refactoring: codeQualityIssues, refactoringPlan, affectedComponents.
- Test: manualTestResults, testPlan (E2E 2-5, Integration 0-8, Unit 0-15, Priority ≤15), infra/doc/cleanup items.
Template Loading
Templates:
task_template_implementation.md, refactoring_task_template.md, test_task_template.md
Template Selection by taskType:
→implementationtask_template_implementation.md
→refactoringrefactoring_task_template.md
→testtest_task_template.md
Loading Logic (for each template):
- Check if
exists in target projectdocs/templates/{template}.md - IF NOT EXISTS:
a. Create
directory if missing b. Copydocs/templates/
→shared/templates/{template}.md
c. Replace placeholders in the LOCAL copy:docs/templates/{template}.md
→ from{{TEAM_ID}}docs/tasks/kanban_board.md
→ "docs" (standard){{DOCS_PATH}}
- Use LOCAL copy (
) for all operationsdocs/templates/{template}.md
Rationale: Templates are copied to target project on first use, ensuring:
- Project independence (no dependency on skills repository)
- Customization possible (project can modify local templates)
- Placeholder replacement happens once at copy time
Workflow (concise)
- Load templates per taskType (see Template Loading) and fetch full existing task descriptions.
- Normalize both sides (IDEAL vs existing sections) and run replan algorithm to classify KEEP/UPDATE/OBSOLETE/CREATE.
- Present summary (counts, titles, key diffs). Confirmation required if running interactively.
- Execute operations in Linear: update descriptions, cancel obsolete, create missing with state="Backlog", preserve parentId for updates.
- Update kanban_board.md: remove canceled, add new tasks under Story in Backlog.
- Return operations summary with URLs and warnings.
Type Rules (must hold after update)
| taskType | Hard rule | What to enforce |
|---|---|---|
| implementation | No new test creation | Updated/created tasks must not introduce test creation text |
| refactoring | Regression strategy required | Issues + severity, 3-phase plan, regression strategy, preserve functionality |
| test | Risk-based limits | Priority ≤15 scenarios; E2E 2-5, Integration 0-8, Unit 0-15, Total 10-28; no framework/library/DB tests |
Critical Notes
- MANDATORY: Always pass
when creating new tasks (CREATE operation). Linear defaults to team's default status (often "Postponed") if not specified.state: "Backlog" - Foundation-First ordering from IDEAL plan is preserved; do not reorder.
- Language preservation: keep existing task language (EN/RU).
- No code snippets; keep to approach/steps/AC/components.
- If Story reality differs (component exists, column exists), propose Story correction to orchestrator.
Definition of Done
- Existing tasks loaded and parsed with correct template.
- IDEAL plan vs existing compared; operations classified.
- Type validation passed for all updated/created tasks.
- Operations executed in Linear (updates, cancels, creations) with parentId intact.
- kanban_board.md updated (Backlog) with correct Epic/Story/indentation.
- Summary returned (KEEP/UPDATE/OBSOLETE/CREATE counts, URLs, warnings).
Reference Files
- Templates (centralized):
,shared/templates/task_template_implementation.md
,shared/templates/refactoring_task_template.mdshared/templates/test_task_template.md - Local copies:
(in target project)docs/templates/*.md - Replan algorithm:
references/replan_algorithm.md - Kanban format:
docs/tasks/kanban_board.md
Version: 3.0.0 Last Updated: 2025-12-23