From orchestrate
Generates the next self-contained task file from a plan, with context, scope, acceptance criteria, and constraints. Tracks progress for sequential decomposition.
npx claudepluginhub haowjy/orchestrate --plugin orchestrateThis skill uses the workspace's default tool permissions.
Create the next implementable task from a plan.
Parses plan Markdown files from context/plans/ into Claude Code tasks: implementation steps with files and verification tasks with dependencies. Invoke via /implement-plan [filename].
Decomposes contextualized plans into atomic, independently executable tasks with embedded context, CLEAR ordering, CoVe checks, and dependency graphs for parallel execution.
Breaks down implementation plans into detailed task lists with agent contexts, acceptance criteria, dependencies, priorities, complexity levels, and status tracking.
Share bugs, ideas, or general feedback.
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.