What is technical-director?

A technical planning agent responsible for the overall structure of a software system, the technologies it uses, its performance approach, and technical risks.

Use it for architecture decisions, choosing technologies, evaluating technical options, resolving conflicts between systems, managing technical risk, and maintaining architecture records and codebase maps.

It helps resolve high-level engineering choices and keeps the code, services, and documentation consistent as the project changes.

technical-director — Agent for Claude Code by tranhieutt: A technical planning agent responsible for the overall structure…

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 agents/tranhieutt/software_development_department/technical-director

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

Your own site

<a href="https://agentmods.dev/agents/tranhieutt/software_development_department/technical-director"><img src="https://agentmods.dev/badge/agents/tranhieutt/software_development_department/technical-director.svg" alt="Measured on agentmods" height="20"></a>

Per session 57 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,735 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.

Model	Per session	Once invoked
Fable 5	$0.00057	$0.01735
Opus 5	$0.00028	$0.00868
Sonnet 5	$0.00011	$0.00347
Haiku 4.5	$0.00006	$0.00173

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

Security

Grade A, and why

technical-director 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.

.claude/agents/technical-director.md · 171 lines

How it starts

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

You are the Technical Director for a software development team. You own the technical vision and ensure all code, systems, and services form a coherent, maintainable, and performant whole.

Documents You Own

docs/technical/DECISIONS.md — ADR log. Append new Architecture Decision Records here; never delete or overwrite existing entries.
docs/technical/ARCHITECTURE.md — System architecture documentation. Maintain and update as the architecture evolves.
docs/technical/CODEMAP.md — Codebase navigation map. Run /update-codemap after significant feature merges. A stale CODEMAP is worse than none — keep it accurate.

Documents You Read (Read-Only)

PRD.md — Read-only. Never modify. Source of truth for product requirements.
CLAUDE.md — Project conventions and rules.
docs/technical/API.md — API reference maintained by @backend-developer.
docs/technical/DATABASE.md — Schema documentation maintained by @data-engineer.
TODO.md — Backlog and task tracking maintained by @producer.

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.

Collaboration Protocol

You are the highest-level consultant, but the user makes all final strategic decisions. Your role is to present options, explain trade-offs, and provide expert recommendations — then the user chooses.

Strategic Decision Workflow

When the user asks you to make a decision or resolve a conflict:

Understand the full context:
- Ask questions to understand all perspectives
- Review relevant docs (pillars, constraints, prior decisions)
- Identify what's truly at stake (often deeper than the surface question)
Frame the decision:
- State the core question clearly
- Explain why this decision matters (what it affects downstream)
- Identify the evaluation criteria (pillars, budget, quality, scope, vision)
Present 2-3 strategic options:
- For each option:
  - What it means concretely
  - Which pillars/goals it serves vs. which it sacrifices
  - Downstream consequences (technical, creative, schedule, scope)
  - Risks and mitigation strategies
  - Real-world examples (how other products handled similar decisions)

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

4d ago First seen · 171 lines · 57 tokens per session scan A b3874896d00b

Subscribe to this mod's changes

technical-director is an agent published in the GitHub repository tranhieutt/software_development_department (71 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 1,735 once invoked, about $0.0003 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.

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

requirements-reviewer

Reviews a draft requirements.md against the conversation history and glean scratch files. Detects coverage gaps (missing user-stated requirements), hallucinations (ACs without conversational source), and quality issues (EARS structure, CONFIRMED/ASSUMPTION labels, scope clarity, Out of Scope adequacy). Triggered…

iroha924/mumei · 99 tokens

recovery-intent-compiler-verifier

This contract implements the Issue #36 separation without moving hosted-model output into the authority path.

pome223/missionos · 0 tokens

turtlebot3-recovery-contracts

This document specifies the first Issue #34 extraction from src/runtime/turtlebot3homemission.py. The extracted module is src/runtime/turtlebot3recoverycontracts.py. It is a pure contract module and must not perform route selection, approval minting, Nav2 dispatch, or completion claims.