ln-200-scope-decomposer

Coordinate initiative decomposition into Epics, Stories, and RICE prioritization.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-200-scope-decomposer-0xtaoist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-200-scope-decomposer
Source: https://github.com/0xtaoist/taogate/tree/main/ln-200-scope-decomposer
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-200-scope-decomposer-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates a complete initiative decomposition workflow from scope to Epics and Stories by delegating work to specialized coordinators (ln-210-epic-coordinator, ln-220-story-coordinator, ln-230-story-prioritizer) and compiling a final summary.

Core Features & Use Cases

  • Auto-discovers Team ID from the project configuration and Kanban board
  • Phase-based orchestration: Phase 1 Discovery, Phase 2 Epic Decomposition, Phase 3 Story Decomposition, Phase 4 optional RICE Prioritization, Phase 5 Summary
  • Sequential processing to ensure Epics' Stories are created and reviewed before proceeding
  • Outputs Epics and Stories to the project board and summary reporting for next steps
  • Supports integration with downstream validators and executors (ln-310, ln-400) as part of the end-to-end flow

Quick Start

Invoke the orchestrator with the initiative name to start full decomposition.

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 automate scope decomposition for project initiatives into epics and stories?

Automating scope decomposition coordinates the end-to-end breakdown of initiatives into Epics and Stories. It sequentially processes phases from initial discovery to story creation, auto-discovering Team IDs to populate your kanban board without manual intervention.

What is RICE prioritization and how does it apply to story creation?

RICE prioritization scores stories based on Reach, Impact, Confidence, and Effort. During initiative decomposition, it optionally ranks generated stories in a dedicated phase to help teams sequence work on the kanban board effectively.

How do I coordinate epic and story creation sequentially for a new project initiative?

Sequential epic and story creation ensures Epics are decomposed and reviewed before Stories are generated. A phase-based orchestrator manages this workflow, delegating tasks to specialized coordinators to maintain structural integrity across the project lifecycle.

Does this initiative decomposition workflow require manual Team ID configuration?

Manual Team ID configuration is not required. The orchestrator auto-discovers Team IDs directly from project configurations and the Kanban board, streamlining the decomposition process and eliminating manual setup overhead.

What's the best way to generate a project summary after batch epic and story creation?

Generating a project summary after batch creation is handled by compiling a final summary phase. It aggregates all decomposed Epics and Stories, reporting results and next steps to the kanban_board.md file for downstream reference.

Can I integrate RICE prioritization and scope decomposition with downstream validators?

Downstream validators and executors integrate seamlessly after scope decomposition. The orchestrator supports integration with downstream tools as part of the end-to-end flow, ensuring validated stories are ready for execution on the kanban board.