Does this skill actually write or execute code?

No, this skill is strictly for the planning phase. Execution is handled by a separate 'execute' skill once the task DAG is finalized.

What inputs are required for the planning phase?

It requires a target project directory and a specification file, typically generated during the /specify phase of the Tasker workflow.

What are the outputs of the Plan skill?

It generates task JSON files, a physical map of the project, and a validation report to ensure the plan is technically sound.

Can I use the Plan skill on an existing codebase?

Yes, the skill automatically detects existing source files and analyzes the project structure to ensure new tasks are compatible with your current architecture.

What is the primary purpose of the Plan skill?

The Plan skill takes a project specification and decomposes it into a structured, executable list of tasks known as a Directed Acyclic Graph (DAG).

Plan (Tasker Workflow)

Name: Plan (Tasker Workflow)
Author: Dowwie

byDowwie

•

Productivity & Workflow

Decomposes project specifications into an executable task DAG with dependencies and phases.

The plan skill is the orchestration engine for the architectural phase of the Tasker framework. It automates the transition from a high-level specification to a concrete, validated technical plan by analyzing project structure, mapping capabilities, and generating a Directed Acyclic Graph (DAG) of tasks. It ensures architectural consistency by utilizing specialized sub-agents for logical and physical mapping, producing a structured set of JSON-defined tasks ready for automated execution without requiring manual decomposition.