Claude for project planning, done properly.
The tested prompt, the codes that help, and the setup project management pros run. Copy, adapt, ship.
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.
Three reasons this actually lands.
The prompt, the codes, the fit. Each one on its own is a nice-to-have. Together, they change the workflow.
One tested prompt, copy-paste ready. Rules baked in, placeholders marked, tone locked down. No prompt-engineering trial runs, no back-and-forth.
Prefix with REASON, V=2, L99 for compound effects. Each code is a documented technique, not a magic word.
Tuned for project management workflows. Not a generic template, and not another "you are a helpful assistant" hack.
Without the pattern vs with it.
What the day looks like when you keep winging the prompt, and what it looks like when you stop.
Generic prompt. Claude writes something that could be about anyone, in any industry, from anywhere. Sounds like a template because it is one.
The CLSkills prompt with placeholders for your context. Claude writes it like a specialist who actually knows the work. Publishable after one edit pass.
You paste, Claude answers, you rewrite, you paste again. Ten minutes of back-and-forth per output. Three hours across a batch of five.
Prompt loaded once. You feed the specifics, Claude returns the finished output. Two minutes per, twenty across five. Same tone, same structure, every time.
Middle-of-the-road copy that reads AI-flavoured. Recipients notice. Response rates stay low. You end up rewriting most of it anyway.
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.
Copy this, replace the placeholders, ship.
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 context.
Stack these prefixes for compound gains.
Prepend one or more of these to the prompt above. Each code is documented on its own page with before and after examples.
Every prompt, once.
The Cheat Sheet is every tested code, with a before and an after.