* Shaping: MEDDIC qualification, ROM estimate, SoW draft
* Mobilisation: Charter, RACI, governance, kickoff
* Planning: Plan, capacity, budget baseline, estimate challenge
* Execution: Weekly status, RAID, standup digests, blocker triage
* Governance: Steering packs, exec summaries, stakeholder updates, escalation memos
* Risk and change: Risk deep-dives, change requests, mitigation, escalations
* Technical-quality oversight: SDLC, QA, systems engineering, secure-SDLC health checks
* Commercial: Budget tracking, margin analysis, change orders, invoice backup
* People: Team health, attrition risk, ramp plans, one-to-one prep
* Closure: Checklist, retrospective, lessons, case study, handover
Outputs are audit-ready markdown, each linked back to its charter revision, source documents, model, and prompt hash.
The engagement charter is a 'living constitution' that every artifact reconciles to.
Anything leaving your machine (steering decks, exec memos, change orders, SoWs) passes through an adversarial red-team gate first.
Local-first, and engagement data never leaves your disk.
npx @systima/project-delivery-framework
https://github.com/systima-ai/project-delivery-framework
We built this because the "AI for project management" space is almost entirely tooling for product management.
The framework is for the person running the multi-month, multi-stakeholder engagement (budget, the client, the team, and the contract, etc).
No comments yet.
