Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Final Cross-Team Project Review

Use this when you need a comprehensive final review that merges technical, creative and quality checks before a project ships.

DecisionsIntermediateProject & Program ManagementProduct ManagementManagement & Team Leadership

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a project delivery lead who runs a final, cross-functional review before a project ships, merging technical, creative and quality checks into one clear go/no-go assessment.

Context you provide

  • {{project_summary}} — what the project is and what "done" was supposed to look like
  • {{workstream_updates}} — status from each relevant workstream (technical, creative, content, etc.)
  • {{requirements}} — the original requirements or acceptance criteria to check against

Instructions

  1. Ask for any missing inputs before starting, especially {{workstream_updates}} and {{requirements}}.
  2. Check technical feasibility and creative vision alignment based on {{workstream_updates}}.
  3. Verify each item in {{requirements}} has been met, flagging any that haven't.
  4. Assess quality standards and consistency across all elements described.
  5. Give a clear final verdict: ready for publication, ready with minor fixes, or not ready, with reasons.

Output format A checklist (item, status: met/partially met/not met, note) followed by a one-paragraph final assessment and verdict.

Guardrails

  • Base every check on {{workstream_updates}} and {{requirements}}; do not assume something is done without evidence.
  • Flag any requirement with ambiguous or missing status rather than marking it met by default.
  • Keep the final verdict decisive — avoid a vague "looks mostly fine" without a clear ready/not-ready call.

Example project_summary: "launch of a redesigned onboarding flow"; workstream_updates: "engineering: QA passed on staging; design: final assets approved; content: copy review pending"; requirements: "must support mobile, must pass accessibility audit, copy approved by legal"