ln-222-story-replanner

Name: ln-222-story-replanner
Availability: InStock
Author: dorrio

Replan Agile stories in Linear when epic requirements change.

Updated Dec 11, 2025

Search Tags:#task synchronization #agile development #story planning #epic management #linear app #requirement changes

Ready to run

npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-222-story-replanner-dorrio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-222-story-replanner
Source: https://github.com/dorrio/sorteo-app-generator/tree/main/.agent/skills/ln-222-story-replanner
Command: npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-222-story-replanner-dorrio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of keeping project stories aligned with evolving epic requirements, ensuring development efforts remain focused and efficient.

Core Features & Use Cases

Requirement Comparison: Compares ideal future state requirements against existing story definitions.
Operation Categorization: Identifies stories to KEEP, UPDATE, OBSOLETE, or CREATE based on requirement changes.
Automated Execution: Executes the identified operations directly within the Linear project management tool.
Use Case: When an epic's scope expands or shifts, this skill automatically updates or flags related stories, preventing outdated work and ensuring new tasks are created.

Quick Start

Use the ln-222-story-replanner skill to replan stories based on updated epic requirements.

Frequently Asked Questions about ln-222-story-replanner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I replan stories in Linear when epic requirements change?▼

To replan stories when epic requirements change, compare ideal future state requirements against existing story definitions, categorize necessary operations, and execute changes directly in the Linear project management tool for continuous alignment.

What does story categorization mean for agile epic management?▼

Story categorization for agile epic management identifies existing stories to KEEP, UPDATE, OBSOLETE, or CREATE based on requirement changes, ensuring development efforts remain focused and efficient when an epic's scope expands or shifts.

Can I automate task synchronization between updated epics and existing stories?▼

Automating task synchronization between updated epics and existing stories is possible by comparing requirement changes and executing identified operations directly within the Linear tool, which automatically updates or flags related stories.

Does the story replanner work with existing story definitions in the Linear app?▼

The story replanner works with existing story definitions in the Linear app by comparing them against ideal future state requirements and executing the identified operations to prevent outdated work.

What is the best way to handle requirement changes without creating outdated work?▼

The best way to handle requirement changes without creating outdated work is to compare ideal versus existing story definitions, flag related stories as obsolete, and create new tasks directly in Linear.

When should I not use automated story replanning for epic management?▼

You should not use automated story replanning for epic management when an epic's scope is stable and requires no shifts, as the process focuses on categorizing and executing operations for changed requirement definitions.