cody-hutson

artifact-generator

Produces new or updated project artifacts — triggered by user request, PPM Agent gap detection, or phase gate requirements. Stages all output in 08-Generated/ with metadata for user review before promotion. Triggers: "draft a", "create a", "generate a", "I need a", "prepare a", "what artifacts do I need", "spin up a", "I need the [artifact]."

comms-writer

The voice of the PMO — produces audience-calibrated, ready-to-send communications. Covers email, Teams, Confluence, exec briefs, meeting agendas, escalation drafts, recaps, and status updates. Use when drafting any stakeholder communication. Triggers: "draft an update for [audience]", "write the exec brief", "prepare the agenda", "send the escalation email", "write the recap", "put together a message", "write a Teams post."

daily-status

Generates Teams-ready AM and PM daily status updates from carry-forward trackers and recent transcripts. Uses the project's Daily Status Update Framework. Triggers: "generate the AM update", "daily status", "morning update", "afternoon update", "PM update", "EOD update", "prep the daily connect", "I just came out of testing — status post."

delivery-engine

Operational backbone for backlog health through release readiness. Modes: Backlog scan · Ticket insight · DoR gate · Sprint planning · Execution control · DoD gate · RAID updates. Use for sprint planning, backlog review, quality gates, or velocity tracking across Agile and Waterfall governance. Triggers: "run DoR on this", "run DoD on this", "check this backlog", "plan the sprint", "velocity check", "is this release ready", "update the RAID log."

file-router

Classifies, routes, and triggers processing for new files arriving in the PMO workspace. Uses three-layer classification (content analysis, project identification, filename patterns) with confidence thresholds. Triggers: "route this", "file this", "where does this go", "classify this", "I have a new transcript", "I just uploaded this", "what folder does this go in."

pmo-process-designer

Converts business context into structured, traceable requirements and process documentation. Modes: Requirements definition · Workflow documentation · Gap analysis · Traceability matrix · Compliance mapping. Use when uploading business requirements, FDDs, or Jira exports. Triggers: "document this process", "build the requirements", "build the traceability matrix", "write the FRD", "trace from requirement to Jira", "what's the gap."

pmo-technical-analyst

Reviews technical artifacts with senior TPM judgment — surfaces risks not obvious from the document alone. Modes: FDD review · Integration risk · Architecture assessment · Dependency identification · Feasibility feedback. Use when uploading FDDs, integration specs, or architecture documents. Triggers: "review this FDD", "what are the technical risks", "check this integration design", "architecture review", "feasibility check", "what's missing from this spec."

ppm-agent

The strategic brain of the PMO — reads any project artifact and pushes every actionable item toward resolution. Use when uploading transcripts, asking about project status, needing decisions framed, or requesting risk assessment. Triggers: "review this", "what's the state of [project]", "process this transcript", "triage this", "what needs my attention", "what actions came out of this", "what needs to surface."

project-initiator

Manages the full project lifecycle — scaffolding new projects and closing completed ones. Modes: Initiation (creates folder structure, populates PROJECT.md, updates PORTFOLIO.md) · Closure (finalizes trackers, produces closure summary, archives). Triggers: "new project", "start project", "kick off [project]", "close project", "archive project", "project closure", "wrap up [project]."

tracker-manager

Generic update engine for all operational trackers in 04-PMO-Operations/. Receives TRACKER_UPDATE instructions, validates against schemas, and produces a consolidated change summary for user approval before writing. Triggers: "update the trackers", "sync the trackers", "apply these changes", "process tracker updates", "consolidate updates", "consolidate tracker updates."

weekly-status-rollup

Generates a weekly executive status roll-up across all active projects. Covers project health, key risks, decisions made/pending, and upcoming milestones. Writes back updated health indicators to PORTFOLIO.md. Triggers: "weekly roll-up", "weekly status", "SteerCo prep", "SteerCo update", "executive status", "portfolio summary", "portfolio health", "cross-project status."

build-reviewer

Conducts final production-readiness review of any governed document pack — Copilot Builder Agent, PMO platform, or generic — using the shared review discipline (see `core/disciplines/review-discipline-principles.md`). Domain-specific dimensions loaded from pluggable dimension packs under `references/dimension-packs/` (3 initial packs: copilot-builder, pmo-platform, generic). Produces a structured findings register with severity, affected documents, root cause, evidence, resolution, and reversibility tier per finding — consumed by implementation-planner downstream. Use when the user wants a final production-readiness review of a document pack, including: "review the copilot builder files", "audit the pmo platform", "review this document pack", "find gaps in the builder doc pack".

implementation-planner

Converts build-reviewer findings registers into sequenced, minimal-change remediation implementation plans for any governed document pack — Copilot Builder Agent, PMO platform, or generic. Domain-specific planning context loaded from pluggable domain packs under `references/domain-packs/`. Applies the Minimal-Change Remediation Bias and classifies every confirmed finding to one of 8 remediation types (RT-1 text correction through RT-8 accepted residual). Produces implementation records (RI-NNN) as Edit-ready specs and Bash scripts directly consumable by Claude Code's native tools per the reference workflow in `release/references/how-to/implementation-execution-pattern.md`. Use when the user has a build-reviewer findings register ready for planning, needs remediation sequencing, or wants to plan the fixes before execution.

pmo-skill-editor

Edit, audit, and regression-test any skill in the PMO Agent Suite. Modes: Targeted edit · Full audit · Regression check · Remediation apply. Maintains skill definitions with full awareness of cross-skill contracts and architecture. Triggers: "edit this skill", "modify this skill", "change this skill", "check for regressions", "audit this skill", "apply these fixes", "what breaks if I change this."

pmo-skill-refiner-selftest-canary

Smoke test for the pmo-skill-refiner factory — produced via the refiner's Create-New workflow during an AC demonstration. Reports the count of skill directories currently present in `release/skills/` and flags any that are missing from `deploy.sh` SKILL_LIST. Report-only (no decision-class outputs, no recommendations, no actions). Permanent fixture per ADR-04 (Stage 5 design for ) — functions as an always-on smoke test that detects factory regressions. Use when the user wants to check skill-roster consistency ("check the skill roster", "count tracked skills", "audit skill deployment drift", "verify skills/ folder matches deploy.sh", "are all my skills deployed").

pmo-skill-refiner

Creates and refines PMO-platform skills by wrapping an Anthropic scaffolding skill (default: anthropic-skills:skill-creator) with a PMO refinement layer. Captures intent via Interview mode (methodology, failure modes, dependencies, reversibility, trigger evidence), delegates commodity scaffolding to the Anthropic skill, then injects PMO-platform fields into the produced SKILL.md (delivery_approach, output-contract stub, dependency-graph node, evidence- quality protocol, failure-mode discipline, Principal Standard checklist, reversibility declaration). Runs the preserved eval harness from skill-creator (variance analysis, description-trigger optimization, blind A/B comparison, cross-skill false-positive detection). For modifying EXISTING PMO skills, coordinates with pmo-skill-editor. Use when the user wants to create a new PMO skill or iterate on an existing skill's eval/description/trigger set.

release-executor

Executes approved release plans. Modes: Execute release · Verify release · Rollback release · Close release. Creates snapshots, applies file changes, closes IMP items, updates release log, runs verification, runs automated Stage 13 close-out. Requires an approved plan with Dry-Run Record. Triggers: "execute the release", "deploy v[X.Y]", "ship v[X.Y]", "verify the release", "rollback v[X.Y]", "go live with v[X.Y]", "close the release", "finalize v[X.Y]", "stage 13 close", "run the close-out", "automated close-out".

release-planner

Plans the PMO platform release lifecycle. Modes: Backlog analysis · Release planning · Dry run. Analyzes the improvement backlog, maps dependencies, suggests release bundles, generates release plans, and produces dry-run diffs. Read-only — never modifies governance files. Triggers: "review the backlog", "plan the release", "bundle the release", "dry run", "show me the diffs", "what's in v[X.Y]."

eval-writer

Authors rigorous eval suites for AI agents, skills, and LLM systems — grounded in the 2026 eval-writing consensus (trace-driven error analysis, binary LLM judges, cross-family validation, α/κ agreement). Produces characterization, failure taxonomies, judge prompts, rubrics, and calibration protocols that harnesses (pmo-skill-refiner, CI) then execute. Two modes — Author (write from scratch) and Review (audit against the framework). First-class playbooks for per-skill evals and for pipeline stage-gate judgment content; generic fallback for arbitrary AI systems. Use whenever the user asks to write evals, audit evals, add eval coverage, calibrate a judge, build a rubric, write a judge prompt, or diagnose why a judge keeps passing broken outputs.

pmo-qa-auditor

Reviews skill outputs against the principal contributor standard. Modes: Single-output review · Cross-output coherence · Evidence audit · Guardrail compliance. Evaluates rigor, accuracy, judgment, and operational value — not formatting. Triggers: "review this output", "audit this", "QA this", "check this against the standard", "is this ready to act on", "quality check this", "is this principal-contributor quality."

prompt-builder

Builds and improves prompts of every kind — everyday Claude prompts, SKILL.md instruction bodies, skill descriptions, and agent/system prompts. Detects mode from input: critique-and-rewrite when the user pastes a draft, interview-and-build when the user describes a goal without a draft. Always does live web research on current Anthropic prompting guidance before producing output. Returns a short critique plus a copy/paste-ready prompt block. Use whenever the user asks for help writing, improving, rewriting, critiquing, sharpening, or scoping a prompt — including phrases like "help me write a prompt for…", "improve this prompt", "make this better", "what's wrong with this prompt", "rewrite this", "I need a system prompt for…", "draft a SKILL.md description for…", "write a prompt for", "sharpen this prompt", or whenever the user shares a block of text that is clearly an LLM prompt and asks for any kind of feedback or revision.

intake-desk

The conversational front door for intake — turns a half-formed idea into a well-formed, correctly-typed, correctly-placed work item logged to the work tracker. Meets you at any altitude (a single bug or a portfolio initiative), proposes the work-item type and its place in the intake hierarchy, elicits the type- and level-appropriate fields (a bug's reproduction and environment; a story's acceptance criteria and value), applies the 5-test rule live, confirms the drafted item with you, then logs it — never a scratch file. One work item per request (child candidates are noted in the body for later slicing; it does not auto-decompose). Two modes: Elicit (guided interview) and Triage-readiness check (run the 5-test against a draft you already wrote). Use when the user says "help me file this idea as an issue", "turn this into a work item", "log this idea", "what type of work item is this", "scope this idea for intake", "is this intake-ready", or "help me write up this bug/story/initiative".