Hire an AI client project kickoff planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A kickoff brief of about one page
• A clear verdict: send a note, not ready, or hold the meeting, with the cost of the meeting
• A timed agenda, only when the verdict is to hold the meeting
• An action list with owner, due date and source for each item
• A list of open questions, each with who must answer

How it does the job well

• Start from the user problem and the evidence for it, then the solution.
• Write decisions down with the reason and the options you rejected.
• Keep scope small enough to ship and learn. Name what is out of scope.
• Define how success will be measured before building.

Mistakes it avoids

• Writing a brief for scope the client has not approved.
• Holding a meeting when the gate says send a note.
• Showing a proposed owner as confirmed.
• Using a pay rate the user did not give.
• Treating opinions or one loud request as proven demand.
• Specs that skip edge cases, error states or dependencies.

What a good result looks like

An example, not your task: A client has signed and you start next week, with scope in a proposal.

• Kickoff brief. Goal, audience, tone, scope in and out, limits and milestones in about one page.
• Open questions. What the client still has to answer, who answers and by when.
• Meeting verdict. Send a note, not ready or hold the meeting, with the reason and the meeting cost.
• Agenda. A timed, decision-first agenda with an outcome for each topic, only when you should meet.
• Action list. Each commitment with an owner, a due date and its source, with unconfirmed owners marked.
• MISSING and CHECKS MISSED. Gaps in the scope or inputs, and any check that could not run.

How the work is checked

• Success criteria, responsibilities and how changes are handled are stated, and every open decision has an owner.
• The agenda appears only when the verdict is MEET.
• Proposed owners are never shown as confirmed.
• Every fact, figure and date traces to a source or is labeled as an assumption.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Project kickoff brief writer. Writes the kickoff brief from the approved scope: goal, audience, tone, what is in and out, limits and milestones, with the open questions listed. Hands step 2 the open questions, the people and the decision to be made. Check before moving on: nothing in the brief goes beyond the signed scope.
• Meeting agenda and cost planner. Asks whether this should be a meeting. It prices it from your attendees, length and pay rates, then answers ASYNC, NOT-READY or MEET. Only MEET gets a timed agenda, and every topic needs an outcome. Hands step 3 the agenda, or the note to send. Check before moving on: a MEET has a decision, an agenda and an owner.
• Executive action register keeper. Turns commitments that are confirmed in the scope and brief into an action list with owner, due date and source. A proposed owner stays marked unconfirmed until someone says yes. Hand-back check: every action traces to a source line.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id prepare-a-clear-client-project-kickoff only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/prepare-a-clear-client-project-kickoff/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The approved scope: what is in and what is out (from the signed proposal or statement of work)
• Who will attend, who decides, and the length of the meeting you have in mind
• The average hourly pay of the attendees, to price the meeting (optional)
• Milestones and dates, and the goal, audience and tone the client has given you
• Questions you still need the client to answer

Helpful context (optional)

• The client's own words about their goal, audience and tone.
• Examples the client likes, if the project is creative.

Tools and access

• A chat AI that can run Python code: The Meeting agenda and cost planner uses small scripts to price the meeting and build the agenda. Without code, the AI does the sums by hand and says so.
• A shared doc: Put the brief and the action list where the client can read and confirm them.
• Claude Code or an AI that can run Python: It runs the three scripts, so the sums and the verdict are exact.
• Any chat AI: It works the cost out by hand and still prints the verdict line.

Functions and deliverables

• Client project kickoff planner: Share approved design scope, participants and open decisions. Get a kickoff brief, meeting decision and action list; an agenda when needed.
  • A kickoff brief of about one page
  • A clear verdict: send a note, not ready, or hold the meeting, with the cost of the meeting
  • A timed agenda, only when the verdict is to hold the meeting
  • An action list with owner, due date and source for each item
  • A list of open questions, each with who must answer
• Project kickoff brief writer: Turn a rough idea into a project kickoff brief with goal, audience, tone and limits that your team can sign off. Under two pages.
  • One-page brief
  • Clear goal, audience and tone
  • Scope and limits
  • A list of open questions to settle
  Source: RampStack.
• Meeting agenda and cost planner: Describe the decision, people and timing. Check whether to meet, estimate its cost and build a timed agenda.
  • A one-line verdict, MEET, ASYNC or NOT-READY, with the total cost in dollars
  • The cost per minute of the meeting
  • A timed, decision-first agenda with a five-minute closing slot
  • An action checklist by owner, with missing owners and dates flagged
  Source: Alireza Rezvani.
• Action item tracker: Share meeting notes or email threads. Get action items with owners, deadlines and unresolved commitments.
  • action-register.csv: id, task, owner, due_at, timezone, status, depends_on, source_id
  • clarifications.md
  • proposed-task-changes.md
• Product context file writer: Share product facts, audience and positioning. Get a reviewed context file that other marketing skills can reference.
  • A product marketing context file
  • A summary of what the file already holds
  • A change log of updates
  • Gaps you still need to fill
  Source: Corey Haines.

Tasks you can use it for

• A client has signed and you start next week, with scope in a proposal.
• A new client expects a kickoff call and you are not sure what it should cover.
• Your team keeps saying yes to kickoff calls that end without decisions.
• A website or design project has open questions that only the client can answer.

Limits to check before starting

• The project is internal and has no client. Use the Project kickoff brief writer on its own.
• The kickoff already happened and you only want to track actions. Use the Action item tracker.
• You only want to know if a meeting is worth holding. Use the Meeting agenda and cost planner.
• A client has asked for a change after work began. Use the Client scope change planner workflow.
• The scope is not approved yet. Settle the scope first, because this workflow plans from approved work only.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Open Claude, ChatGPT or Gemini. Pick one that can run Python code if you want the meeting cost worked out by script.
• Add the workflow pack. Paste the approved scope, the attendee list, who decides, the meeting length and your milestones.
• After step 1, read the brief with the client in mind. Does each line match what they signed? Fix anything that goes beyond it.
• After step 2, accept the verdict. If it says send a note, send the brief by email and skip the meeting.
• After step 3, check that each action has a real owner or is marked unconfirmed. After the meeting, add your notes and run step 3 again.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/prepare-a-clear-client-project-kickoff for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.