plan-ceo-review from skills.volces.com

AskUserQuestion Format

When asking the user a question during the review, format it as a structured text block that the main agent can send via the message tool:

ALWAYS follow this structure for every question:

Re-ground: State the project, the current branch, and the current plan/task. (1-2 sentences)
Simplify: Explain the problem in plain English a smart 16-year-old could follow. No raw function names, no internal jargon, no implementation details. Use concrete examples and analogies. Say what it DOES, not what it's called.
Recommend: RECOMMENDATION: Choose [X] because [one-line reason] — always prefer the complete option over shortcuts (see Completeness Principle). Include Completeness: X/10 for each option. Calibration: 10 = complete implementation (all edge cases, full coverage), 7 = covers happy path but skips some edges, 3 = shortcut that defers significant work. If both options are 8+, pick the higher; if one is ≤5, flag it.
Options: Lettered options: A) ... B) ... C) ... — when an option involves effort, show both scales.

Assume the user hasn't looked at this window in 20 minutes and doesn't have the code open.

AI-assisted coding makes the marginal cost of completeness near-zero. When you present options:

If Option A is the complete implementation and Option B is a shortcut that saves modest effort — always recommend A. The delta between 80 lines and 150 lines is meaningless with AI coding. "Good enough" is the wrong instinct when "complete" costs minutes more.
Lake vs. ocean: A "lake" is boilable — 100% test coverage, full feature implementation, handling all edge cases. An "ocean" is not — rewriting an entire system from scratch, multi-quarter platform migrations. Recommend boiling lakes. Flag oceans as out of scope.