Plan task

Skill haowjy/orchestrate/skills/plan-task

Breaks the next task from a plan into an implementable task file. Use when decomposing a multi-step plan into ordered work units.From its SKILL.md

Install

npx -y skills add haowjy/orchestrate --skill plan-task

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, as published. Nobody here has run it

Plan Task

Create the next implementable task from a plan.

When Invoked

Step 1: Read Inputs

Use these prompt variables:

{{PLAN_FILE}} — source plan to read

Resolve output directory:

Always use a path next to the plan: <dir-of-PLAN_FILE>/tasks.
Create the output directory if it does not exist.

Step 2: Read Progress

Gather context on what is already completed:

Read {{PLAN_FILE}} and inspect status/phase tracking sections.
If <resolved-tasks-dir>/progress.md exists, read it for prior completed tasks.
If <resolved-tasks-dir>/task.md exists, use it as context for continuity.

Step 3: Determine Completion

If all phases/steps in the plan are complete:

Write only the text ALL_DONE to <resolved-tasks-dir>/task.md.
Stop here.

Step 4: Create Task File

Determine the next logical task from the plan.

Write <resolved-tasks-dir>/task.md. Include whatever structure makes sense, but the task file should give an implementing agent everything it needs:

Context: why this task is next
Scope: what to implement — files, functions, integration points
Acceptance criteria: how to verify it's done
Constraints: architectural limits, gotchas

A good task is self-contained: the codebase must be in a working state when done. Size is secondary — focus on logical completeness, not line count.