ln-222-story-replanner

Epic replanning compares your updated IDEAL plan against existing Linear stories and automatically classifies each story as KEEP, UPDATE, OBSOLETE, or CREATE. The Skill loads your epic data, applies the comparison, generates diffs of acceptance criteria and standards, and executes the necessary updates or creates new issues to realign your kanban with the new plan.

During replanning, UPDATE modifies existing stories when requirements shift but the story remains valid; CREATE generates new stories for requirements the IDEAL plan introduces that have no matching existing story. Both preserve history for In Progress and Done states and validate INVEST criteria before execution.

No. Epic replanning requires at least one existing story to compare against. The Skill uses existing story IDs as reference points to classify changes; without them, there's no baseline for the comparison and classification workflow.

The Skill detects ambiguous matches—cases where one story maps to multiple new requirements or multiple stories consolidate into one—and flags them for confirmation before execution. You review the proposed splits or merges, then approve or cancel to avoid unintended kanban disruption.

Confirmation is built into the workflow, but the autoApprove input lets you skip manual review for routine changes. The Skill obtains your approval, produces diffs of acceptance criteria and standards research, then executes updates or creations only after confirmation.