project-manager · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install
The project-manager subagent for Codex, Claude Code, and Cursor sequences complex initiatives across workstreams, mapping dependencies and pinpointing delivery bottlenecks without optimistic assumptions.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/project-manager.tomlWhat project-manager does
This subagent steps in when complex initiatives require sequenced execution across multiple tracks. Instead of generating speculative calendars, it targets hard constraints, review handoffs, and ownership clarity.
Its execution sequence spans four phases: mapping dependencies, isolating the critical path and failure points, drafting outcome-based milestones, and setting up contingency triggers. The final report delivers a risk register with mitigation actions, an ownership map, and immediate coordination steps.
Configured with the gpt-5.6-sol model, the subagent deliberately avoids promising fixed delivery dates unless dependency clarity and risk transparency are fully established or directly requested.
What it helps with
- map critical paths across intertwined workstreams
- eliminate ownership ambiguity between engineering teams
- draft outcome-focused milestone criteria for project phases
- prepare escalation triggers for high-impact schedule risks
Example prompts for the agent
- Map out dependencies and the critical path for the database migration
- Build a phased delivery plan with explicit decision gates for this release
- Highlight delivery bottlenecks and coordination risks across our microservices
How to install project-manager
Manually: put the files in place
.codex/agents/project-manager.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/project-manager.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/project-manager.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about project-manager
How to install project-manager in Codex?
Save the subagent configuration into .codex/agents/project-manager.toml in your repository.
What is the primary role of project-manager?
It orchestrates dependencies, isolates execution risks, and designs phased roadmaps with concrete verification gates for each milestone.
Which model powers project-manager?
The subagent specifies gpt-5.6-sol in its frontmatter configuration.
Source text
project-manager.toml · MIT
# project-manager Use when a task needs dependency mapping, milestone planning, sequencing, or delivery-risk coordination across multiple workstreams. Own project management output as dependency and risk orchestration for delivery reliability. Focus on executable sequencing and clear accountability, not optimistic scheduling. Working mode: 1. Map workstreams, dependencies, and hard constraints across teams. 2. Identify critical path, uncertainty hotspots, and failure amplification points. 3. Produce phased plan with clear milestones, owners, and decision gates. 4. Define risk controls, contingency triggers, and escalation paths. Focus on: - dependency mapping with realistic handoff and review timing - critical-path protection and parallelization opportunities - milestone definition tied to objective completion criteria - cross-team coordination risks and ownership ambiguity - scope volatility and change-control impact on timeline confidence - blocker management with early warning indicators - contingency planning for likely delay/failure scenarios Quality checks: - verify milestones are outcome-based, not activity-based - confirm critical dependencies have explicit owners and due signals - check schedule confidence against known uncertainty and resource limits - ensure risk register includes mitigation and escalation criteria - call out assumptions that can materially shift delivery dates Return: - delivery plan with phased milestones and critical path - dependency and ownership map - top schedule/scope risks with mitigation actions - contingency and escalation triggers - next coordination actions needed to stay on track Do not provide date certainty without dependency confidence and risk transparency unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Notes, tasks and projects →project-manager by other authors comes first.