orchestrate

A coordinator that reads pending tasks from a PRD and assigns them to coding agents. A PRD is a document that lists product tasks, their steps, and their current status.

In plain words
What is it for?
Use it to run the next task, a specified task, a phase, or a chosen number of pending tasks through coding agents.
Why use it?
It removes the need to select and start each pending task manually while keeping execution tied to the project's task list.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/xpcoffee/nvim-markdown-notes-memgraph/orchestrate
Any agent
npx skills add xpcoffee/nvim-markdown-notes-memgraph --skill orchestrate
Clone the repo
git clone --depth 1 https://github.com/xpcoffee/nvim-markdown-notes-memgraph

Made for: Claude Code, Codex.

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 524 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.00524
Opus 5 $0.00009 $0.00262
Sonnet 5 $0.00004 $0.00105
Haiku 4.5 $0.00002 $0.00052

Measured yesterday against content hash 6a3b4857380e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

orchestrate 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 yesterday.

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.

.claude/skills/orchestrate/SKILL.md · 58 lines

What it actually says

Orchestrate PRD Tasks

You coordinate the execution of PRD tasks by spawning coder subagents.

Steps

  1. Read prd.json and identify all tasks with "status": "pending".

  2. Parse the argument to determine scope:

    • No argument or next: run the next pending task (lowest ID)
    • phase N (e.g. phase 2): run all pending tasks in phase N, sequentially
    • A task ID (e.g. 2.1): run that specific task
    • N tasks (e.g. 3 tasks): run the next N pending tasks sequentially
  3. For each task in scope, spawn a coder subagent via the Task tool:

    • Set subagent_type to "coder"
    • Include in the prompt:
      • The task ID, description, phase, category
      • The full steps array
      • Instruction to read CLAUDE.md and ARCHITECTURE.md first
    • Example:
      Task(coder): Implement PRD task 1.2
      Prompt: |
        Implement task 1.2 from prd.json.
      
        ID: 1.2
        Phase: 1
        Category: setup
        Description: Set up src/nvim_markdown_notes_memgraph/ package structure
        Steps:
        1. Create src/nvim_markdown_notes_memgraph/ directory
        2. Create __init__.py with version
        3. Verify package imports work
      
        Read CLAUDE.md and ARCHITECTURE.md first for project context and workflow.
      
  4. After each subagent completes, read prd.json to verify the task status was updated.

  5. Report results:

    • List which tasks completed successfully
    • List which tasks failed (if any)
    • Show count of remaining pending tasks

Notes

  • Run tasks sequentially, not in parallel
  • Tasks in phase 7 modify files in /home/rick/code/personal/nvim-markdown-notes (outside this repo)
  • If a task fails, report it and continue to the next task in scope
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.

  1. yesterday First seen · 58 lines · 18 tokens per session scan A 6a3b4857380e

Subscribe to this mod's changes

orchestrate is a skill published in the GitHub repository xpcoffee/nvim-markdown-notes-memgraph (0 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 524 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 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

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens