cw-plan

Convert software specifications into dependency-aware task graphs with parent and sub-tasks.

14|1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/sighup/claude-workflow --skill cw-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cw-plan
Source: https://github.com/sighup/claude-workflow/tree/main/skills/cw-plan
Command: npx skills add https://github.com/sighup/claude-workflow --skill cw-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams convert a written spec into a structured, dependency-aware task graph, enabling autonomous execution by producing demoable parent units first and then decomposed sub-tasks after approval.

Core Features & Use Cases

  • Converts a spec into a native task graph using TaskCreate/TaskUpdate, establishing clear parent–subtask relationships and metadata for workers.
  • Enforces an explicit approval step before decomposition to maintain alignment and control scope.
  • Generates self-contained task metadata, verification steps, and proof artifacts to support automated execution and traceability.
  • Use cases include feature development pipelines, spec-driven automation, and collaborative planning with auditable DAGs.

Quick Start

Provide a project spec and ask cw-plan to generate a parent-task graph with dependencies for review.

Frequently Asked Questions about cw-plan

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

FAQPage Schema
How do I turn a software specification into a dependency-aware task graph?

A specification is converted into a dependency-aware task graph by mapping requirements to parent demoable units first, then creating sub-tasks upon approval to enable autonomous execution.

How does spec-driven task graph generation enforce atomic and testable outcomes?

Spec-driven task graph generation enforces atomic and testable outcomes by validating dependencies, mapping requirements to self-contained tasks, and producing verification steps with proof artifacts for traceability.

Do I need an explicit approval step before decomposing tasks in an autonomous workflow?

Yes, an explicit approval step is enforced before decomposing parent demoable units into sub-tasks, maintaining alignment and controlling scope before autonomous execution of the dependency-aware task graph.

What's the best way to structure a feature development pipeline using a task graph?

The best way to structure a feature development pipeline is by creating parent demoable units first, enforcing an explicit approval step before decomposition, and generating native task metadata with proof artifacts to guide workflow execution.

Where does automated task planning read project specs from?

Automated task planning reads the project spec from the docs/specs directory or the most recent spec available, mapping requirements to tasks and producing native task metadata to guide autonomous workflow execution.

Why does my task graph decomposition fail dependency validation?

Task graph decomposition fails dependency validation when mapped requirements lack proper dependency awareness or when parent demoable units have not received the explicit approval required before sub-task decomposition.