plan-pipeline-ceo-review

To validate a feature request before implementation, use an explicit product thinking gate to challenge the literal request and surface the real job-to-be-done. This process clarifies the optimal scope and aligns the brief with true product goals.

Scope management in a CEO review is a pre-implementation gate that evaluates feature requests against true product goals. It uses scope expansion, hold, or reduction modes to reveal the optimal product path and surface hidden risks.

Run the plan pipeline review by applying the provided prompt template to the feature brief. It requires explicit mode selection to output a structured plan that clarifies risks, alternatives, and a recommended execution path.

You need a pre-implementation gate when a roadmap item moves towards coding. It challenges the literal request to ensure the feature aligns with the true product goals before committing development resources.

Yes, the feature request review supports scope reduction alongside scope expansion and hold scope modes. This allows you to adapt the planning process and surface the real job-to-be-done regardless of the initial brief size.

Literal feature requests specify exact solutions, while true product goals address the underlying job-to-be-done. A pre-implementation gate challenges the literal request to reveal the optimal product scope and mitigate misaligned execution risks.