planning-task-graph

Plan a multi-file feature by generating phase specifications and a dependency-aware task graph. This separates design from execution tracking, outputting versioned phase docs alongside a machine-readable graph with prerequisites, statuses, and acceptance criteria.

Generate a dependency-aware task graph to track execution order across multiple subsystems. It provides deterministic task sequencing with explicit IDs and prerequisites, ensuring clear handoffs and crash-resumable progress for complex initiatives.

Yes, you can separate feature design from execution tracking using a two-artifact pairing. It generates detailed phase specifications for design reasoning and a machine-parseable task graph for dependency-aware execution tracking.

Version phase documents by generating versioned phase specs and a deterministic task graph. This supports auditable history and crash-resumable progress for large features spanning multiple files or subsystems with explicit phase boundaries.

Use a task graph for feature management when features touch multiple files or subsystems, require phased rollout, or need explicit execution order. It provides deterministic sequencing and machine-parseable dependency tracking over standard lists.