How does it handle token limits with large Epics?

It uses a progressive loading strategy, fetching full story descriptions one by one rather than all at once, ensuring efficient use of Claude's context window.

Does this skill delete stories from Linear?

No, it marks obsolete stories as 'Canceled' rather than deleting them to ensure history is preserved while keeping the backlog clean.

What happens if a story is already 'In Progress'?

The skill detects the 'In Progress' status and issues a warning, requiring explicit user confirmation before making any changes to avoid disrupting active work.

Can I customize the story template used during replanning?

Yes, the skill looks for a local story_template.md in your project's docs folder, allowing you to maintain custom sections and formatting.

Story Replanner for Linear

Name: Story Replanner for Linear
Author: levnikolaevich

bylevnikolaevich

•

Collaboration Tools

Synchronizes and updates Linear user stories automatically when Epic requirements or technical standards change.

About

The ln-222-story-replanner is a production-ready worker skill for Claude Code that manages the evolution of software delivery. It intelligently compares a project's ideal state against existing Linear stories to categorize required actions as KEEP, UPDATE, OBSOLETE, or CREATE. By handling complex logic—such as status constraints for 'In Progress' work, story splits, and merges—it ensures your project backlog remains a source of truth. It streamlines the replanning phase by generating diffs for acceptance criteria and technical notes, updating kanban documentation, and enforcing INVEST standards without manual intervention.

Key Features

Standardized Change Logs: Adds meaningful comments to Linear issues explaining why stories were updated or canceled.
38 GitHub stars
Automated Kanban Sync: Synchronizes local kanban_board.md files with the latest story statuses and requirements.
Token-Efficient Loading: Implements progressive, sequential loading for story metadata to handle large Epics without context overflow.
Intelligent Requirement Matching: Uses fuzzy matching to compare ideal plans against existing stories based on persona and capability.
Status-Aware Updates: Automatically handles state transitions in Linear while protecting 'Done' stories from accidental changes.

Use Cases

Updating a project backlog after an Epic's Acceptance Criteria or features have been modified.
Pruning obsolete stories and cleaning up Linear boards after a project pivot or scope reduction.
Injecting new technical standards or RFC requirements into existing stories mid-sprint.

About

Key Features

Standardized Change Logs: Adds meaningful comments to Linear issues explaining why stories were updated or canceled.
38 GitHub stars
Automated Kanban Sync: Synchronizes local kanban_board.md files with the latest story statuses and requirements.
Token-Efficient Loading: Implements progressive, sequential loading for story metadata to handle large Epics without context overflow.
Intelligent Requirement Matching: Uses fuzzy matching to compare ideal plans against existing stories based on persona and capability.
Status-Aware Updates: Automatically handles state transitions in Linear while protecting 'Done' stories from accidental changes.

Use Cases

Updating a project backlog after an Epic's Acceptance Criteria or features have been modified.
Pruning obsolete stories and cleaning up Linear boards after a project pivot or scope reduction.
Injecting new technical standards or RFC requirements into existing stories mid-sprint.