build-epic

List an epic's open tickets in board order and tag each one buildable, blocked or owner-step, so you know which tickets can be built now and in what order. Steps 1-3 only read Jira and git and print the list. Step 4 builds the buildable tickets one at a time, only when the user says yes.

Triggers: /tdd-pipeline:build-epic <EPIC-KEY>, e.g. /tdd-pipeline:build-epic PROJ-70.

Epic: $ARGUMENTS

---

Step 0 — Preconditions

• No key in $ARGUMENTS → STOP: "Name the epic: /tdd-pipeline:build-epic <EPIC-KEY>."
• Run the Wiring check and Detection in ${CLAUDE_PLUGIN_ROOT}/references/jira-mcp.md. This command is entirely about the ticket: no Jira: line, or no Atlassian MCP → STOP with that file's one line.
• Determine <default> per ${CLAUDE_PLUGIN_ROOT}/references/git-host.md, then git fetch origin <default> -q.
• Worktree check: a JS repo (package.json at the root) or an iOS repo (Podfile or a *.xcodeproj) with no .worktreeinclude at the root → STOP. Test each marker on its own ([ -e package.json ], [ -e Podfile ], find . -maxdepth 1 -name '*.xcodeproj'): one ls with a glob aborts in zsh when the glob matches nothing. "❌ No .worktreeinclude: a worktree of this repo starts without its gitignored files (.env, node_modules, Pods). List the ones a build needs in .worktreeinclude, then re-run."

Step 1 — Read the epic's open children

One call to the resolved search issues by JQL tool:

parent = <EPIC> AND statusCategory != Done ORDER BY rank ASC

Ask for fields summary, status, issuetype, issuelinks, description (50 results; description feeds rule 4), in the tool's fuller view when its schema has one (see ${CLAUDE_PLUGIN_ROOT}/references/jira-mcp.md). If issuelinks is still missing from every row, print once: "⚠️ Jira returned no issuelinks: blockers come from titles only." Never read a missing field as "no blockers". One plain line each, then STOP:

• the key does not exist or is not an epic → "❌ is not an epic."
• zero rows → "✅ has no open children."
• the call fails → "⚠️ Jira unreachable: ."