shouenlee/task_breakdown
plugins/task-breakdown/skills/task_breakdown/SKILL.md
Decomposes feature descriptions or GitHub issues into ordered subtasks with file-level scope, acceptance criteria, and optional gh issue create. Use when asked to "break down task", "decompose feature", "create subtasks", "plan implementation", "break this into tasks", "task list", or "implementation plan".
tools
Updated Apr 14, 2026
$ install --global
skillsauthnpx skillsauth add shouenlee/ghcp-dev-plugin task_breakdownInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 14, 2026, 2:29 AM62.2s1 file scanned
SKILL.md
- name:
- task_breakdown
- description:
- Decomposes feature descriptions or GitHub issues into ordered subtasks with file-level scope, acceptance criteria, and optional gh issue create. Use when asked to "break down task", "decompose feature", "create subtasks", "plan implementation", "break this into tasks", "task list", or "implementation plan".
Task Breakdown
Decompose feature descriptions or GitHub issues into ordered implementation subtasks with file-level scope, acceptance criteria, and dependency ordering.
When to Use
- You have a feature description or GitHub issue that needs to be broken into actionable subtasks
- You want to plan an implementation with clear ordering and dependencies
- You need to create GitHub issues for each subtask in a larger feature
- You want to estimate complexity and scope before starting work
Prerequisites
- A feature description, GitHub issue number, or branch/PR to analyze
ghCLI installed and authenticated (required only for fetching issues and creating subtasks as issues)
Workflow
-
Gather the feature or task to decompose:
- If the user provides a GitHub issue number, fetch it:
gh issue view <number> --json title,body,labels,comments - If the user provides a description, use it directly
- If the user provides a branch name or PR, analyze the scope from the diff or description
- If the user provides a GitHub issue number, fetch it:
-
Analyze the codebase to understand:
- Which files and modules will need changes
- Dependencies between components
- Existing patterns for similar features
- Test infrastructure and conventions
-
Break down into ordered subtasks, each including:
- Title: Clear, imperative-mood description (e.g., "Add User model with email and password fields")
- Files: Specific files to create or modify
- Acceptance criteria: Measurable conditions for "done"
- Dependencies: Which other subtasks must complete first
- Estimated complexity: Small / Medium / Large
-
Order subtasks by dependency (foundation first, integration last):
- Data models and schemas first
- Business logic and services next
- API endpoints / views
- Tests alongside or after implementation
- Documentation and cleanup last
-
Present the breakdown as a numbered list for the user to review.
-
Offer to create GitHub issues for each subtask:
gh issue create --title "<title>" --body "<body with acceptance criteria>"- Add labels if specified
- Set up issue references between dependent tasks
-
Optionally create a tracking issue that links to all subtasks so progress can be monitored from a single place.
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| Issue not found | The issue number does not exist or gh is not authenticated | Verify the issue number and run gh auth status to check authentication |
| Scope too vague | The feature description lacks enough detail to identify files | Ask the user clarifying questions about expected behavior, affected components, and constraints |
| Circular dependencies | Two subtasks depend on each other | Merge the coupled subtasks into one or extract the shared concern into a separate subtask that both depend on |
Related Skills
shouenlee/release_notes
documentation
VerifiedTrustedCommunity
Generates changelogs from conventional commits, bumps semantic versions in pyproject.toml or package.json, and publishes GitHub releases. Use when asked to "create release", "release notes", "changelog", "bump version", "semantic version", "tag release", "publish release", or "what changed since last release".
SKILL.mdUpdated Apr 14, 2026
shouenlee/python_lint_fix
development
VerifiedTrustedCommunity
Runs ruff, mypy, and bandit on changed Python files — explains violations and auto-fixes with ruff check --fix. Use when asked to "lint", "fix lint", "check types", "type check", "run mypy", "run ruff", "python quality", or "lint python files".
SKILL.mdUpdated Apr 14, 2026
shouenlee/make_skill_template
development
VerifiedTrustedCommunity
Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional scripts/references/assets folders.
SKILL.mdUpdated Apr 14, 2026
shouenlee/resolve_pr
development
VerifiedTrustedCommunity
Fetch active PR review threads from GitHub and resolve them by making code changes. Use when the user wants to address, fix, or resolve PR review comments automatically.
SKILL.mdUpdated Apr 14, 2026