Claude-code-skills ln-220-story-coordinator
Creates, replans, or appends 5-10 Stories per Epic with standards research and multi-epic routing. Use when Epic needs Story decomposition.
git clone https://github.com/levnikolaevich/claude-code-skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/levnikolaevich/claude-code-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills-catalog/ln-220-story-coordinator" ~/.claude/skills/levnikolaevich-claude-code-skills-ln-220-story-coordinator && rm -rf "$T"
skills-catalog/ln-220-story-coordinator/SKILL.mdPaths: File paths (
,shared/,references/) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.../ln-*
Story Coordinator
Type: L2 Domain Coordinator Category: 2XX Planning
Runtime-backed Story planning coordinator. The runtime owns flow control, pause/resume, and worker result tracking.
MANDATORY READ
Load these before execution:
shared/references/coordinator_runtime_contract.mdshared/references/story_planning_runtime_contract.mdshared/references/coordinator_summary_contract.mdshared/references/environment_state_contract.mdshared/references/storage_mode_detection.mdshared/references/problem_solving.md
Purpose
- assemble Epic planning context
- perform focused standards research when it changes Technical Notes
- build the ideal Story plan before checking existing Stories
- detect routing and mode per epic group
- batch child manifest/artifact preparation before delegation
- delegate creation or replanning to standalone workers
Inputs
| Parameter | Required | Description |
|---|---|---|
| Yes | Epic to decompose |
| No | If false, runtime pauses on preview confirmation |
Runtime
Runtime family:
story-planning-runtime
Identifier:
epic-{epicId}
Phases:
PHASE_0_CONFIGPHASE_1_CONTEXT_ASSEMBLYPHASE_2_RESEARCHPHASE_3_PLANPHASE_4_ROUTINGPHASE_5_MODE_DETECTIONPHASE_6_DELEGATEPHASE_7_FINALIZEPHASE_8_SELF_CHECK
Terminal phases:
DONEPAUSED
Summary flow:
- consume child
artifacts fromstory-plan-worker
/ln-221ln-222 - write coordinator
artifact duringstory-planPHASE_7_FINALIZE
Phase Map
Phase 1: Context Assembly
Resolve Epic and assemble only the planning inputs that change Story decomposition:
- Epic scope
- success criteria
- known personas and constraints
- project task provider
Checkpoint payload:
context_ready
Phase 2: Research
Do focused research only when it changes Story Technical Notes or implementation constraints.
Do not let research expand Story scope.
Checkpoint payload:
research_statusresearch_file
Phase 3: Plan
Build the ideal Story plan before looking at existing Stories.
Rules:
- vertical slices only
- 5-10 Stories when Epic warrants it
- concise Story statements and observable ACs
- no orchestration prose inside the plan
- delegate ACs must specify what equips the actor (context, instructions, tools, configuration), not just what the actor does
Checkpoint payload:
ideal_plan_summary
Phase 4: Routing
Route planned Stories to epic groups.
Fast path:
- all Stories stay in the resolved Epic
Pause only when routing is ambiguous or requires confirmation.
Checkpoint payload:
routing_summary
Phase 5: Mode Detection
Determine mode per epic group:
CREATEREPLANADD
Checkpoint payload:
epic_group_modes
Phase 6: Delegate
Phase 6 has two internal steps.
Phase 6a: Prepare delegation
- finalize routing groups
- materialize worker manifests
- precompute
andrun_id
for each childsummary_artifact_path - checkpoint the expected worker set before execution
Phase 6b: Execute delegation
Delegate by group:
ln-221-story-creatorln-222-story-replanner
Workers remain standalone-capable. In managed mode the coordinator starts them through
planning-worker-runtime, passes runId + summaryArtifactPath, stores the launch metadata in child_run, then records the resulting worker artifact through record-epic.
Worker summary kind:
story-plan-worker
Phase 7: Finalize
Finalize only after all expected worker summaries are recorded.
Coordinator output:
- build one
summary for the parent runtimestory-plan - write it through
node shared/scripts/story-planning-runtime/cli.mjs record-plan-summary - persist the artifact before advancing to
PHASE_8_SELF_CHECK
Template compliance gate: Fetch each created Story via
get_issue. Run validateTemplateCompliance(description, 'story') from planning-runtime/lib/template-compliance.mjs. All stories must pass (9 sections in order). Record template_compliance_passed in state. Guard blocks SELF_CHECK without it.
Checkpoint payload:
final_resulttemplate_compliance_passed
Phase 8: Self-Check
Confirm:
- phase coverage
- planned vs produced Story counts
- no missing epic groups
Checkpoint payload:
passfinal_result
Pending Decisions
Use runtime
PAUSED + pending_decision for:
- missing context
- routing confirmation
- ambiguous
vsADDREPLAN - preview confirmation when
autoApprove=false
Do not hold these decisions only in chat.
Worker Contract
Workers:
- do not know the coordinator
- do not read runtime state
- remain standalone
- may receive
summaryArtifactPath - return shared summary envelope either way
Expected summary kind:
- child workers:
story-plan-worker - coordinator output:
story-plan
Worker Invocation (MANDATORY)
| Phase | Worker | Context |
|---|---|---|
| 6 | | CREATE or ADD path |
| 6 | | REPLAN path |
node shared/scripts/planning-worker-runtime/cli.mjs start --skill {worker} --identifier {identifier} --manifest-file {workerManifestPath} --run-id {childRunId} --summary-artifact-path {childSummaryArtifactPath} child_run = { skill, run_id, identifier, summary_artifact_path } childSummaryArtifactPath = .hex-skills/runtime-artifacts/runs/{parent_run_id}/story-plan-worker/{worker}--{identifier}.json Skill(skill: "{worker}", args: "{identifier} --ideal-plan {idealPlanJSON} --epic {epicId} --run-id {childRunId} --summary-artifact-path {childSummaryArtifactPath}") Read {childSummaryArtifactPath} node shared/scripts/story-planning-runtime/cli.mjs record-epic --epic {epicId} --payload-file {childSummaryArtifactPath} node shared/scripts/story-planning-runtime/cli.mjs record-plan-summary --epic {epicId} --payload-file {coordinatorSummaryPath}
TodoWrite format (mandatory)
- Phase 1: Assemble context (pending) - Phase 2: Research only what changes Technical Notes (pending) - Phase 3: Build ideal Story plan (pending) - Phase 4: Route Stories by Epic (pending) - Phase 5: Detect mode per group (pending) - Phase 6a: Prepare delegation batch (pending) - Phase 6b: Execute worker(s) sequentially (pending) - Phase 7: Finalize result (pending) - Phase 8: Self-check (pending)
Critical Rules
- Build the ideal plan before checking existing Stories.
- Use research only to improve Technical Notes and implementation realism.
- Do not keep routing or preview approvals in chat-only state.
- Batch only read-only preparation. Do not parallelize Story mutations across routed groups unless runtime semantics explicitly allow it.
- Do not create or update Stories directly when a worker should do it.
- Consume worker summaries, not free-text worker prose.
Definition of Done
- Runtime started with Epic-scoped identifier
- Context assembly checkpointed
- Research checkpointed or explicitly minimal
- Ideal plan checkpointed
- Routing checkpointed
- Mode detection checkpointed
- All expected worker summaries recorded
- Coordinator
summary recordedstory-plan - Final result checkpointed
- Template compliance passed for all created Stories
- Self-check passed
Meta-Analysis
MANDATORY READ: Load
shared/references/meta_analysis_protocol.md
Skill type:
planning-coordinator. Run after all phases complete. Output to chat using the protocol format.
Reference Files
shared/references/environment_state_contract.mdshared/references/storage_mode_detection.mdreferences/replan_algorithm.md
Version: 5.0.0 Last Updated: 2026-02-03