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.
Best use case
ln-220-story-coordinator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Creates, replans, or appends 5-10 Stories per Epic with standards research and multi-epic routing. Use when Epic needs Story decomposition.
Teams using ln-220-story-coordinator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ln-220-story-coordinator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ln-220-story-coordinator Compares
| Feature / Agent | ln-220-story-coordinator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Creates, replans, or appends 5-10 Stories per Epic with standards research and multi-epic routing. Use when Epic needs Story decomposition.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
> **Paths:** File paths (`shared/`, `references/`, `../ln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.
# 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.md`
- `shared/references/story_planning_runtime_contract.md`
- `shared/references/coordinator_summary_contract.md`
- `shared/references/tools_config_guide.md`
- `shared/references/storage_mode_detection.md`
- `shared/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
- delegate creation or replanning to standalone workers
## Inputs
| Parameter | Required | Description |
|-----------|----------|-------------|
| `epicId` | Yes | Epic to decompose |
| `autoApprove` | No | If false, runtime pauses on preview confirmation |
## Runtime
Runtime family: `story-planning-runtime`
Identifier:
- `epic-{epicId}`
Phases:
1. `PHASE_0_CONFIG`
2. `PHASE_1_CONTEXT_ASSEMBLY`
3. `PHASE_2_RESEARCH`
4. `PHASE_3_PLAN`
5. `PHASE_4_ROUTING`
6. `PHASE_5_MODE_DETECTION`
7. `PHASE_6_DELEGATE`
8. `PHASE_7_FINALIZE`
9. `PHASE_8_SELF_CHECK`
Terminal phases:
- `DONE`
- `PAUSED`
## 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_status`
- `research_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
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:
- `CREATE`
- `REPLAN`
- `ADD`
Checkpoint payload:
- `epic_group_modes`
### Phase 6: Delegate
Delegate by group:
- `ln-221-story-creator`
- `ln-222-story-replanner`
Workers remain standalone-capable. They may optionally write `story-plan` summary artifacts, but must always return the same structured summary even without artifact writing.
Record each result through runtime `record-epic`.
### Phase 7: Finalize
Finalize only after all expected worker summaries are recorded.
**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_result`
- `template_compliance_passed`
### Phase 8: Self-Check
Confirm:
- phase coverage
- planned vs produced Story counts
- no missing epic groups
Checkpoint payload:
- `pass`
- `final_result`
## Pending Decisions
Use runtime `PAUSED + pending_decision` for:
- missing context
- routing confirmation
- ambiguous `ADD` vs `REPLAN`
- 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:
- `story-plan`
## Worker Invocation (MANDATORY)
| Phase | Worker | Context |
|-------|--------|---------|
| 6 | `ln-221-story-creator` | CREATE or ADD path |
| 6 | `ln-222-story-replanner` | REPLAN path |
```text
Skill(skill: "ln-221-story-creator", args: "{epicId}")
Skill(skill: "ln-222-story-replanner", args: "{epicId}")
```
## TodoWrite format (mandatory)
```text
- 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 6: Delegate to worker(s) (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.
- 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
- [ ] 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/tools_config_guide.md`
- `shared/references/storage_mode_detection.md`
- `references/replan_algorithm.md`
---
**Version:** 5.0.0
**Last Updated:** 2026-02-03Related Skills
ln-830-code-modernization-coordinator
Modernizes codebase via OSS replacement and bundle optimization. Use when acting on audit findings to reduce custom code.
ln-820-dependency-optimization-coordinator
Upgrades dependencies across all detected package managers. Use when updating npm, NuGet, or pip packages project-wide.
ln-510-quality-coordinator
Coordinates code quality checks: metrics, cleanup, agent review, regression, log analysis. Use when Story needs quality_verdict with aggregated results.
ln-500-story-quality-gate
Story-level quality gate with 4-level verdict (PASS/CONCERNS/FAIL/WAIVED) and Quality Score. Use when Story is ready for quality assessment.
ln-400-story-executor
Executes Story tasks in priority order (To Review, To Rework, Todo). Use when Story has planned tasks ready for implementation.
ln-300-task-coordinator
Analyzes Story and builds optimal task plan (1-8 tasks), then routes to create or replan. Use when Story needs task breakdown or replanning.
ln-230-story-prioritizer
RICE-scores Stories with market research and generates prioritization table. Use when Stories need business priority ranking for sprint planning.
ln-222-story-replanner
Replans Stories by comparing IDEAL vs existing (KEEP/UPDATE/OBSOLETE/CREATE). Use when Epic requirements changed and Stories need realignment.
ln-221-story-creator
Creates Story documents with 9-section structure and INVEST validation in Linear. Use when Epic has an IDEAL plan ready for Story generation.
ln-210-epic-coordinator
Creates or replans 3-7 Epics from scope using Decompose-First pattern. Use when initiative needs Epic-level breakdown or Epic scope changed.
ln-110-project-docs-coordinator
Coordinates project documentation creation with single context gathering and project type detection. Use when generating project docs subset.
ln-914-community-responder
Responds to unanswered GitHub discussions and issues with codebase-informed replies. Use when clearing community question backlog.