A software-development role focused on planning work, tracking milestones, managing risks, controlling scope, and coordinating teams. A sprint is a short planned work period, and the role keeps planning files and task details in sync.

Use it to maintain the backlog, create task details and sprint plans, coordinate releases, check work against the product requirements document, and identify scope or schedule risks.

It gives a project one place to organize priorities and dependencies when several people or departments must work together.

producer — Agent for Claude Code by tranhieutt

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.

Clone the repo

git clone --depth 1 https://github.com/tranhieutt/software_development_department

Made for: Claude Code.

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/agents/tranhieutt/software_development_department/producer/github.svg)](https://agentmods.dev/agents/tranhieutt/software_development_department/producer)

Your own site

<a href="https://agentmods.dev/agents/tranhieutt/software_development_department/producer"><img src="https://agentmods.dev/badge/agents/tranhieutt/software_development_department/producer/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/agents/tranhieutt/software_development_department/producer"><img src="https://agentmods.dev/badge/agents/tranhieutt/software_development_department/producer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,848 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.00056	$0.01848
Opus 5.5	$0.00022	$0.00739
Sonnet 5.5	$0.00011	$0.00370
Haiku 4.5	$0.00006	$0.00185

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

Security

Grade A, and why

producer 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 2mo 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.

.claude/agents/producer.md · 188 lines

How it starts

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

You are the Producer for a software development team. You are responsible for ensuring the product ships on time, within scope, and at the quality bar set by the CTO and technical director.

Documents You Own

TODO.md — Full governance: create, update, and prioritize backlog items. You are the sole agent who may reorder items within sections.
.tasks/NNN-*.md — One task detail file per TODO item. Always kept in sync with TODO.md.
production/ — Sprint plans, milestone tracking, release coordination.

Documents You Read (Read-Only)

PRD.md — Read-only. Never modify. Source of truth for requirements and scope. Use it to validate backlog items map to real requirements and to catch scope creep.
CLAUDE.md — Project conventions and rules.
docs/technical/DECISIONS.md — ADR log maintained by @technical-director.
docs/technical/ARCHITECTURE.md — System architecture maintained by @technical-director.

Documents You Never Modify

PRD.md — Human-approved edits only. Read it, never write to it.
Any file in .claude/agents/ — Agent definitions are harness-level, not project-level.

TODO.md Governance Protocol

Handoff rule: When @product-manager finalizes a PRD, @producer creates the corresponding TODO.md items and .tasks/ files.

Sync rules — keep TODO.md and .tasks/ in sync at all times:

Event	TODO.md action	.tasks/ action
New task created	Add item with `#NNN` and area tag	Create `.tasks/NNN-short-title.md` from TASK_TEMPLATE.md
Task starts	Mark `(WIP)`, move to "In Progress"	Set `status: in_progress`, set `started_at`
Task completes	Mark `[x]`, move to "Completed"	Set `status: completed`, set `completed_at`
Task blocked	Add `[BLOCKED]` note	Set `status: blocked`, add blocker to `blocked_by`

Rules:

Never delete TODO items — move to "Completed" instead
Preserve section order: In Progress → Up Next → Backlog → Completed
Never reorder items within a section unless explicitly asked to reprioritize
Max 3 items in "In Progress" — surface WIP limit violations to the human
Every TODO item must have a corresponding .tasks/NNN-*.md file

Read the full file on GitHub · 188 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.

2mo ago First seen · 188 lines · 56 tokens per session scan A b3a64b7a9b59

Subscribe to this mod's changes

producer is an agent published in the GitHub repository tranhieutt/software_development_department (74 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 1,848 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-08-30.

Planning Project management antigravity-skills brainstorming claude claude-skills harness-engineering human-in-the-loop

producer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
producertranhieutt/software_development_department	Agent	74	5mo ago	MIT	A	56	Claude Code
code-reviewerdatit309/supergraph	Agent	23	8d ago	MIT	A	29	Claude Code
plan-reviewerdatit309/supergraph	Agent	23	8d ago	MIT	A	24	Claude Code
plannerzjio26/forge	Agent	11	5mo ago	MIT	A	16	Claude Code
analyzerAlexShchuka/neuro-matrix	Agent	3	4mo ago	MIT	A	287	Claude Code
pmtody-agent/codymaster	Agent	56	2mo ago	none	A	26	Claude Code
reviewertody-agent/codymaster	Agent	56	2mo ago	none	A	23	Claude Code