scope-epic

Decompose project themes into EPIC issue files and child issue stubs.

7|2|Updated Jan 3, 2026

Search Tags:#automation #workflow #scoping #decomposition #epic #issue-tracking

Ready to run

npx skills add https://github.com/BrennonTWilliams/little-loops --skill scope-epic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-epic
Source: https://github.com/BrennonTWilliams/little-loops/tree/main/.gemini/skills/scope-epic
Command: npx skills add https://github.com/BrennonTWilliams/little-loops --skill scope-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the ambiguity of high-level project goals by enforcing a structured decomposition process that ensures every theme is broken down into independently shippable, verified child issues.

Core Features & Use Cases

Automated Decomposition: Transforms a natural-language goal into a formal EPIC file and 3–8 pre-wired child issue stubs.
Learning Test Integration: Automatically identifies external dependencies and creates prerequisite learning tests to prove API behavior before implementation.
Use Case: When starting a new feature, use this to generate a complete project roadmap including implementation tasks and necessary research spikes, ensuring all work is tracked and staged for git.

Quick Start

Use the scope-epic skill to decompose the goal of adding dark mode support into an epic with child issues.

Frequently Asked Questions about scope-epic

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

FAQPage Schema

How do I decompose a high-level project goal into actionable EPICs and child issues?▼

Decompose a high-level project goal by transforming natural-language themes into a formal EPIC file and 3–8 pre-wired child issue stubs. This structured breakdown ensures every theme becomes independently shippable, verified child issues tracked throughout the issue lifecycle.

What is the best way to automate issue decomposition and generate learning tests before implementation?▼

Automated issue decomposition identifies external dependencies and creates prerequisite learning tests to prove API behavior before implementation. This ensures every child issue is pre-verified and staged for git, satisfying requirements for consistent lifecycle tracking.

Can I use automated scoping to generate a git-staged project roadmap for a new feature?▼

Yes, automated scoping generates a complete project roadmap including implementation tasks and research spikes. It creates structured EPIC issue files and associated child issue stubs that are pre-wired and git-staged for immediate task creation.

Does issue decomposition work for managing dependencies and pre-implementation verification in software development workflows?▼

Issue decomposition applies directly to software development workflows requiring systematic task breakdown and dependency management. It enforces a structured process that ensures every theme is broken down into independently shippable, verified child issues with automated learning test generation.

When do I need to break down project themes into structured EPIC issue files?▼

Break down project themes into structured EPIC issue files when starting a new feature that requires a complete project roadmap. This solves ambiguity of high-level goals by enforcing systematic task breakdown and pre-implementation verification.

Why should I use automated epic scoping instead of manually creating issue stubs?▼

Automated epic scoping enforces a structured decomposition process that solves the ambiguity of high-level project goals. It automatically generates 3–8 pre-wired child issue stubs and learning tests, ensuring consistent issue lifecycle tracking and git-staged task creation without manual overhead.