agentmods.dev

pm-as-solo-orchestrator

pm-as-solo-orchestrator is a skill for Claude Code, Codex from makifbaysal/tasktrooper. It costs 40 tokens per session (871 once invoked), scanned A, original, Apache-2.0.

A set of rules for a product manager agent that coordinates a delivery request by writing tasks to a work board. A work board is a list of tasks whose columns show their progress.

In plain words
What is it for?
It helps break a request into board work, assign the planning step correctly, and sequence read-only research before board changes.
Why use it?
It prevents the plan from creating separate duplicate tasks for analysis, implementation, testing, and approval. It also ensures that only the product manager writes the board in this setup.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 113repo +3 changed 4d ago A scan 40 tokens original Apache-2.0

Good fit It helps break a request into board work, assign the planning step correctly, and sequence read-only research before board changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/makifbaysal/tasktrooper/pm-as-solo-orchestrator
View source ↗ makifbaysal/tasktrooper tasktrooper.ai
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 makifbaysal/tasktrooper --skill pm-as-solo-orchestrator
Clone the repo
git clone --depth 1 https://github.com/makifbaysal/tasktrooper

Made for: Claude Code, 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.

agentmods badge for pm-as-solo-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/pm-as-solo-orchestrator/github.svg)](https://agentmods.dev/skills/makifbaysal/tasktrooper/pm-as-solo-orchestrator)
Your own site
<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/pm-as-solo-orchestrator"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/pm-as-solo-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.

agentmods 80×15 button for pm-as-solo-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/pm-as-solo-orchestrator"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/pm-as-solo-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 871 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00871
Opus 5.5 $0.00016 $0.00348
Sonnet 5.5 $0.00008 $0.00174
Haiku 4.5 $0.00004 $0.00087

Measured 4d ago against content hash eb42c265e45a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pm-as-solo-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 4d 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.

catalog/agents/product-manager/skills/pm-as-solo-orchestrator/SKILL.md · 49 lines

How it starts

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

PM as Solo Orchestrator

Overview

When product-manager is the only enabled orchestration agent, the plan you write for a request is not a multi-agent handoff — it's one subtask that writes the board, followed by columns doing the rest of the work automatically.

Core principle: One subtask creates the tasks; the board, not the plan, drives every stage after that.

Rules

  • All subtasks are assigned to product-manager — never to system-architect, security-agent, backend-developer, frontend-developer, mobile-developer, data-scientist, game-developer, or qa-agent. Developer work goes through create_board_task, not an orchestration subtask.
  • Multiple parallel PM subtasks are fine only when every one is read-only (e.g. web research + list_board_tasks concurrently). At most one subtask per parallel group may write to the board; a second board writer in the same group rejects the whole plan. Use depends_on to sequence when a later subtask needs an earlier one's result.
  • Delivery stages (analiz, implementation, QA verification, pm_uat, approval) are board columns the task travels through afterwards — never plan a subtask per stage; that opens one board record per stage for a single piece of work and is rejected before the plan runs.
  • Analiz tasks skip approval — they go straight to todo (investigation is always safe to start).
  • Planner sets ready=false only when a product decision blocks creating any board task (max 3 questions, see stakeholder-intake's ask-vs-assume rule). Otherwise ready=true.

Standard flow — one subtask, in order

  1. Create the tasks in backlog (see implementation-task-spec, acceptance-criteria-gwt).
  2. Call ask_user, choice mode:
    • context: what you asked / what you're assuming (name each assumption so the stakeholder can correct it cheaply) / the task list with assignee and order.
    • options: "Start all (recommended)", "Start only some", "Change something", plus whatever else applies.
  3. On approval, move every approved task to todo with move_board_task. Order lives in blocked_by — never hold a task back in backlog to fake an order; a blocked task parks itself and starts automatically once its blocker lands.
  4. On partial approval, move only the selected tasks; leave the rest in backlog.
  5. On rejection or requested changes, update_board_task the affected fields, or delete_board_task + create_board_task for assignee/derived_from (creation-only fields) — and for task_type when update_board_task's schema does not list it.
  6. Report which tasks moved to todo (agents will pick them up) and which stay in backlog, and why.

Read the full file on GitHub · 49 lines

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. 4d ago Changed eb42c265e45a
  2. 8d ago First seen · 49 lines · 40 tokens per session scan A 3ab7337744f7

Subscribe to this mod's changes

pm-as-solo-orchestrator is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 871 once invoked, about $0.0002 per session on Opus 5.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-10-05.

Autonomous AgentsClaude CodePlanningProject managementagentic-aiai-agentsclaudecoding-agentspm
Related

Other skills, from other repositories

paperclip

Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.

paperclipai/paperclip · 54 tokens

paperclip

Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.

paperclipai/paperclip · 43 tokens

paperclip-board

Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.

paperclipai/paperclip · 47 tokens

paperclip-distill

Use when an operation issue is a Paperclip cursor-window, distill, or backfill. Turn source-bundled Paperclip activity into wiki-insightful project standups, durable project pages, decisions, and history without asset dereferencing.

paperclipai/paperclip · 54 tokens

summarize-status

Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.

paperclipai/paperclip · 0 tokens

paperclip-task-bridge

Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.

paperclipai/paperclip · 27 tokens