plan

Decompose a specification into an executable task DAG with dependencies and phased execution.

19|1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/Dowwie/tasker --skill plan-dowwie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Dowwie/tasker/tree/main/skills/plan
Command: npx skills add https://github.com/Dowwie/tasker --skill plan-dowwie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning deconstructs a specification into a concrete, testable task DAG with explicit dependencies and phased execution, enabling reliable implementation.

Core Features & Use Cases

  • Phase-based planning aligns tasks with dependencies and phases (ingest, logical, physical, definition, validation, sequencing, ready).
  • Generates artifacts such as task DAGs, maps, and validation reports to support auditable planning.
  • Use case: When given a spec, map requirements to tasks and define dependencies to ensure correct ordering and traceability.

Quick Start

Provide the target project directory and run the plan workflow to generate a task DAG with dependencies.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I decompose a specification into an executable task DAG with dependencies?

Decomposing a specification into an executable task DAG involves applying a structured six-phase planning process that maps requirements to tasks and defines explicit dependencies to ensure correct ordering and traceability.

What is phased execution in task DAG planning?

Phased execution in task DAG planning aligns generated tasks with dependencies and specific workflow phases including ingest, logical, physical, definition, validation, sequencing, and ready stages to enable reliable implementation.

How do I generate a task DAG from a spec using a spec-driven workflow?

To generate a task DAG from a target spec within a spec-driven workflow, provide the target project directory and run the planning process to produce the task DAG alongside physical maps and validation reports.

Do I need capability maps and FSM artifacts to generate a task DAG?

You need a target specification to generate a task DAG, and you should provide capability maps and FSM artifacts when available to guide the generation of physical maps and validation artifacts.

What validation artifacts are generated when planning tasks from a spec?

Planning tasks from a target spec generates auditable validation artifacts and reports alongside the task DAG and maps to support safe, auditable planning through the structured six-phase process.