plan-pipeline-ceo-review

Insert a product gate between receiving a request and coding to ensure product thinking precedes implementation. This structured review process uses a prompt template to surface the real product objective and shape a stronger plan before development begins.

Use the SCOPE EXPANSION mode during your product gate review to clarify fuzzy briefs and surface the true product objective. This approach adapts the plan by expanding the scope to ensure alignment before any coding starts.

Apply the HOLD SCOPE mode to review fixed briefs while maintaining the original boundaries. This mode enforces a decision gate to ensure the specific product objective remains clear and aligned before you proceed to implementation.

Use the SCOPE REDUCTION mode to narrow down shifting briefs during your product gate review. This mode provides a structured decision process to trim unnecessary elements and solidify a focused product plan before coding.

Use a decision gate whenever you receive a significant feature request, especially when the brief is specific or ambiguous. It forces early clarification and alignment, ensuring product thinking happens first to prevent premature coding.

No specific tool is required to run the product decision gate. The process relies on a structured prompt template and a clear decision framework that you can apply independently to shape your product plan before coding.