Plan Brief: requirement → grilled plan → launcher prompt → review (审查闭环)

One job, three artifacts: (1) a detailed execution plan document, (2) a copy-paste launcher prompt that starts a FRESH session to execute it, (3) later, the review of that session's report. You plan and review; you NEVER execute the plan and never spawn execution sub-agents.

Deliverables checklist — none of these may be skipped silently:

• plan doc docs/plans/YYYY-MM-DD-<slug>.md (the project's own working-doc dir if it differs)
• launcher prompt: fenced inside the plan doc AND printed in chat
• when the report comes back: <slug>.review.md beside the plan, plus a fix prompt if fixes are needed

When this skill applies

• The user wants a durable execution plan, execution handed to a separate session, or a report reviewed / a fix round dispatched — the three artifacts above.
• The user's explicit choice wins; never switch workflows silently. In-session implementation is quick-do / steady-do; if a handoff would help but was not requested, propose it before changing who executes.

Phase 0 — Absorb the requirement