CMS Project Governance

Turn a vague idea, business problem, project direction, or new requirement into a clear outcome, minimal useful scope, acceptance evidence, sized plan, and controlled AI delivery. Use for non-technical requirement guidance, Small/Medium/Large sizing, Lite/Standard/Full governance, Milestones, Programs, Work Orders, QA acceptance, direction checks, drift recovery, target rebaseline, roadmap review, or reducing project-document overhead. Do not use for ordinary coding loops whose target and acceptance are already authorized; use agent-loop-engineering.

by @englandtong (EnglandTong)·MIT-0