CLSkills
Project Management

How to Use Claude for Project Planning

The exact prompt, setup, and codes to get great results.

The Problem

Projects fail because scope isn't defined upfront, dependencies aren't mapped, and timelines are based on optimism instead of reality. Planning feels like overhead until it's too late.

The Prompt (Copy & Paste)

Create a project plan for [PROJECT].

Project: [WHAT YOU'RE BUILDING/DOING]
Team: [WHO'S INVOLVED + THEIR ROLES]
Deadline: [TARGET DATE]
Budget: [IF APPLICABLE]
Dependencies: [EXTERNAL FACTORS, OTHER TEAMS, VENDORS]

Generate:
1. **Project scope**: What's IN and what's explicitly OUT (prevent scope creep)
2. **Work breakdown**: Major phases β†’ tasks β†’ subtasks
3. **Timeline**: Gantt-style with dependencies (text format is fine)
4. **Milestones**: 4-6 checkpoints where you evaluate progress
5. **Risk register**: Top 5 risks + mitigation strategies + probability/impact
6. **RACI matrix**: Who's Responsible, Accountable, Consulted, Informed for each phase
7. **Communication plan**: How often and where the team syncs

Add 20% buffer to all time estimates (Hofstadter's Law applies).

Replace the [BRACKETED] placeholders with your specific details.

What You Get

A comprehensive project plan with clear scope, realistic timelines (with buffers), and a risk register. The RACI matrix prevents the 'I thought you were doing that' problem.

Prompt Codes That Help

Add these prefix codes to the start of your prompt for even better results:

Click any code to see its before/after examples and learn how it works.

Want all 120+ prompt codes?

The Claude Prompt Cheat Sheet has every tested code with before/after examples, combo stacks, and 10 workflow playbooks for different roles.

πŸ“¬

Get new prompts + workflows weekly

Join developers and professionals getting tested Claude prompt codes, workflows, and real-world techniques. One email when there’s something worth sharing.