Prompt Chain: Generate a Complete Project Kickoff Package in 15 Minutes

What This Builds

A multi-step prompt workflow that takes a basic project brief and generates a complete kickoff package: project charter, RACI matrix, risk register, communication plan, and kickoff meeting agenda — all in a single 15-minute session. This replaces 4–6 hours of document creation at the start of every project, and ensures every project starts with complete, professional documentation regardless of how rushed the kickoff is.

Prerequisites

• Claude Pro subscription ({{tool:Claude.price}}) — for longer context and faster generation
• A project brief (even rough notes about the project scope, team, and timeline)
• 15–20 minutes per project kickoff
• Cost: {{tool:Claude.price}}

The Concept

A prompt chain is like an assembly line for documents. Instead of asking AI for everything at once (which produces mediocre output), you feed the output of each step into the next step as context. Each document builds on the ones that came before — the risk register references the RACI matrix, the communication plan references the risk register, and so on.

By the end of the chain, every document in your kickoff package is internally consistent — the same people, timelines, and risks appear in every document because each one was generated with full context from the previous ones.

Build It Step by Step

Part 1: Write Your Project Brief

Before running the chain, spend 5 minutes writing a brief in plain text. You don't need formal templates — just answer these questions:

Project Name: [name]
What we're doing: [1-2 sentence description]
Why we're doing it: [business reason or goal]
In scope: [what's included]
Out of scope: [what's not included — be specific]
Key deliverables: [list 3-5 things we'll produce]
Timeline: start [date] → end [date]
Budget: [$amount or "TBD"]
Team: [list names/roles — PM, BA, developers, QA, etc.]
Stakeholders: [sponsor name/role, client/owner, key approvers]
Key dependencies: [other systems, teams, or events we depend on]
Known risks: [anything you're already worried about]

This brief is your seed — everything downstream comes from it.

Part 2: Run the Chain (5 Prompts in Sequence)

Open Claude Pro. Paste your project brief as the first message:

"Here is the project brief I'll be working from: [paste your brief]. I'll be generating several project documents using this as the foundation."

Then run these 5 prompts in sequence, using each output as context for the next:

Prompt 1 — Project Charter:

Based on the project brief above, write a complete project charter. Include:
1. Project Overview (purpose, business justification)
2. Scope Statement (in scope, out of scope — be specific)
3. Project Objectives (3-5 measurable objectives using SMART criteria)
4. Key Deliverables (list with description of each)
5. Major Milestones (5-7 key dates based on the timeline)
6. Constraints and Assumptions
7. Success Criteria (how we'll know the project succeeded)
8. Project Sponsor and Approval section

Use formal project management language. This document will be reviewed by executives.

Review the charter output. Make mental note of anything that needs adjustment, but move on — you can refine at the end.

Prompt 2 — RACI Matrix:

Using the project charter above and the original brief, create a RACI matrix.
Roles to include: [list your team roles from the brief]
Tasks/decisions to include: all major deliverables and decisions from the project charter, plus these specific items: [add any specific governance decisions important to this project].

Format as a table. Use R=Responsible, A=Accountable, C=Consulted, I=Informed.
Flag any rows where multiple people are marked R (this is usually a governance problem).

Prompt 3 — Risk Register:

Based on the project charter and RACI matrix above, generate a risk register with 12-15 risks.
For each risk:
- Risk description (1 sentence)
- Category (Technical/Resource/Stakeholder/External/Schedule/Budget)
- Probability (H/M/L)
- Impact (H/M/L)
- Risk Score (multiply: H=3, M=2, L=1)
- Owner (from the RACI matrix above — assign to the most appropriate role)
- Mitigation Strategy (2-3 sentences)
- Contingency Plan (if it happens, we will...)

Prioritize risks based on risk score. Include at least 3 risks specific to the out-of-scope items (scope creep risk).

Prompt 4 — Communication Plan:

Using the stakeholders from the project charter and the risks from the risk register, create a communication plan. For each communication type, include:
- Communication type (status report, steering committee, team standup, etc.)
- Audience
- Frequency
- Format (email, meeting, dashboard)
- Owner (from RACI matrix)
- Key content to cover

Also include:
- Escalation path (based on the stakeholder hierarchy in the charter)
- How to communicate the risks flagged in the risk register
- Protocol for scope change communications

Format as a table for the regular communications, then add the escalation and special situations sections below.

Prompt 5 — Kickoff Meeting Agenda:

Create a kickoff meeting agenda for this project. Attendees: [list from brief].
Duration: 90 minutes.

The agenda should cover:
- Project overview and objectives (reference the charter)
- Scope walkthrough — especially what's out of scope
- RACI review — confirm roles and responsibilities
- Risk discussion — top 5 risks from the register
- Communication plan overview — how we'll work together
- Timeline and first milestone
- Q&A and open issues

For each agenda item: time allocation, presenter/facilitator (from RACI), key points to cover, and any decision to be made.

Also create a "parking lot" section template for issues raised but not resolved during the meeting.

Part 3: Review and Refine (5 minutes)

After running all 5 prompts:

1. Scan each document for accuracy — are the names, dates, and roles correct?
2. Check for internal consistency — does the same person appear as RACI owner for a risk's mitigation?
3. Ask Claude: "Is there anything missing or inconsistent across these five documents?" — it will catch things you missed.
4. Make targeted edits: "Update the risk register — the data migration risk should be High probability, not Medium, because we know the legacy data is poor quality."

Real Example: IT System Implementation Kickoff

Setup: You've been handed a new ERP implementation project. Brief notes from the sponsor meeting, 3-week timeline to kickoff.

Input (project brief): Project: ERP Implementation Phase 1 What: Replace legacy accounting system with SAP S/4HANA for Finance department Why: Legacy system end-of-life Dec 2026; manual workarounds costing 30 hrs/week In scope: Finance module, 15 users, data migration from old system, training Out of scope: HR module, IT infrastructure, mobile access in Phase 1 Team: PM (you), Business Analyst, 2 SAP consultants (vendor), IT lead, Finance lead Stakeholders: CFO (sponsor), Controller (primary user), IT Director (approver) Timeline: 6 months, go-live December 1 Budget: $380K

Output: 5 complete, internally consistent documents ready for executive review in 15 minutes.

Time saved: What used to be a 6-hour documentation effort (after 2 rounds of revisions) completes in 20 minutes including review.

What to Do When It Breaks

• Output gets repetitive or loses context → Start a fresh Claude conversation and paste the project brief plus the output of the previous step as context before running the next prompt.
• Risk register doesn't reference the right people → Paste the RACI matrix directly into the risk register prompt: "Using these RACI assignments: [paste table], assign risk owners accordingly."
• Charter is too generic → Add specifics: "Add a section on the specific business process changes that will result from this project" or "Reference the regulatory compliance requirement driving this project."
• Kickoff agenda is too long → Ask: "Reduce this to 60 minutes by cutting less critical agenda items. What would you remove and why?"

Variations

• Simpler version: Run just the first prompt (project charter) — this alone saves 2–3 hours and provides the foundation for manual creation of the other documents.
• Extended version: After the 5 documents, add a 6th prompt: "Based on everything above, create a 30-day project plan for the first phase, with weekly milestones and owner assignments from the RACI."

What to Do Next

• This week: Run the chain on your next new project — even if just to generate a starting point
• This month: Save the project brief + all 5 generated documents as a template — future projects start with this structure
• Advanced: Load the 5-prompt chain into a Claude Project (Level 3 guide) so it automatically has your preferred formats and can reuse outputs across sessions

Advanced guide for Project Management Specialist professionals. Requires Claude Pro ({{tool:Claude.price}}) for best results with long document chains.