backlog-technical-project-manager

Technical project management for Backlog.md workstreams using coordinated sub-agents. Use only when the user explicitly asks Codex to take over one or more existing Backlog.md tasks (for example: "act as TPM", "coordinate these tasks", "delegate to sub-agents"). Orchestrate planning, implementation, and finalization; manage dependencies and overlapping code areas; review and approve sub-agent plans before implementation.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured orchestration skill with strong workflow gates and validation feedback loops. Its main weakness is progressive disclosure: everything lives in a single inline file with no external reference split, and there is minor redundant phrasing.

Suggestions

Split the Sub-Agent Brief Template and Common Agent Mistakes sections into separate reference files (e.g. references/sub-agent-brief.md, references/common-mistakes.md) and link to them from SKILL.md to reduce inline bulk and enable one-level-deep navigation.

Remove redundant restatements — the trailing 'Enforce isolation' line duplicates the Sub-Agent Workspace Rules, and the Activation Rule repeats the frontmatter trigger examples — to tighten the body.

Replace the bare `backlog://workflow/*` URIs with a short note on what each resource covers, so the overview stands on its own before the runtime resources are loaded.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and process-specific, but contains minor redundancy — e.g., the 'Enforce isolation' line restates the Sub-Agent Workspace Rules and the Activation Rule repeats the frontmatter trigger examples.	4 / 5
Actionability	Provides executable guidance — a concrete git-clone bash block, branch naming, `task_view`, and a detailed sub-agent brief template — with only minor gaps for an orchestration skill.	4 / 5
Workflow Clarity	Clear sequenced phases (Coordination Workflow, Plan Approval Gate, Finalization Gate) with explicit validation checkpoints, AC/DoD checklists, and feedback loops ('If verification is blocked, do not set Done; escalate').	5 / 5
Progressive Disclosure	Well-sectioned internally but monolithic — no bundle files exist and all content (including the lengthy Sub-Agent Brief Template and Common Agent Mistakes) is inlined in one ~170-line SKILL.md rather than split into one-level-deep references.	3 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that clearly states capabilities, gives concrete natural-language triggers, and answers both 'what' and 'when' explicitly. No padding or vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — orchestrate planning/implementation/finalization, manage dependencies, manage overlapping code areas, and review/approve sub-agent plans — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what (technical project management / orchestration of Backlog.md workstreams) and when ('Use only when the user explicitly asks Codex to take over...'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides natural user phrases in quotes ('act as TPM', 'coordinate these tasks', 'delegate to sub-agents', 'take over ... tasks') that a user would actually say, with synonym variation.	5 / 5
Distinctiveness Conflict Risk	Narrow niche — Backlog.md task coordination via sub-agents triggered only by explicit delegation intent — with minimal overlap risk against other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: MrLesk/Backlog.md
Path: .codex/skills/backlog-technical-project-manager/SKILL.md
Commit: 3c7fde6

Reviewed: ~5 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.