A free guide by Fadia Joheir ↗ INSTAGRAM · ↗ TIKTOK

SAVE THIS

THE PROJECT DOC GENERATOR

Every project needs the same docs — kickoff brief, scope, status updates, close-out. Most freelancers wing it. This skill builds the full project documentation suite from a 3-question intake. Looks pro. Saves the relationship.

THE PROBLEM

Project docs are how you avoid scope creep, late-night clarification calls, and the "I thought you meant..." conversation. Writing them from scratch every project = you don't.

Templates exist but they're either too lawyer-y (for big agencies) or too thin (Notion templates). This skill generates docs sized for solopreneurs.

THE SKILL

You give Claude:

Project name + client
Scope (what they're hiring you for)
Timeline + budget

Claude returns the project doc suite:

Kickoff brief (the "what we're doing" doc)
Scope of work (the "what's in / what's out" doc)
Weekly status update template
Mid-project review template
Close-out doc (final delivery + next steps)

INSTALL

Standard.

THE FULL SKILL FILE

---
name: project-doc-generator
description: Generates the full project documentation suite — kickoff brief, scope of work, weekly status template, mid-project review, and close-out doc. Tailored to project name, scope, timeline, and budget. Designed for solopreneurs and small teams.
when_to_use: User says "project docs," "kickoff brief," "scope of work," or describes starting a new client project.
---

# The Project Doc Generator

You build project doc suites. Tight. Anti-lawyer-speak. Solopreneur-sized.

## Inputs
1. **Project name + client name**
2. **Scope** — what you're hired for
3. **Timeline + budget**
4. **Optional:** specific concerns / past issues with similar clients

## Output: 5-doc suite

### 1. KICKOFF BRIEF (1 page)

PROJECT: [Name] CLIENT: [Client] START: [Date] END: [Target date] BUDGET: $[X]

WHAT WE'RE DOING: [2 sentences in plain English]

WHY: [1 sentence on the outcome client wants]

WHAT SUCCESS LOOKS LIKE:

[Outcome 1 — measurable]
[Outcome 2]
[Outcome 3]

KEY MILESTONES:

[Date]: [Milestone]
[Date]: [Milestone]
[Date]: Final delivery

YOUR DECISIONS NEEDED:

[Decision 1] by [date]
[Decision 2] by [date]

MY DELIVERABLES:

[Specific item 1]
[Specific item 2]

COMMUNICATION:

Updates: [cadence and channel]
Response time: [normal / urgent]

POINT OF CONTACT:

You: [client name + email]
Me: [user name + email]


### 2. SCOPE OF WORK (the "in/out" doc)

SCOPE OF WORK — [Project name]

IN SCOPE:

[Specific deliverable 1]
[Specific deliverable 2]
[Specific deliverable 3]

OUT OF SCOPE (clarification — these are not included):

[Common scope creep 1]
[Common scope creep 2]
[Common scope creep 3]

If you want any of the out-of-scope items, we'll add them as a change order: [process].

CHANGE ORDERS: Any addition to scope = new line-item. Estimated separately. Approved before starting.

ASSUMPTIONS:

[Assumption 1]
[Assumption 2]

If any assumption is wrong, scope adjusts.


### 3. WEEKLY STATUS UPDATE TEMPLATE

SUBJECT: [Project] — Week [N] update

Hi [Client],

This week: ✅ Completed: [list] 🔄 In progress: [list] ⚠️ Blocked: [if any — and what would unblock]

Next week:

[Plan 1]
[Plan 2]

Decisions needed from you by [date]:

[Decision 1]

Time used so far: [X / Y budget]

Anything I'm missing? Reply by [date].

[Your name]


### 4. MID-PROJECT REVIEW (~50% milestone)

PROJECT REVIEW — [Project] — [Date]

PROGRESS:

Completed: [list]
On track for [end date]: yes / no

WHAT'S WORKING:

[Pattern 1]
[Pattern 2]

WHAT'S NOT:

[Issue 1] → [proposed fix]
[Issue 2] → [proposed fix]

ADJUSTMENTS NEEDED:

[Scope adjustment if any]
[Timeline adjustment if any]
[Budget adjustment if any]

RISKS AHEAD:

[Risk 1] → [mitigation plan]

Want a 30-min call to align? [Calendar link]


### 5. CLOSE-OUT DOC

PROJECT CLOSE-OUT — [Project name] DATE: [Final delivery date]

DELIVERED:

[Item 1] → [link]
[Item 2] → [link]
[Item 3] → [link]

OUTCOMES:

[Measurable outcome 1]
[Measurable outcome 2]

TIME / BUDGET:

Hours: [X]
Budget: $[X] of $[Y]

WHAT WORKED:

[Pattern]

WHAT DIDN'T:

[Honest reflection]

NEXT STEPS:

[Optional: ongoing retainer? specific follow-up?]
[Specific date for check-in if applicable]

ASKS:

Testimonial: [if you'd like]
Referrals: [your ideal next client]

Thank you. Working with you was [genuine reflection].

[Your name]


## What NOT to do

- Don't include lawyer-speak unless user explicitly wants it
- Don't include things user hasn't agreed to
- Don't make scope-of-work hostile — it's a clarity doc, not a defense doc
- Don't generate templates longer than the project warrants

## Delivery

End with: *"Send the kickoff brief + scope of work BEFORE starting. Saves the late-night clarification call every time."*

SAFETY CHECK

Same as Day 1.

WHAT'S NEXT

Day 95 of 100. Pair with Day 71 — SOP Builder (for recurring projects) and Day 24 — Invoice Chase Sequence (for payment chasing).