issue-decomposition

Decompose project descriptions into structured GitHub issues with user stories and estimates.

5|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/britt/agent-skills --skill issue-decomposition-britt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-decomposition
Source: https://github.com/britt/agent-skills/tree/main/skills/issue-decomposition
Command: npx skills add https://github.com/britt/agent-skills --skill issue-decomposition-britt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a high-level feature or project idea into actionable GitHub issues is time-consuming and often produces vague, untestable tickets. This Skill converts project descriptions into 5-15 well-structured issues with user stories, acceptance criteria, dependencies, labels, and effort estimates. ## Core Features & Use Cases - INVEST-Quality Issues: Generates issues that are Independent, Negotiable, Valuable, Estimable, Small, and Testable, each with a user story and Given-style acceptance criteria. - Dependency Mapping: Identifies blocking relationships, parallel work opportunities, and the critical path across generated issues. - GitHub CLI Integration: Creates issues directly via gh issue create with labels, after showing a preview table for user approval. - Use Case: You describe "Build a user authentication system" and receive 7 sized issues (registration endpoint, JWT login, password reset, middleware, tests) with explicit dependency chains, ready to create in your repo. ## Quick Start Ask the agent to break your feature description into GitHub issues, for example: "Decompose the user authentication feature into GitHub issues with estimates."

Frequently Asked Questions about issue-decomposition

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

FAQPage Schema
How do I break a feature into GitHub issues?▼

Describe the feature or project goal and the skill generates 5-15 issues, each with a user story, acceptance criteria, dependencies, labels, and a T-shirt estimate. It shows a preview table for approval before creating issues with the gh CLI.

What makes a good GitHub issue for project planning?▼

Good issues follow the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small (1-5 days), and Testable. Each should include a user story, specific acceptance criteria, explicit dependencies, and a realistic effort estimate.

Does issue creation require the GitHub CLI?▼

Yes, automatic issue creation uses `gh issue create` and requires the gh CLI authenticated for the repository. If gh is unavailable, the skill outputs the full issue bodies so you can create them manually.

How are issue dependencies and estimates handled?▼

Dependencies are mapped as blocked-by and blocks relationships, highlighting parallel work and the critical path. Estimates use T-shirt sizes: Small (0.5-1 day), Medium (2-3 days), Large (4-5 days), and XL (1+ week, flagged for further breakdown).

When should I not use issue decomposition?▼

Avoid it for single bug reports or tasks already small enough to be one issue. It is also not for dependency visualization of existing issues; use a dependency-mapping skill for that instead.