Kickoff Alignment Kit
Turn vague asks into testable scope, success criteria, and a shared plan in one pass
When stakeholders are unclear, change their mind midstream, or deliver non-actionable feedback, this recipe forces clarity fast: goals, success criteria, in-scope/out-of-scope, acceptance criteria, assumptions, and a first-cut plan. It produces a structured kickoff pack you can circulate for sign-off.
INGREDIENTS
PROMPT
Create a skill called "Kickoff Alignment Kit". Goal: turn vague project asks into a signed-off, testable kickoff pack. When I paste a messy brief (notes, emails, or a ticket), you will: 1) Ask only the minimum clarifying questions needed to avoid guessing about scope and success criteria. 2) Produce outputs in this order: - Project Charter-lite (goal, non-goals, constraints, success metrics) - In-scope / Out-of-scope lists - Assumptions + Open Questions register (question, owner, due date) - Deliverables list with acceptance criteria (testable) and definition of done - A 2-week "next steps" plan (milestones, owners, dependencies, risks) 3) Add a "Sign-off request" section with exactly what stakeholders must approve. Guardrails: - Never invent requirements. If information is missing, capture it as an open question. - If methodology is unspecified, keep outputs methodology-neutral. - Use plain language suitable for executives and delivery teams.
How It Works
Paste a messy project brief — meeting notes, emails, tickets, whatever you have — and this
recipe converts vague statements into measurable outcomes and explicit boundaries. If
information is missing, it captures open questions instead of guessing.
What You Get
- Project Charter-lite: goal, non-goals, constraints, success metrics — all on one page
- Scope boundaries: in-scope / out-of-scope lists with explicit assumptions
- Acceptance criteria: testable conditions per deliverable, plus a definition of done
- Open questions register: question, owner, due date — nothing falls through the cracks
- 2-week plan: milestones, owners, dependencies, and risks for the next sprint
Setup Steps
- Gather whatever project context exists (brief, notes, emails, tickets, SOW)
- Identify stakeholders and who has decision authority
- Paste everything in and let the recipe ask its minimum clarifying questions
- Review the kickoff pack, adjust, and circulate for sign-off
Tips
- Works with any methodology — agile, waterfall, hybrid, or unspecified
- Output formats: Google Doc, Confluence, Markdown, or slide outline
- Best used at project start, but also effective mid-project when scope has drifted
- Pair with the Scope Change Gatekeeper recipe to protect the baseline you just created