pmo-intakelisted

# pmo-intake ## Purpose Convert source material into confirmed requirements, assumptions, questions, scope, and mode recommendations. ## Trigger Use for new source review, requirement extraction, gap analysis, scope clarification, or source conflict triage. ## Required Inputs `PROJECT.md`, relevant `source/**`, and any user-stated goal. Read only the context set allowed by `CONTEXT-ROUTER.md` and `pmo-config/context-map.json`. ## Allowed Context Default to `PROJECT.md` plus the specific source files needed. Do not bulk-load archived skills or every source file unless the task is an impact analysis or conflict review. ## Onboarding Before any intake work on a project whose `PROJECT.md` does not yet declare both `Execution path:` and `Default mode:`, ask the user directly. Do not infer, detect, or silently default either answer — `docs/concepts/execution-paths.md` and `DEC-011` both treat a system claiming to have "detected" either answer, rather than stating what the user declared, as a fabricated evidence claim. This mirrors `axiom init`'s interactive wizard (`cli/axiom.mjs`) for the skill-based flow, which never invokes that CLI. Ask, in the user's own words if useful, but cover both: 1. **Who builds this work** — a developer or vendor after a verified handoff (`development_handoff`), or an AI execution agent under a governed contract, verified afterward against git ground truth (`governed_ai_execution`)? See `docs/concepts/execution-paths.md`. 2. **How stric