ln-302-task-replanner

安装量: 111
排名: #7687

安装

npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-302-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

| Load existing | get_issue(task_id) per task | Read("docs/tasks/epics/.../tasks/T{NNN}-*.md") per task

| Update task | update_issue(id, description) | Edit task file content

| Cancel task | update_issue(id, state: "Canceled") | Edit status to Canceled

| Create new | create_issue(parentId, state: "Backlog") | Write new T{NNN}-{slug}.md

File Mode replan:

  • Load existing task files via Glob

  • Compare with IDEAL plan

  • Edit/Write/Update files as needed

  • Update kanban_board.md to reflect changes

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: taskType, teamId, Story data (id/title/description with AC, Technical Notes, Context), existingTaskIds.

  • 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 docs/templates/{template}.md exists in target project

  • IF NOT EXISTS: a. Create docs/templates/ directory if missing b. Copy shared/templates/{template}.mddocs/templates/{template}.md c. Replace placeholders in the LOCAL copy:

{{TEAM_ID}} → from docs/tasks/kanban_board.md

  • {{DOCS_PATH}} → "docs" (standard)

  • Use LOCAL copy (docs/templates/{template}.md) for all operations

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)

| 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 state: "Backlog" when creating new tasks (CREATE operation). Linear defaults to team's default status (often "Postponed") if not specified.

  • 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.md, shared/templates/test_task_template.md

  • Local copies: docs/templates/*.md (in target project)

  • Replan algorithm: references/replan_algorithm.md

  • Kanban format: docs/tasks/kanban_board.md

Version: 3.0.0 Last Updated: 2025-12-23

返回排行榜