plan-orchestrator
From the author
THE BRAIN behind /toh-plan — analyzes the request or PRD, writes .toh/plan.md per the orchestration-protocol Section D schema (plans are files, never chat state), shows a condensed summary, and holds the single "Go" approval gate before handing execution to THE TOH LOOP. Also drafts plans for /toh-vibe. Use for planning, re-planning, or adjusting a plan before execution.
Install
npx skills add wasintoh/toh-framework --skill plan-orchestrator -a claude-code
Installs to .claude/skills/plan-orchestrator/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 81
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- ops-orchestratorDasDigitaleMomentum/opencode-processing-skillsOrchestrator for structured planning, documentation, and gated implementation using docs/ and plans/. Use when planning features, documenting codebases, executing plan phases, or resuming multi-session work.Planning★ 60
- orchestration-protocolwasintoh/toh-frameworkThe single source of truth for how TFW commands survey their runtime, choose an execution mode (teams / subagents / sequential), route models, and run the TOH LOOP — the autonomous plan-execute-verify protocol driven by .toh/plan.md + .toh/progress.md. Loaded by /toh, /toh-vibe, /toh-plan. Triggers: build a whole plan, resume a plan, "continue building", autonomous execution, multi-agent orchestration, parallel agents, work until done, MVP build, big multi-task jobs.Planning★ 98
- plan-orchestratemturac/everything-openai-codexRead a plan document, decompose it into steps, design a per-step agent chain from the ecc catalogue, and emit ready-to-paste /orchestrate custom prompts. Generative only — never invokes /orchestrate itself. Use when the user has a multi-step plan and wants to drive it through orchestrate without composing chains by hand.Planning★ 83
- plannerjdrhyne/agent-skillsCreate structured plans for multi-task projects that can be used by the task-orchestrator skill. Use when breaking down complex work into parallel and sequential tasks with dependencies.Planning★ 240
- vibe-orchestratorwasintoh/toh-frameworkMaster workflow controller for Lovable-style development. Creates working UI immediately from ANY prompt - no questions asked, no choices given. Resumes or materializes .toh/plan.md, generates the design identity (root DESIGN.md) first, then spawns specialist sub-agents from plan task lines (ui-builder, dev-builder, design-reviewer, backend-connector, platform-adapter). Triggers: create, build, make, want, new project requests, app ideas, MVP, prototype, or any development request. This skill MUST be read first for any development task.Design★ 98
- planhashgraph-online/awesome-codex-pluginsPlan future work, investigate before building, research a topic, or compare the alternatives for a choice. Takes optional free text. The skill reads the request, open drafts, accepted canon, branch, and code, then creates only the documents a later reader needs — none for a small fix. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'plan the onboarding journey', 'investigate X before we plan', 'compare the alternatives for Y', 'REST or a queue? two teams disagree', 'I need market research before we plan', 'we are regulated — trace the requirements'. With no arguments it resumes an open planning draft or offers what to plan next. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review.Planning★ 1.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in