Prompt: Create a Project Brief

Starting a project without a brief is how scope creep, missed deadlines, and budget overruns happen. This prompt create project brief turns a vague idea into a structured document everyone can align on.

Clarity before execution. Every time.

The Prompt

You are a project manager creating a comprehensive project brief from my description.

PROJECT DESCRIPTION:
[Describe the project in your own words. Include: what you want to build/achieve, who it is for, why it matters, any constraints you know about, and any decisions already made.]

BUDGET: [range or "to be determined"]
TIMELINE: [desired completion date or "flexible"]
TEAM: [who is available to work on this]

CREATE A PROJECT BRIEF WITH:

1. PROJECT OVERVIEW
   - Objective: One sentence describing what success looks like
   - Background: Why are we doing this? What problem does it solve?
   - Scope: What is IN scope and what is explicitly OUT of scope

2. DELIVERABLES
   - List every tangible output with acceptance criteria
   - For each deliverable: what it is, who owns it, when it is due

3. TIMELINE
   - Phase breakdown with milestones
   - Dependencies: what must happen before what
   - Key dates and decision points

4. RESOURCES
   - Team members and their roles
   - Tools and access needed
   - Budget allocation by phase

5. RISKS
   - Top 5 things that could go wrong
   - For each: likelihood (high/medium/low), impact, mitigation plan

6. SUCCESS METRICS
   - How do we know this project succeeded?
   - Specific, measurable criteria

7. OPEN QUESTIONS
   - What needs to be decided before we start?
   - What assumptions are we making that need validation?

RULES:
- Be specific. "Build a website" is not a deliverable. "Build a 5-page website with contact form, service pages, and blog" is.
- If my description is vague, make reasonable assumptions and flag them as assumptions.
- The brief should be complete enough that someone who was not in the room could execute the project.

After Generation

Review the scope section carefully. This is where misalignment hides. If anything in the "in scope" list surprises you, adjust it now. If anything critical is in "out of scope," move it.

The risks section should make you slightly uncomfortable. If all risks are low likelihood, the analysis was too optimistic. Push for honesty.

Using the Brief

Share it with everyone involved before work begins. Get sign-off on scope, timeline, and deliverables. This brief is your contract with the team and the stakeholder.

When scope creep appears later (and it will), point to the brief. "That was not in scope. We can add it, but it changes the timeline by X."

Build These Systems

Ready to implement? These step-by-step tutorials show you exactly how:

• How to Create Automated SOW Generation - Generate statements of work automatically from project scope discussions.
• How to Build an AI Task Planning Agent - Create an agent that breaks down goals into tasks and manages execution.
• How to Create Automated Post-Meeting Task Creation - Convert meeting action items into project management tasks automatically.