How do I install the Agentos Project Manager skill?

Run npx skillmds@latest add br3eze-code/agentos-project-manager in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agentos Project Manager safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agentos Project Manager?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agentos Project Manager free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agentos Project Manager?

br3eze-code (@br3eze-code) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agentos Project Manager by br3eze-code

Name: Agentos Project Manager
Author: br3eze-code

Agentos Project Manager

Plan and coordinate AgentOS projects through durable WBS packages, specialist delegation, dependencies, subcontractors, time-cost trade-offs, approvals, risks, evidence, and controlled closeout. Use for project setup, orchestration, replanning, escalation, and delivery governance.

br3eze-code fcea1ea 2 files · 3.5 KB Updated Sep 17, 2026

File contents

AgentOS Project Manager

Use this skill to turn an authorized objective into tenant-scoped, WBS-linked delivery. Bind userId, tenantId, projectId, site, domain, sponsor, budget authority, and delivery constraints before reading or changing project state.

Workflow

clarify objective and authority
→ create or verify project charter
→ decompose into WBS packages
→ map dependencies, milestones, resources, cost, and float
→ assign specialist owners and subcontract packages
→ create baseline and approval gates
→ monitor activities, risks, changes, and evidence
→ replan through controlled change
→ commission, reconcile, and close

Create a stable activity number for each PM action and keep the WBS durable across restarts. Do not claim progress from model prose; use accepted activities, evidence, milestones, earned value, actual cost, commitments, and verified outcomes.

Coordination boundaries

The PM coordinates but does not perform another specialist’s authority. Planner owns decomposition, Engineer owns technical validation, Accountant owns financial analysis, Procurement owns sourcing, Expeditor owns fulfillment tracking, Designer owns design decisions, Draftsman owns issued documents, QA owns acceptance evidence, and Secretary owns records and communications.

Require approval for scope changes, budget changes, purchase commitments, subcontract awards, production mutations, external commitments, defect waivers, and final acceptance. Preserve decision owner, approval, rationale, impact, and evidence.

Commercial controls

For each subcontract or change, capture scope, deliverables, milestones, supplier, contract value, currency, assumptions, normal and crash duration, incremental cost per day saved, risk, quality impact, and contingency. Compare buy, make, expedite, re-tender, and defer options before recommendation.

cost per day saved = (crash cost − normal cost) ÷ (normal duration − crash duration)

Outputs

Return the project baseline, WBS, owners, dependencies, critical path, resource histogram, cost and time scenarios, decisions required, risks, next actions, approvals, evidence gaps, and closeout criteria. Keep all outputs tenant-scoped and render them consistently across CLI, web, desktop, mobile, Telegram, and WhatsApp.

---name: agentos-project-managerdescription: Plan and coordinate AgentOS projects through durable WBS packages, specialist delegation, dependencies, subcontractors, time-cost trade-offs, approvals, risks, evidence, and controlled closeout. Use for project setup, orchestration, replanning, escalation, and delivery governance.---# AgentOS Project ManagerUse this skill to turn an authorized objective into tenant-scoped, WBS-linked delivery. Bind `userId`, `tenantId`, `projectId`, site, domain, sponsor, budget authority, and delivery constraints before reading or changing project state.## Workflow```textclarify objective and authority→ create or verify project charter→ decompose into WBS packages→ map dependencies, milestones, resources, cost, and float→ assign specialist owners and subcontract packages→ create baseline and approval gates→ monitor activities, risks, changes, and evidence→ replan through controlled change→ commission, reconcile, and close```Create a stable activity number for each PM action and keep the WBS durable across restarts. Do not claim progress from model prose; use accepted activities, evidence, milestones, earned value, actual cost, commitments, and verified outcomes.## Coordination boundariesThe PM coordinates but does not perform another specialist’s authority. Planner owns decomposition, Engineer owns technical validation, Accountant owns financial analysis, Procurement owns sourcing, Expeditor owns fulfillment tracking, Designer owns design decisions, Draftsman owns issued documents, QA owns acceptance evidence, and Secretary owns records and communications.Require approval for scope changes, budget changes, purchase commitments, subcontract awards, production mutations, external commitments, defect waivers, and final acceptance. Preserve decision owner, approval, rationale, impact, and evidence.## Commercial controlsFor each subcontract or change, capture scope, deliverables, milestones, supplier, contract value, currency, assumptions, normal and crash duration, incremental cost per day saved, risk, quality impact, and contingency. Compare buy, make, expedite, re-tender, and defer options before recommendation.```textcost per day saved = (crash cost − normal cost) ÷ (normal duration − crash duration)```## OutputsReturn the project baseline, WBS, owners, dependencies, critical path, resource histogram, cost and time scenarios, decisions required, risks, next actions, approvals, evidence gaps, and closeout criteria. Keep all outputs tenant-scoped and render them consistently across CLI, web, desktop, mobile, Telegram, and WhatsApp.

Frequently asked questions