ln-222-story-replanner
Replans Stories by comparing IDEAL vs existing (KEEP/UPDATE/OBSOLETE/CREATE). Use when Epic requirements changed and Stories need realignment.
How do I install this agent skill?
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-222-story-replannerIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill facilitates story replanning by comparing an ideal plan against existing project data. It utilizes a custom runtime managed by local Node.js scripts for state persistence and phase transitions. It presents a data ingestion surface via the loading of existing stories from external providers, which introduces a potential for indirect prompt injection.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- Runlayerwarn
1/2 files flagged
- ZeroLeakspass
1 finding · Score: 86/100
What does this agent skill do?
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
Story Replanner
Type: L3 Worker Category: 2XX Planning
Standalone-first worker for Story replanning. It compares ideal Story intent with existing Stories and applies the resulting operations.
MANDATORY READ
Load these before execution:
references/planning_worker_runtime_contract.mdreferences/coordinator_summary_contract.mdreferences/environment_state_contract.mdreferences/storage_mode_detection.mdreferences/template_loading_pattern.mdreferences/replan_algorithm_stories.md
Inputs
Core inputs:
epicDataidealPlanexistingStoryIdsstandardsResearchteamIdautoApprove
Optional transport inputs:
runIdsummaryArtifactPath
The worker must remain fully usable without caller-provided runId and without summaryArtifactPath. In standalone mode it generates its own run_id before emitting the summary envelope.
Runtime
Runtime family: planning-worker-runtime
Identifier:
epic-{epicId}
Phases:
PHASE_0_CONFIGPHASE_1_RESOLVE_CONTEXTPHASE_2_LOAD_EXISTING_STORIESPHASE_3_CLASSIFY_REPLANPHASE_4_CONFIRM_OR_AUTOAPPROVEPHASE_5_APPLY_REPLANPHASE_6_UPDATE_KANBANPHASE_7_WRITE_SUMMARYPHASE_8_SELF_CHECK
Managed child-run mode:
- caller starts the runtime with
--run-idand--summary-artifact-path - runtime writes the final summary artifact directly to the caller-provided path
- parent coordinator records the resulting
story-plan-workerartifact
Standalone mode:
- runtime generates its own
run_id - runtime still returns the same structured summary envelope
- artifact writing is optional unless
summaryArtifactPathis provided
Output Contract
Always build a structured summary envelope:
schema_versionsummary_kind=story-plan-workerrun_ididentifierproducer_skill=ln-222produced_atpayload
Payload fields:
modeepic_idstories_plannedstories_createdstories_updatedstories_canceledstory_urlswarningskanban_updatedresearch_path_used
If summaryArtifactPath is provided:
- write the same JSON summary to that path
If summaryArtifactPath is not provided:
- return the same summary in structured output only
Managed artifact path pattern:
.hex-skills/runtime-artifacts/runs/{parent_run_id}/story-plan-worker/ln-222--{identifier}.json
Workflow
- Resolve Epic context if not already provided.
- Load existing Stories one by one.
- Normalize ideal vs existing Story structures.
- Run the replan algorithm to classify
KEEP,UPDATE,OBSOLETE,CREATE. - Show operations summary unless
autoApprove=true. - Execute provider-specific updates.
- Update kanban.
- Return structured summary.
Critical Rules
- Prefer conservative updates when matching is ambiguous.
- Preserve finished work when replanning conflicts with completed Stories.
- Keep the worker standalone-capable.
- Never require coordinator runtime state to operate.
- Return machine-readable results, not prose-only outcomes.
- STOP before tracker createStory/updateBody: verify all 9 sections present in body: Story, Context, Acceptance Criteria, Implementation Tasks, Test Strategy, Technical Notes, Definition of Done, Dependencies, Assumptions. PreToolUse hook will BLOCK creation without them.
Definition of Done
- Existing Stories loaded and normalized
- Replan algorithm applied
- Required updates, cancellations, and creations executed
- kanban updated
- Structured summary returned
- Summary artifact written when
summaryArtifactPathis provided
Version: 3.0.0 Last Updated: 2025-12-23
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/levnikolaevich/claude-code-skills/ln-222-story-replanner">View ln-222-story-replanner on skillZs</a>