skills.rest
mcauduro0
mcauduro0COMMUNITY
Explore all skills by this author →
GitHub

ln-220-story-coordinator

Coordinates decomposition of Epics into 5-10 User Stories with ViNTA criteria and standards research integration.

1|Updated Feb 19, 2026
Search Tags:#workflow automation#requirements gathering#agile development#epic decomposition#linear integration#story management
One-click install
npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-220-story-coordinator-mcauduro0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ln-220-story-coordinator
Source: https://github.com/mcauduro0/Macro_Trading/tree/main/.claude/skills/ln-220-story-coordinator
Command: npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-220-story-coordinator-mcauduro0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of breaking down large Epics into manageable, actionable User Stories, ensuring alignment with development standards and best practices.

Core Features & Use Cases

  • Automated Decomposition: Transforms Epics into 5-10 well-defined User Stories.
  • Standards Integration: Incorporates industry standards research via delegation to ln-001-standards-researcher.
  • Decompose-First Pattern: Ensures a robust plan is built before considering existing Stories, preventing outdated structures.
  • Mode Detection: Intelligently handles CREATE (new Epics) and REPLAN (updated Epics) scenarios.
  • Use Case: When a new Epic like "Implement User Authentication" is defined, this Skill will automatically generate Stories such as "User Registration", "Login Functionality", "Password Reset", and "Token Management", complete with acceptance criteria and technical notes.

Quick Start

Use the ln-220-story-coordinator skill to create stories for Epic 7: OAuth Authentication.

Frequently Asked Questions about ln-220-story-coordinator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down an Epic into User Stories for agile development?▼

Decomposing an Epic into User Stories involves transforming large requirements into 5-10 manageable stories using vertical slicing. This automated decomposition ensures alignment with development standards and incorporates industry best practices while adhering to INVEST criteria.

What is the Decompose-First pattern for epic decomposition?▼

The Decompose-First pattern builds a robust story structure before considering existing Stories, preventing outdated structures from influencing plans. It handles initial Epic decomposition and replanning for evolving requirements while maintaining vertical slicing.

How do I ensure my User Stories meet INVEST criteria during requirements gathering?▼

To ensure User Stories meet INVEST criteria during requirements gathering, the decomposition process structures each story to satisfy these criteria automatically. Vertical slicing is applied to generate stories complete with acceptance criteria and technical notes.

Can I update existing User Stories when an Epic changes during replanning?▼

Yes, you can update existing User Stories when an Epic changes through intelligent mode detection. The system handles REPLAN scenarios for updated Epics by adjusting previously generated stories based on evolving requirements while preserving vertical slicing.

Does this story management approach integrate with standards research?▼

Yes, this story management approach integrates with standards research by delegating to specialized research components. It incorporates industry standards research directly into the generated User Stories, ensuring technical compliance and best practice alignment.

What are the limitations of automating workflow automation for story creation?▼

A limitation of automating workflow for story creation is that it decomposes Epics into a restricted set of 5-10 User Stories. Epics requiring significantly more stories or highly customized non-vertical slicing may require manual intervention beyond the automated decomposition.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

intake-skill

Transform natural language project descriptions into structured engagement briefs.

Community
Advanced
Exia-thdExia-thd

project-manager

Plan and execute agile sprints, tasks, and risks for software teams.

Community
Advanced
paraskakisparaskakis
41

design-api

Transform requirements and domain models into a linted OpenAPI document.

Community
Advanced
alex-tgkalex-tgk

agile-product-owner

Generate INVEST-compliant user stories with acceptance criteria from epics.

Community
Intermediate