원클릭으로
ln-221-story-creator
// Creates Story documents with 9-section structure and INVEST validation via the configured tracker provider. Use when Epic has an IDEAL plan ready for Story generation.
// Creates Story documents with 9-section structure and INVEST validation via the configured tracker provider. Use when Epic has an IDEAL plan ready for Story generation.
Checks local maintainability hotspots: complexity, long methods, god modules, signatures, algorithms, and constants. Also flags identifier drift across API/DTO/DB layers. Use when auditing code hotspots.
Decomposes scope into Epics, Stories, and RICE priorities. Use when user has project scope and wants full Agile breakdown.
Discovers growth opportunities using Traffic-First KILL funnel. Use when searching for next product direction with validated demand.
Creates or replans 3-7 Epics from scope using Decompose-First pattern. Use when initiative needs Epic-level breakdown or Epic scope changed.
Creates, replans, or appends 5-10 Stories per Epic with standards research and multi-epic routing. Use when Epic needs Story decomposition.
Replans Stories by comparing IDEAL vs existing (KEEP/UPDATE/OBSOLETE/CREATE). Use when Epic requirements changed and Stories need realignment.
| name | ln-221-story-creator |
| description | Creates Story documents with 9-section structure and INVEST validation via the configured tracker provider. Use when Epic has an IDEAL plan ready for Story generation. |
| license | MIT |
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
Type: L3 Worker Category: 2XX Planning
Standalone-first worker for Story creation. It may be called directly or as part of a coordinator flow, but its public contract is the same in both cases.
Load these before execution:
references/planning_worker_runtime_contract.mdreferences/coordinator_summary_contract.mdreferences/environment_state_contract.mdreferences/storage_mode_detection.mdreferences/creation_quality_checklist.mdreferences/template_loading_pattern.mdCore inputs:
epicDataidealPlan or appendMode + newStoryDescriptionstandardsResearchteamIdautoApproveOptional transport inputs:
runIdsummaryArtifactPathThe 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 family: planning-worker-runtime
Identifier:
epic-{epicId}Phases:
PHASE_0_CONFIGPHASE_1_RESOLVE_CONTEXTPHASE_2_LOAD_TEMPLATEPHASE_3_GENERATE_STORIESPHASE_4_VALIDATE_STORIESPHASE_5_CONFIRM_OR_AUTOAPPROVEPHASE_6_APPLY_CREATEPHASE_7_UPDATE_KANBANPHASE_8_WRITE_SUMMARYPHASE_9_SELF_CHECKManaged child-run mode:
--run-id and --summary-artifact-pathstory-plan-worker artifactStandalone mode:
run_idsummaryArtifactPath is providedAlways build a structured summary envelope:
schema_versionsummary_kind=story-plan-workerrun_ididentifierproducer_skill=ln-221produced_atpayloadPayload fields:
modeepic_idstories_plannedstories_createdstories_updatedstories_canceledstory_urlswarningskanban_updatedresearch_path_usedIf summaryArtifactPath is provided:
If summaryArtifactPath is not provided:
Managed artifact path pattern:
.hex-skills/runtime-artifacts/runs/{parent_run_id}/story-plan-worker/ln-221--{identifier}.jsonautoApprove=true.story-plan-worker summary.createStory: 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.summaryArtifactPath is providedVersion: 3.0.0 Last Updated: 2025-12-23