plan-dag

Render the current plan as a dependency DAG so sequencing, the critical path, and parallelizable work are visible at a glance. Default output is monospace text using Unicode box-drawing glyphs (─, ►, ┐ ├ ┤ └) so it lands cleanly in chat, terminals, and PR descriptions.

This skill is repo-agnostic. It assumes a GitHub-backed issue tracker with sub-issue links and dependency-language prose; it makes no assumptions about specific labels, area taxonomies, or repo-specific dev-process skills.

When to use

• After a what's next survey, to commit to a sequence.
• When asked "what's left for #N" on an umbrella spec with sub-issues.
• Before picking the next branch — to see what unblocks the most downstream work.
• When a spec fans out into N sub-issues and the dependency edges aren't all linear.

Skip when:

• A single-PR spec — the plan is the Plan section, not a DAG.
• An unanswered design question — drawing a DAG before alignment is theater.
• The "graph" is one linear chain of three or fewer nodes — a sentence is shorter than a diagram.