Program Evaluation & Review Technique
Weighted three-point estimates with critical-path detection. Surfaces float, slack, and which task to actually unblock.
Open-source Skills, MCP servers, and APIs that let Claude and other agents reason about projects the way a senior analyst does — with PERT, Monte Carlo, Bayesian updating, TCO and the rest of the kit.
We're not selling a replacement. We're shipping the toolbox the next generation of PMO work is built on — kernel open, premium plugins where data integration warrants it, consulting where the analysis is bespoke.
An AI agent can estimate a delivery date in seconds, but it can't judge which task to unblock next. pmo.run gives PMOs and their agents the maths to do both — with every number traceable.
Each method ships as a Skill (for Claude), an MCP server (for any agent), and an HTTP API. Same kernel, three surfaces.
Weighted three-point estimates with critical-path detection. Surfaces float, slack, and which task to actually unblock.
Replaces single-point dates with distributions. p50 / p90 ship dates, sensitivity per task, and confidence intervals you can defend.
Updates prior beliefs as tickets close. Replaces the "gut feel re-baseline" with an auditable likelihood update.
License + ops + integration + training + the hidden line items. Used by SIers to defend procurement decisions.
No platform lock. Skills load into Claude. The same kernel runs as a local MCP server, or behind your gateway as an HTTP API.
# clone the open-source repo $ git clone https://github.com/lemur47/logic $ cd logic # install the skills for Claude Code $ cp -r skills/* ~/.claude/skills/ # Claude can now reason with PERT claude> what's the critical path on the Q3 plan? → skill: pmo/pert critical: A → B → D → F → G (14.2d) slack: C: 2.1d, E: 0.8d
# after cloning: install + run the server $ uv pip install -e . $ uv run python -m mcp_server.server # or wire it into any MCP client { "mcpServers": { "pmo-logic": { "command": "uv", "args": ["run", "python", "-m", "mcp_server.server"] } } } # prototype · 5 tools over stdio
The three-layer core is open source: the core logic and tools stay MIT-licensed. Paid plugins and consulting services add on top — your own proprietary layer.
| Layer | What's in it | Who it's for | License | Pricing |
|---|---|---|---|---|
| OSS Kernel | Skills, MCP servers, APIs. PERT, Monte Carlo, Bayes, EVM, TCO, queueing. | International PMO communities, individual practitioners, contributors. | MIT | free |
| PAID Plugins | Proprietary connectors: Jira Cloud, ServiceNow, SAP, MS Project, Salesforce. Industry datasets, benchmark libraries. | Systems integrators, internal platform teams. | commercial | seat / usage |
| SERVICE Strategic | Bespoke analysis, model calibration, rollout, executive briefings, training programmes. | Consulting firms, large transformation programmes. | contract | retainer |
The administrative half of the PMO role — status rollups, variance reports, schedule maintenance — will be done by agents. Our work is to give those agents the same rigorous tools your best analysts use, so the human half can move upstream into strategy.
Stop hand-rolling Monte Carlo in Excel. Drop the skill in Claude. Get the same numbers, defensible.
Plug into your client's Jira / ServiceNow / SAP. Ship licensed integrations under your brand if you need to.
Put your historical data to work with PMO logic and tools, and sharpen your firm's insight.