waypoint-planner

Decompose designed waypoints into a task DAG using Claude Code's TaskCreate.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/ryanismert/do-stuff-helper --skill waypoint-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: waypoint-planner
Source: https://github.com/ryanismert/do-stuff-helper/tree/main/skills/waypoint-planner
Command: npx skills add https://github.com/ryanismert/do-stuff-helper --skill waypoint-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read a designed waypoint and recursively decompose it into a task DAG using Claude Code's native TaskCreate. Tasks are tagged with waypoint metadata, have proper dependencies via addBlockedBy/addBlocks, and persist across sessions via CLAUDE_CODE_TASK_LIST_ID.

Core Features & Use Cases

  • Recursive decomposition: turn designs into a structured, executable DAG of tasks.
  • Metadata tagging & dependencies: tasks carry waypoint IDs and correct blocking relationships for deterministic execution.
  • Cross-session persistence: tasks persist across sessions via the CLAUDE_CODE_TASK_LIST_ID to enable resumption.
  • Deterministic task creation: uses Claude Code's TaskCreate to generate reproducible task sets from designs.

Quick Start

Provide a saved waypoint design and run the waypoint-planner to decompose it into a task DAG.

Frequently Asked Questions about waypoint-planner

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

FAQPage Schema
How do I decompose project waypoints into a task DAG?

Waypoint planning recursively decomposes designed waypoints into a task DAG using Claude Code's TaskCreate, tagging tasks with waypoint metadata and proper blocking dependencies for deterministic execution.

What is a task DAG and how does it help with workflow automation?

A task DAG structures executable tasks with proper blocking dependencies via addBlockedBy/addBlocks, ensuring deterministic execution order and cross-session persistence for workflow automation.

How do I set up the environment to use the waypoint-planner?

Setup requires configuring CLAUDE_CODE_TASK_LIST_ID for cross-session task persistence and saving a designed waypoint document under docs/waypoints to drive the recursive decomposition process.

Can I persist task DAGs across different sessions in Claude Code?

Yes, task DAGs persist across sessions by setting the CLAUDE_CODE_TASK_LIST_ID environment variable, which maintains task metadata and blocking relationships for resumable workflow execution.

Do I need a pre-designed waypoint before generating a task DAG?

Yes, a pre-designed waypoint must exist under docs/waypoints with its dependencies ready, as the planner reads this design to recursively generate the sequence of leaf tasks with blocking relationships.

What's the best way to manage task dependencies in automated workflows?

Managing task dependencies is best handled by generating a task DAG that uses addBlockedBy and addBlocks to establish correct blocking relationships, ensuring deterministic execution of leaf tasks.