ln-200-scope-decomposer

Decompose initiatives into Epics, Stories, and RICE prioritization.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-200-scope-decomposer-cbbkrd-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-200-scope-decomposer
Source: https://github.com/cbbkrd-tech/jl-finishes/tree/main/.claude/skills/ln-200-scope-decomposer
Command: npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-200-scope-decomposer-cbbkrd-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the entire process of breaking down a high-level initiative into actionable Epics and User Stories, streamlining project planning and reducing manual effort.

Core Features & Use Cases

  • Full Decomposition Pipeline: Orchestrates discovery, Epic creation, Story creation, and optional RICE prioritization.
  • Automated Discovery: Auto-discovers Team ID from kanban_board.md.
  • Sequential Processing: Ensures Stories for one Epic are completed before moving to the next, managing interactive steps effectively.
  • Use Case: When starting a new large project, use this Skill to automatically generate all necessary Epics and Stories, ensuring a structured and efficient kickoff.

Quick Start

Use the ln-200-scope-decomposer skill to decompose the initiative "New E-commerce Platform".

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 initiative into epics and user stories?

To decompose a project initiative into epics and user stories, you can orchestrate a full pipeline that breaks down high-level scope into structured epics, sequential user stories, and applies RICE prioritization to streamline project planning.

What is RICE prioritization in project planning and when should I apply it?

RICE prioritization in project planning is an optional step applied after decomposing an initiative into epics and stories, allowing you to score and rank user stories based on reach, impact, confidence, and effort to sequence work effectively.

Does the initiative decomposition process require a specific team setup?

The initiative decomposition process requires auto-discovering a Team ID from a kanban_board.md file, ensuring the generated epics and stories are attached to the correct project tracking environment before decomposition begins.

Why is epic 0 reserved for infrastructure during project scope decomposition?

Epic 0 is reserved for infrastructure during project scope decomposition to ensure foundational technical setup and environment configurations are structured separately from feature-centric epics and user stories before sequential story generation begins.

Can I generate all user stories for multiple epics simultaneously?

You cannot generate all user stories for multiple epics simultaneously because story decomposition runs sequentially, completing stories for one epic and handling interactive user confirmation steps before moving to the next epic.