subtask-detection

Detect and resolve GitHub Issue subtasks with dependency-based execution ordering.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/takemo101/compose-workflow --skill subtask-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subtask-detection
Source: https://github.com/takemo101/compose-workflow/tree/main/.opencode/skill/subtask-detection
Command: npx skills add https://github.com/takemo101/compose-workflow --skill subtask-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of breaking down large parent issues into smaller, manageable subtasks and determining the correct execution order based on dependencies.

Core Features & Use Cases

  • Subtask Detection: Automatically identifies subtasks linked to a parent issue through various formats (checkboxes, comments, explicit mentions).
  • Dependency Resolution: Determines execution order using GitHub's dependency API or by parsing explicit text patterns within issue bodies.
  • Use Case: When a complex feature is created as a parent GitHub Issue, this Skill can automatically find all related subtasks and present them in a sequence that respects their interdependencies, streamlining the development workflow.

Quick Start

Use the subtask-detection skill to resolve and order the subtasks for issue number 123.

Frequently Asked Questions about subtask-detection

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

FAQPage Schema
How do I automate subtask detection and dependency resolution for GitHub issues?

Automate subtask detection by identifying linked subtasks through parent issue body checklists, comments, and explicit references, then resolving their execution order using GitHub's dependency API or text pattern matching.

What is the best way to establish a topologically sorted execution order for GitHub subtasks?

Establish a topologically sorted execution order by parsing explicit and implicit dependencies within GitHub issues, using either the GitHub dependency API or text pattern matching to sequence the subtasks correctly.

Can I detect subtasks in GitHub issues if they are only defined in comments or checklists?

Yes, you can detect subtasks defined in issue body checklists, comments, or explicit 'Subtask of' references, allowing flexible issue decomposition without requiring a strict linking format.

How does dependency resolution work when explicit GitHub issue links are missing?

Dependency resolution falls back to text pattern matching within issue bodies when explicit GitHub dependency API links are missing, parsing the text to infer and map the required execution sequence.

Do I need the GitHub dependency API to resolve subtask execution order?

No, you do not need the GitHub dependency API, because dependency resolution can also be achieved by parsing explicit text patterns within issue bodies to determine the correct subtask sequence.