Review and Approve Drafts

Opheleon drafts planning overlays for you, but the final decision stays with your team.

When an overlay draft is ready for review, you can:

• Approve it and move forward.
• Request changes with feedback, and Opheleon revises the draft.
• Reject the draft and rerun the stage.

You don’t edit the draft yourself — you describe what should change, and Opheleon makes the corrections.

Opheleon also pauses earlier, before drafting, to ask clarifying questions when scope is unresolved. Answering those questions is part of keeping the overlay grounded — see Human Review Gates.

What to check

When reviewing a draft, look for:

• Incorrect assumptions.
• Missing constraints.
• Product behavior that does not match the intended scope.
• Technical decisions that need more context.
• Areas where the draft is too vague to act on.

Why approval matters

The PRD overlay becomes context for the Tech Approach overlay, and the Tech Approach overlay becomes the basis for implementation tasks. A weak PRD overlay leads to a weak technical approach, which leads to weak tasks.

Approve a draft only when it is strong enough for the next stage to build on. When you reject an overlay, Opheleon redrafts it with your feedback rather than asking you to fix it by hand. When a draft is not ready, tell the agent what needs to change before continuing.