ln-200-scope-decomposer

Decompose initiative scope into Epics and Stories via ln-210 and ln-220.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-200-scope-decomposer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-200-scope-decomposer
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-200-scope-decomposer
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-200-scope-decomposer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as the top-level orchestrator for complete initiative decomposition, auto-discovering context and delegating work to specialized coordinators, saving you hours by avoiding manual handoffs between scope, Epic, and Story planning.

Core Features & Use Cases

  • End-to-end orchestration: Decomposes scope into Epics and Stories by delegating to ln-210-epic-coordinator and ln-220-story-coordinator.
  • Auto-Discovery: Extracts Team ID from docs/tasks/kanban_board.md for context-aware planning.
  • Sequential decomposition: Ensures Epics' stories are created in order, blocking subsequent Epics until current ones are completed.
  • Consolidated summary: Produces a final tally and recommended next steps.

Quick Start

Use the ln-200-scope-decomposer skill to start full initiative decomposition for a new project. It will auto-discover the Team ID and orchestrate Epics and Stories via the dedicated coordinators.

Frequently Asked Questions about ln-200-scope-decomposer

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

FAQPage Schema
How do I decompose a project scope into epics and stories automatically?

Scope decomposition breaks down initiatives into manageable epics and stories. This skill automates the full process end-to-end, auto-discovering team context and delegating to specialized coordinators to create structured epics and stories sequentially without manual handoffs.

Can I orchestrate scope decomposition across multiple epics while maintaining story order?

Yes. Sequential decomposition ensures each epic's stories are created in order before the next epic begins. The orchestrator blocks subsequent epics until current ones complete, maintaining workflow integrity across your full initiative.

What information does the skill auto-discover during scope decomposition?

The skill extracts Team ID from your kanban_board.md file for context-aware planning. Auto-discovery eliminates manual configuration and ensures decomposed epics and stories align with your existing team structure and project context.

How does this skill coordinate between epic and story planning?

It delegates epic creation to ln-210-epic-coordinator and story creation to ln-220-story-coordinator, orchestrating handoffs sequentially. This separation enforces consistent decomposition logic and produces consolidated metrics summarizing the complete initiative structure.

When should I use scope decomposition for a new initiative?

Use it when starting fresh initiatives requiring end-to-end planning. It's built for projects needing comprehensive scope-to-epic-to-story mapping, including infrastructure epic handling (Epic 0) and phase-by-phase execution with final summary metrics.

Does this approach support infrastructure epics in project decomposition?

Yes. It handles Infrastructure Epic (Epic 0 if applicable) as part of standard decomposition. The orchestrator recognizes and processes infrastructure concerns alongside functional epics in the sequential workflow.