plan

To turn design docs into executable tasks, this Skill converts design documents into a wired, dependency-aware task graph. It extracts work items from design sections, groups them into phases, and generates a ready-to-run task set for Claude Code execution.

Task graph generation works by mapping design document sections to phase-based tasks with explicit dependencies and blockers. It validates required frontmatter like name and description, then derives a deterministic task graph that respects external blockers to seed a compliant execution plan.

Yes, this planning workflow supports multi-session planning and manages external blockers as tasks in a pending state. It generates a deterministic task graph that tracks these blockers, ensuring dependencies are respected across multiple execution phases.

The best way to group design sections into implementation phases is by extracting work items from numbered design sections like 11.1 and 11.2, then mapping them into a phase-based plan with explicit dependencies, blockers, and a ready-to-run task set.

Yes, you need specific frontmatter in your design documents to generate a task graph. The planning process validates required frontmatter fields, specifically name and description, before mapping design sections to a compliant task graph for execution.

A limitation of converting design docs to task graphs is that the design document must be located in the docs/ directory or provided via ARGUMENTS. The task graph generation relies entirely on the structure and content of the input design document to derive phases and dependencies.