Stats
Actions
Tags
From orchestrate
Generates the next self-contained task file from a plan, with context, scope, acceptance criteria, and constraints. Tracks progress for sequential decomposition.
How this skill is triggered — by the user, by Claude, or both
Slash command
/orchestrate:plan-taskThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create the next implementable task from a plan.
Create the next implementable task from a plan.
Use these prompt variables:
{{PLAN_FILE}} — source plan to readResolve output directory:
<dir-of-PLAN_FILE>/tasks.Gather context on what is already completed:
{{PLAN_FILE}} and inspect status/phase tracking sections.<resolved-tasks-dir>/progress.md exists, read it for prior completed tasks.<resolved-tasks-dir>/task.md exists, use it as context for continuity.If all phases/steps in the plan are complete:
ALL_DONE to <resolved-tasks-dir>/task.md.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:
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.
npx claudepluginhub haowjy/orchestrate --plugin orchestrateDecomposes contextualized plans into atomic, independently executable tasks with embedded context, CLEAR ordering, CoVe checks, and dependency graphs for parallel execution.
Parses Markdown plan files from context/plans/ into Claude Code tasks with implementation, verification steps, and dependencies. Invoke via /implement-plan [filename] to create executable workflows.
Creates structured implementation plans for multi-step tasks from specs or requirements. Generates plan.json and task markdown files with explicit code and testing steps.