Plan Ceo Review

Applied Rubric

• require a clear why-now argument, not only a complete artifact
• require explicit non-goals and a core success state
• prefer narrowing to the highest-value user path when value is uncertain
• treat observability, rollout risk, and support burden as part of scope cost
• if value is weak even after narrowing, return hold_scope or fail

Verdict Contract

Return exactly one of:

• pass
• conditional_pass
• scope_reduction
• hold_scope
• fail

Output Shape

planCeoReview:
  artifact: "PLAN.md"
  verdict: "scope_reduction"
  summary: "Current phase list is broader than the near-term value case."
  requiredChanges:
    - "split admin analytics into a later slice"
  assumptions:
    - "Current run targets only core user path"
  blockers: []

Rules

• prefer scope reduction over speculative expansion
• do not treat completeness as value
• if value is weak or timing is poor, use hold_scope or fail
• if details are missing but not critical, use conditional_pass

References

• .claude/skills/product-orchestrator/SKILL.md
• .claude/skills/moonshot-plan-writer/SKILL.md