Skip to content
ln-221-story-creator logo

Story Creator

ln-221-story-creator

Creates Stories from IDEAL plan (CREATE) or appends user-requested Stories (ADD). Generates 8-section documents, validates INVEST, creates in Linear. Invoked by ln-220.

SKILL.md

Full skill instructions

Story Creator

Universal factory worker for creating Stories. Supports two modes:

  • CREATE MODE: Epic has no Stories → create from IDEAL plan (5-10 Stories)
  • ADD MODE: Epic has Stories → append new Story(s) from user request

Invoked by ln-220-story-coordinator (Phase 5a for CREATE, Phase 5c for ADD).

When Invoked

1. ln-220-story-coordinator CREATE MODE (Phase 5a):

  • Epic has NO existing Stories (Linear query count = 0)
  • IDEAL plan generated (Phase 3)
  • Standards Research completed by ln-001 (Phase 2)
  • Parameters: epicData, idealPlan, standardsResearch, teamId, autoApprove

2. ln-220-story-coordinator ADD MODE (Phase 5c):

  • Epic HAS existing Stories, user wants to ADD more (not replan)
  • Single Story or few Stories from user request
  • Parameters: epicData, appendMode: true, newStoryDescription, standardsResearch, teamId

Input Parameters

For CREATE MODE (from ln-220-story-coordinator Phase 5a):

{
  epicData: {id, title, description},
  idealPlan: [
    {
      number: "US004",
      title: "Register OAuth client",
      statement: {persona, capability, value},
      ac: [GWT scenarios],
      technicalNotes: {architecture, integrations, performance},
      estimatedHours: 12,
      testCounts: {e2e: 2, integration: 5, unit: 11}
    }
  ],
  standardsResearch: "OAuth 2.0 (RFC 6749)...",
  teamId: "team-id",
  autoApprove: true
}

For ADD MODE (from ln-220-story-coordinator Phase 5c with appendMode):

{
  epicData: {id, title, description},
  appendMode: true,                    // Signals ADD MODE - append to existing
  newStoryDescription: "User's request for new Story",
  standardsResearch: "Focused research for new Story only",
  teamId: "team-id",
  autoApprove: false                   // User confirmation recommended
}
  • appendMode: true signals ADD MODE - append to existing Stories
  • newStoryDescription: User's request for new Story(s) to add
  • NO idealPlan - creates only what user requested (single Story or few)

Workflow

[!NOTE] ADD MODE (appendMode: true): When adding Stories to existing Epic, workflow is simplified:

  • Phase 1: Generate only requested Story(s) from newStoryDescription
  • Skip full IDEAL plan comparison
  • Standards Research is focused only on new Story topics
  • Other phases proceed normally (INVEST, Preview, Create)

Phase 1: Generate Story Documents

Load story template (see "Template Loading" section) and use 8 sections.

For EACH Story in IDEAL plan:

SectionContent
1. Story StatementAs a [persona] / I want [capability] / So that [value]
2. ContextCurrent Situation (from Epic Scope Out) / Desired Outcome (from Epic Success Criteria)
3. ACCopy AC from idealPlan (3-5 GWT scenarios)
4. TasksPlaceholder: "Tasks created via ln-300-task-coordinator after ln-310-story-validator"
5. Test StrategyCopy test counts from idealPlan, Risk-Based Testing note
6. Technical NotesINSERT Standards Research in Library Research subsection
7. DoDStandard checklist from template
8. DependenciesEmpty OR "Depends On: US00X" if ordering implies dependency

Output: Array of N complete Story documents (5-10) with Standards Research inserted.

Phase 2: Validate INVEST

For EACH Story, check:

CriterionCheckPassFail
IndependentNo circular dependencies✅❌ STOP
NegotiableAC focus on WHAT not HOW✅❌ STOP
ValuableClear "So that" value✅❌ STOP
Estimable6-20 hours✅❌ STOP
Small3-5 AC, 10-28 tests✅❌ STOP
TestableMeasurable AC (GWT format)✅❌ STOP

Error if ANY Story fails → Report to orchestrator, stop execution.

Phase 3: Show Preview

STORY CREATION PREVIEW for Epic 7: OAuth Authentication

Will create 5 Stories:

1. US004: Register OAuth client
   Persona: Third-party developer | Capability: Register app, get credentials
   Value: Can integrate with API | AC: 4 | Estimate: 12h | Tests: 18

2. US005: Request access token
   Persona: API client | Capability: Exchange credentials for token
   Value: Authenticate to API | AC: 5 | Estimate: 18h | Tests: 24

... (3 more)

Total: 5 Stories, 62h, 90 tests

Standards Research: OAuth 2.0 (RFC 6749), RFC 7636 (PKCE), RFC 7009 (Revocation)
Story ordering: Dependency-aware (US004 → US005 → US006)
INVEST validation: ✓

Type "confirm" to create.

Phase 4: User Confirmation

If autoApprove=true: Skip confirmation → Phase 5 Otherwise: Wait for "confirm"

Phase 5: Create in Linear + Update Kanban

Create Linear Issues:

for each Story:
  create_issue({
    title: Story.number + ": " + Story.title,
    description: Story.generated_document,
    project: epicData.id,
    team: teamId,
    labels: ["user-story"],
    state: "Backlog"
  })

Update kanban_board.md:

Epic Grouping Algorithm:

  1. Find ### Backlog
  2. Search **Epic {epicNumber}: {epicTitle}**
    • Found: use existing Epic group
    • NOT found: create **Epic N: Epic Title**
  3. Add Stories under Epic (2-space indent, 📖 emoji)

Format:

**Epic 7: OAuth Authentication**

  📖 [ID: US004 Register OAuth client](url)
    _(tasks not created yet)_
  📖 [ID: US005 Request access token](url)
    _(tasks not created yet)_

Update Epic Story Counters table:

  • Last Story: US008
  • Next Story: US009

Return:

STORIES CREATED for Epic 7: OAuth Authentication

✓ Created 5 Stories in Linear:
  1. [ID: US004 Register OAuth client](url)
  2. [ID: US005 Request access token](url)
  3. [ID: US006 Validate access token](url)
  4. [ID: US007 Refresh expired token](url)
  5. [ID: US008 Revoke token](url)

✓ kanban_board.md updated (Backlog + Epic Story Counters)
✓ Standards Research included: OAuth 2.0, RFC 7636 PKCE, RFC 7009 Revocation

Total: 5 Stories, 62h, 90 tests

NEXT STEPS:
1. Run ln-310-story-validator to validate Stories (Backlog → Todo)
2. Use ln-300-task-coordinator to create tasks

Critical Rules

RuleDescription
Standards Research InsertionMUST insert in EVERY Story Technical Notes → Library Research
INVEST ValidationAll Stories must pass before creation (stop if ANY fails)
Template OwnershipThis skill owns story_template_universal.md in references/
Epic GroupingReuse Epic header if exists (search by Epic number), don't duplicate
Story NumberingSequential across ALL Epics (read Next Story from kanban_board.md)
No CodeDescriptions contain approach ONLY, not code

Definition of Done

✅ Phase 1:

  • All N Stories have 8 sections
  • Standards Research inserted in Technical Notes → Library Research

✅ Phase 2:

  • All Stories pass INVEST validation

✅ Phase 3:

  • Preview shown (summaries, totals, Standards Research, ordering)

✅ Phase 4:

  • autoApprove=true OR user confirmed

✅ Phase 5:

  • All N Stories created in Linear (project=Epic, labels=user-story, state=Backlog)
  • kanban_board.md updated (Backlog + Epic Story Counters)
  • Summary returned (URLs + next steps)

Template Loading

Template: story_template.md

Loading Logic:

  1. Check if docs/​templates/​story_template.md exists in target project
  2. IF NOT EXISTS: a. Create docs/​templates/ directory if missing b. Copy shared/​templates/​story_template.md → docs/​templates/​story_template.md c. Replace placeholders in the LOCAL copy:
    • {{TEAM_ID}} → from docs/​tasks/​kanban_board.md
    • {{DOCS_PATH}} → "docs" (standard)
  3. Use LOCAL copy (docs/​templates/​story_template.md) for all operations

Rationale: Templates are copied to target project on first use, ensuring:

  • Project independence (no dependency on skills repository)
  • Customization possible (project can modify local templates)
  • Placeholder replacement happens once at copy time

Reference Files

story_template.md

Location: shared/​templates/​story_template.md (centralized) Local Copy: docs/​templates/​story_template.md (in target project) Purpose: Universal Story template (8 sections) Template Version: 9.0.0

Integration

Called by: ln-220-story-coordinator

  • Phase 5a (CREATE MODE, count = 0) - full IDEAL plan
  • Phase 5c (ADD MODE, count ≥ 1, appendMode) - user-requested Story(s)

Returns:

  • Success: Story URLs + summary + next steps
  • Error: "Story USXXX violates INVEST: [details]"

Worker does NOT:

  • Query Linear for Epic (already in context)
  • Analyze Epic complexity (orchestrator Phase 3)
  • Research standards (orchestrator Phase 2 delegates to ln-001)
  • Build IDEAL plan (receives from orchestrator)

Version: 3.0.0 Last Updated: 2025-12-23

More skills from majiayu000

xiaohongshu logo
majiayu000/claude-arsenal

xiaohongshu

xiaohongshu

286 148
View
agent-task-conductor logo
majiayu000/claude-skill-registry

agent-task-conductor

Conduct multi-agent task orchestration and workflow coordination.

663 1
View
conductor-setup logo
majiayu000/claude-skill-registry

conductor-setup

Initialize project with Conductor artifacts (product definition,

663 1
View
animation-designer logo
majiayu000/claude-skill-registry

animation-designer

Expert in web animations, transitions, and motion design using Framer Motion and CSS

663 1
View
diagramming logo
majiayu000/claude-skill-registry

diagramming

Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...

663 1
View
h3-pg logo
majiayu000/claude-skill-registry-data

h3-pg

PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.

23 1
View
conductor-development logo
majiayu000/claude-skill-registry

conductor-development

Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...

663 1
View
conductor-status logo
majiayu000/claude-skill-registry

conductor-status

Display project status, active tracks, and next actions

663 1
View
dockerization logo
majiayu000/claude-skill-registry

dockerization

Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.

663 1
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View