Use this skill when the user wants to "create subissue", "break down issue", "split into tasks", "track subtasks", or manage hierarchical GitHub issues. Creates subissues with parent linking using GitHub's native sub-issues API (with markdown fallback).
/plugin marketplace add constellos/claude-code-plugins/plugin install github-orchestration@constellos-localThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Hierarchical issue management using GitHub's native sub-issues API with automatic PR-subissue coordination.
Subissue Orchestration enables breaking down large epics or features into smaller, trackable tasks. Uses GitHub's native sub-issues API (GA 2025) for proper parent-child relationships that appear in GitHub's UI and Projects, with markdown checklist fallback for compatibility.
GitHub's native sub-issues provide:
The sync-task-to-subissue hook automatically links created subissues using the native API.
Utilities from native-subissues.ts:
addNativeSubissue(cwd, parentIssue, subissueNumber) - Link as native sub-issuelistNativeSubissues(cwd, parentIssue) - List native sub-issuesremoveNativeSubissue(cwd, parentIssue, subissueNumber) - Unlink sub-issuegetParentIssue(cwd, subissueNumber) - Get parent of a sub-issueisNativeSubissuesAvailable(cwd) - Check if API is availableCreate child issues with native linking:
PARENT=42
TITLE="Implement OAuth integration"
# Create subissue
SUBISSUE=$(gh issue create \
--title "$TITLE" \
--label "task" \
--body "**Parent Issue:** #$PARENT
Implementation details for OAuth integration..." \
--json number -q .number)
# Link as native sub-issue (preferred)
SUBISSUE_ID=$(gh api repos/{owner}/{repo}/issues/$SUBISSUE --jq '.id')
gh api repos/{owner}/{repo}/issues/$PARENT/sub_issues -X POST -f sub_issue_id=$SUBISSUE_ID
For repos without native sub-issues, markdown checklists are still supported.
Utilities from subissue-checklist.ts:
hasNativeSubissues(cwd, parentIssue) - Check if native sub-issues existgenerateChecklistMarkdown(subissues) - Create checklist from arrayupdateParentIssueChecklist(cwd, parentIssue, subissues) - Sync checklistaddSubissueToChecklist(cwd, parentIssue, subissue) - Add single itemmarkSubissueComplete(cwd, parentIssue, subissueNumber) - Check off itemsyncSubissueStates(cwd, parentIssue, subissueNumbers) - Sync all states# Create multiple subissues from list
PARENT=42
TASKS=("OAuth integration" "Email auth" "Password reset" "2FA support")
for task in "${TASKS[@]}"; do
gh issue create \
--title "$task" \
--label "task" \
--body "**Parent Issue:** #$PARENT" \
--json number -q .number
done
# Generate and update parent checklist
syncSubissueStates "$PWD" $PARENT
# Create parent epic
PARENT=$(gh issue create \
--title "Authentication System" \
--label "epic" \
--body "## Subtasks
- [ ] Implement OAuth
- [ ] Implement email auth
- [ ] Add password reset
- [ ] Add 2FA support" \
--json number -q .number)
# Create subissues
for task in "Implement OAuth" "Implement email auth" "Add password reset" "Add 2FA support"; do
gh issue create --title "$task" --label "task" --body "**Parent Issue:** #$PARENT"
done
# Mark subissue as complete
gh issue close 43
# Update parent checklist
markSubissueComplete "$PWD" 42 43
# Changes "- [ ] #43 OAuth integration" to "- [x] #43 OAuth integration"
When using stacked PRs with subagents, PRs automatically include Closes #X to close the associated subissue when merged.
Workflow:
sync-task-to-subissue creates subissuestacked-pr-subagent-stop creates PRCloses #subissueNumber (looked up from task-subissues.json)This provides end-to-end tracking from task → subissue → PR → merge.
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.