backlog-technical-project-manager

backlog-technical-project-manager is a skill for Claude Code, Codex from MrLesk/Backlog.md. It costs 90 tokens per session (1,935 once invoked), scanned A, original, MIT.

A coordination workflow for managing existing Backlog.md tasks with multiple helper agents. It covers planning, delegating implementation work, checking results, and finishing tasks.

In plain words
What is it for?
Use it only when explicitly taking over Backlog.md tasks, coordinating contributors or agents, and approving completed work.
Why use it?
It provides a controlled way to handle larger workstreams without losing track of requirements, dependencies, or acceptance criteria.

Skill for Claude CodeCodex

About the project

Backlog.md is a Markdown-based task manager and Kanban board for Git repositories, storing project tasks as plain files and providing a zero-configuration command-line interface. It is for teams and AI agents that need to define work, review implementation plans, track coding tasks, and preserve a readable record in Git.

MrLesk/Backlog.md · 6,631 stars · on GitHub

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/mrlesk/backlog.md/backlog-technical-project-manager
Any agent
npx skills add MrLesk/Backlog.md --skill backlog-technical-project-manager
Clone the repo
git clone --depth 1 https://github.com/MrLesk/Backlog.md

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 backlog-technical-project-manager

README.md
[![agentmods](https://agentmods.dev/badge/skills/mrlesk/backlog.md/backlog-technical-project-manager.svg)](https://agentmods.dev/skills/mrlesk/backlog.md/backlog-technical-project-manager)
Your own site
<a href="https://agentmods.dev/skills/mrlesk/backlog.md/backlog-technical-project-manager"><img src="https://agentmods.dev/badge/skills/mrlesk/backlog.md/backlog-technical-project-manager.svg" alt="Measured on agentmods" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,935 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.00090 $0.01935
Opus 5 $0.00045 $0.00967
Sonnet 5 $0.00018 $0.00387
Haiku 4.5 $0.00009 $0.00194

Measured 5d ago against content hash 58702bf61525, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

backlog-technical-project-manager 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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.codex/skills/backlog-technical-project-manager/SKILL.md · 182 lines

How it starts

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

Backlog.md Technical Project Manager

Overview

Act as a coordinator and approver for complex Backlog.md task delivery. Avoid deep code implementation work directly; delegate discovery and coding to sub-agents, then validate business outcomes and acceptance criteria.

Activation Rule

Activate this skill only after explicit user intent to delegate coordination, such as:

  • "Act as TPM"
  • "Take over these tasks"
  • "Coordinate implementation with sub-agents"

If intent is not explicit, ask for confirmation before activating.

TPM Operating Constraints

  1. Read Backlog.md workflow guidance first:
    • backlog://workflow/overview
    • backlog://workflow/task-creation
    • backlog://workflow/task-execution
    • backlog://workflow/task-finalization
  2. Treat the workflow resources above as authoritative for Backlog.md process behavior.
  3. Keep TPM token usage focused:
    • Do not perform broad codebase research yourself
    • Delegate implementation research, blast-radius analysis, and coding to sub-agents
  4. Verify requirements and outcomes:
    • Confirm each approved plan maps to task acceptance criteria and Definition of Done
    • Enforce scope boundaries and dependency-safe sequencing
  5. Unblock verification aggressively when needed:
    • TPM is authorized to install required tooling/dependencies for agents
    • TPM is authorized to troubleshoot the environment (including stopping stuck processes) so verification can run
    • TPM should not accept "done" without verifiable evidence
  6. Maintain the skill's operational memory:
    • Keep the ## Common Agent Mistakes (Keep Updated) section current
    • At the end of each takeover, add newly observed repeatable failure patterns
    • Remove or rewrite stale entries when process or tooling changes make them obsolete
  7. Improve quality gates with explicit user approval:
    • When recurring verification gaps appear, propose DoD updates to the user
    • Suggest concrete new DoD checklist items when they would prevent repeat failures
    • Do not silently change task DoD scope; present recommendation and wait for user decision
  8. Keep task-record git state consistent:
    • Sub-agents must update task records on their own task branch as part of their task delivery
    • Do not perform standalone task-record sync commits on main

Read the full file on GitHub · 182 lines

Files

What ships with it

1 file 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.

  1. 5d ago First seen · 182 lines · 90 tokens per session scan A 58702bf61525

Subscribe to this mod's changes

backlog-technical-project-manager is a skill published in the GitHub repository MrLesk/Backlog.md (6,631 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 1,935 once invoked, about $0.0005 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.

Related

Other skills, from other repositories