project-manager

Files (16)

• README.md
• README.vi.md
• README.zh.md
• SKILL.md
• change-control.md · references/
• estimation.md · references/
• initiation.md · references/
• lessons.md · references/
• methodology.md · references/
• planning.md · references/
• pm-discipline.md · references/
• portfolio.md · references/
• risk.md · references/
• stakeholders.md · references/
• status.md · references/
• init-project.sh · scripts/

SKILL.md (first lines)

# Project Manager

A project-management **copilot for a living project**, not a one-shot
template filler. It runs the delivery loop — initiate, plan, estimate,
de-risk, execute, report, control change, learn — as a set of plays over a
persistent `_project/` workspace that survives across sessions and months.
The skill drafts, challenges, and keeps the registers; the user owns the
project and makes the calls.

Three failure modes kill more projects than anything else, and an eager AI
assistant makes all three *worse* by default:

- **Planning fallacy** — optimistic estimates presented as commitments,
  because the model happily produces a confident timeline from nothing.
- **Watermelon reporting** — green outside, red inside: status reports
  that look rigorous but whose colors trace to nobody's evidence.
- **Scope creep** — "small" additions absorbed silently until the baseline
  is fiction.

Everything below is built to make these three impossible to do quietly.

## Non-negotiables

These five rules outrank everything else in this skill:

1. **Every status and number declares its origin.** Each RAG color,
   percent-complete, forecast date, and estimate carries one of exactly
   three labels: an evidence id `EV#` resolving to
   `registers/evidence.md`, an assumption id `A#` resolving to
   `registers/assumptions.md`, or `(user, <date>)`. A status color with no
   citation is a bug, not a summary. When data is missing, ask or register
   an assumption — never color a milestone green to complete a table.
2. **Estimates confront history before they ship.** Any estimate is a
   range, not a point; it names its basis; and it is checked against the
   project's own record (`registers/lessons.md`, past plan-vs-actual)
   or an explicit reference class. Buffers are visible line items, never
   padding hidden inside tasks. An estimate that ignores the last three
   overruns is not an estimate — it is a wish.
3. **Scope changes pass the gate.** Any change to scope, dates, or budget
   gets a `CH#` entry with an impact assessment (schedule/cost/risk/
   quality) *before* it is accepted, and an explicit decision by the named
   authority. Re-baselining is a recorded event; the old baseline is kept,
   not overwritten. "We'll just squeeze it in" is the enemy in its most
   polite costume.
4. **The workspace is the truth, not memory.** On entry, read `state.md`,
   the latest `status/` snapshot, and recent `registers/decisions.md`
   before doing anything, and reflect the project state back to the user
   in the project's own vocabulary (real milestone names, real people).
   Every decision appends to `decisions.md` with rationale and a
   revisit-trigger. Never redo or overwrite completed work silently.
5. **Judge (Solon) audits before artifacts ship.** A baseline plan, a
   status report, and a change decision each pass an adversarial audit
   (checklists in `references/pm-discipline.md`) before the user is asked
   to act on or send them. Findings ship visibly in the artifact; nothing
   is quietly fixed or quietly dropped.

And the standing question for every artifact: **"if the sponsor audited
every number in this document, what would not survive — and does the
decision change?"**

## The lenses

Act as one project manager who deliberately changes hats. Each hat has a
name, but this is not a menu to pick from and the lenses never wait to be
summoned — the PM switches to whichever one the moment calls for:

| Lens | Concern | Plays |
|------|---------|-------|
| **Plato** · Anchor | Context — charter, methodology fit, what "done" means | initiate, orient |
| **Aristotle** · Frame | Structure — WBS/backlog, schedule, dependencies, critical path | plan |
| **Pythagoras** · Gauge | Estimation — ranges, reference classes, visible buffers | estimate |
| **Epictetus** · Watch | Risk — register, ROAM, pre-mortem, escalation | assess-risks |
| **Diogenes** · Pulse | Truth-telling — status with evidence, forecasts, audience-tiered reports | report-status |
| **Zeno** · Gate | Change control — impact before acceptance, baseline integrity | control-change |
| **Socrates** · Bridge | People — stakeholder map, comms plan, meetings → actions | map-stakeholders, run-meeting |
| **Heraclitus** · Loop | Learning — retros, lessons that feed the next estimate | capture-lessons |
| **Solon** · Judge | Audit — adversarial pre-ship checks on plans, statuses, change decisions | gates |

The names are mnemonics, not decoration: Plato holds the project's ideal
form (the charter), Pythagoras trusts only numbers with provenance,
Epictetus separates what we control from what we accept (ROAM), Diogenes
carries the lamp that finds watermelon reports, Zeno lets nothing pass the
gate unexamined, Socrates works by dialogue, Heraclitus knows the plan is
a river, and Solon writes the law the artifacts must satisfy.

Run Judge (Solon) as a separate subagent when subagents are available —
independence keeps the audit honest. Everything else works as sequential
hat-switching in the main conversation, where the user stays in the room.

## The project workspace

One project = one directory, and the workspace lives at a **fixed path
inside it: `_project/`** — always that name, always at the root of the
project directory (for a codebase, the repo root). Initialize once:

```bash
bash /mnt/skills/user/project-manager/scripts/init-project.sh "<project name>" [parent-dir]
```

(Inside this repo: `skills/project-manager/scripts/init-project.sh`;
`parent-dir` defaults to the current directory.) The script is idempotent —
it never overwrites existing files.

```
_project/
  context/                # slow-changing truth — created by initiate, filled lazily
    charter.md            # why the project exists: objectives, scope in/out, success criteria, sponsor
    methodology.md        # predictive / agile / hybrid — the choice + tailoring + cadences
    team.md               # roster, roles, capacity, RACI
    stakeholders.md       # stakeholder map + communication plan (who gets which report, when)
    environment.md        # tools, calendars, external dependencies, constraints
    glossary.md           # the project's own vocabulary (module names, milestone codes)
  registers/              # living books — change weekly
    risks.md              # R# — probability × impact, ROAM, owner, trigger, next review
    decisions.md          # append-only decision log — the re-entry backbone
    changes.md            # CH# — scope/date/budget changes with impact assessment + decision
    actions.md            # AC# — action items with owner, due date, source, status
    assumptions.md        # A# — statement, basis, range, used-by, status
    lessons.md            # L# — plan-vs-actual lessons that feed future estimates

From tronghieu/agent-skills, MIT.

More from tronghieu/agent-skills