What is task-plan-v2-orchestrator?

A planning and coordination guide for multi-step coding work using a Markdown task plan. It separates preparation, implementation tasks, tests, reviews, rollbacks, and a derived HTML dashboard.

Use it to create, reorganize, or audit plans for work handled by several agents, including task ownership, execution rules, verification, rollback details, and dashboard views.

It turns loose requirements into a clear sequence with dependencies and checks, so work is easier to coordinate and incomplete preparation is visible before coding starts.

task-plan-v2-orchestrator — Skill for Codex by sergekostenchuk

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add sergekostenchuk/ui-ux-agent-skill-system --skill task-plan-v2-orchestrator

Clone the repo

git clone --depth 1 https://github.com/sergekostenchuk/ui-ux-agent-skill-system

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/task-plan-v2-orchestrator/github.svg)](https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/task-plan-v2-orchestrator)

Your own site

<a href="https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/task-plan-v2-orchestrator"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/task-plan-v2-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/task-plan-v2-orchestrator"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/task-plan-v2-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 119 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,459 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00119	$0.01459
Opus 5	$0.00060	$0.00730
Sonnet 5	$0.00024	$0.00292
Haiku 4.5	$0.00012	$0.00146

Measured 12d ago against content hash 836dd286cb67, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

task-plan-v2-orchestrator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

core/skills/task-plan-v2-orchestrator/SKILL.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Task Plan V2 Orchestrator

Use this skill for planning and orchestration artifacts, not for feature implementation itself.

Canonical Model

FEATURE-PREPARATION.md is the pre-implementation gate.
TASK-PLAN.md is the canonical, editable control document.
TASK-DASHBOARD.html is derived from Markdown and never the source of truth.

If the user asks for only one file, preserve the same logical separation inside that file.

Workflow

Classify the request:
- create a new plan
- refactor an existing plan
- audit a plan
- prepare runtime-specific projections
Read references/field-layers.md.
If the user mentioned Codex, Claude Code, Gemini, or Antigravity, also read references/runtime-adapters.md.
If the user wants HTML, dashboard, graph, kanban, or observability views, also read references/dashboard-contract.md.
Start with the pre-implementation layer. If it is incomplete, do not mark implementation tasks as ready.
Normalize every task into a stable task block with explicit fields instead of freeform prose.
Model multi-agent execution as sequential by default.
Add Execution Governance and Verification Policy before task execution.
Keep missing facts explicit as TBD, unknown, or open_question; do not invent them.
Treat critical TBD fields as blockers for ready, in_progress, approved, and done.
Default to NO-MOCKS and NO-PLACEHOLDERS.
If a mock or placeholder is temporarily unavoidable, convert it into an explicit alarm with replacement requirements and carry that alarm into every downstream prompt or runtime projection.

Multi-Agent Rules

A task may have many agents, but only one current owner_role.
agent_sequence is ordered and sequential unless the user explicitly asks for parallel lanes.
agent_contracts must define:
- entry criteria
- expected outputs
- handoff target
- stop conditions
required_approvals must name roles or gates, not vague "review".
max_review_loops must be finite.
escalation_rule must say what happens when review loops are exhausted or a blocker cannot be resolved locally.

Read the full file on GitHub · 114 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 114 lines · 119 tokens per session scan A 836dd286cb67

Subscribe to this mod's changes

task-plan-v2-orchestrator is a skill published in the GitHub repository sergekostenchuk/ui-ux-agent-skill-system (23 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 119 tokens to every session and 1,459 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agents Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens