daf-issue-topo-sort

Issue Topology Sort

Topologically sort issues by explicit dependencies AND file conflict avoidance. Produces an ordered work plan with concurrent groups.

Usage

/daf-issue-topo-sort [--repo owner/repo] [--label <label>] [--parent <JIRA-KEY>]

GitHub: /daf-issue-topo-sort --repo owner/repo --label v1.0 GitHub (current repo): /daf-issue-topo-sort --label v1.0 JIRA: /daf-issue-topo-sort --parent PROJ-123

If no arguments given, ask the user which mode (GitHub or JIRA) and the required parameters.

---

Step 1: Gather Issues

GitHub

gh issue list --repo <repo> --label <label> --state open --json number,title,body,url --limit 100

If --repo not provided, use current repository (auto-detected from git remote).

For each issue, also fetch comments:

gh issue view <number> --repo <repo> --json comments --jq '.comments[].body'

JIRA

Use MCP JIRA tools to fetch child issues of the parent:

mcp__mcp-atlassian__jira_search(
  jql="parent = <PARENT-KEY> AND status != Done ORDER BY key ASC",
  fields="summary,status,description,comment,issuelinks"
)

For each issue, also fetch full details including comments:

mcp__mcp-atlassian__jira_get_issue(issue_key=<KEY>, fields="*all", comment_limit=50)

Output of this step: A list of open issues only, each with: key/number, title, body/description, comments, and (for JIRA) existing issue links. Closed/done issues must never appear in this list or any subsequent step.

---

Step 2: Analyze Each Issue

For each issue, extract two things:

2a. Explicit Dependencies

Scan issue body AND all comments for dependency patterns (case-insensitive):

Pattern	Meaning
depends on #X / depends on PROJ-X	This issue depends on X
after #X / after PROJ-X	This issue should come after X
needs #X first / needs PROJ-X first	This issue needs X completed first
blocked by #X / blocked by PROJ-X	This issue is blocked by X
requires #X / requires PROJ-X	This issue requires X
prerequisite: #X / prerequisite: PROJ-X	X is a prerequisite