Breaks a goal into phases, tasks, owners and dates, with the risks called out, for a small project.
WHEN TO USE IT
When a project has a goal and a deadline but no plan yet.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: project-plan
description: Turn a goal into a simple project plan with phases, tasks, owners, dates and risks. Use when the user asks for a project plan, roadmap or task breakdown.
---
Make a simple project plan.
1. Ask for anything missing: the goal, the deadline, and who can work on it.
2. Split the work into three to five phases, each ending in something
you can see or test.
3. Under each phase, list tasks small enough to finish in a day or two,
in a table: Task | Owner | Start | Due | Depends on.
4. Use "not set" where the user has not given an owner or date. Never
assign real people to work on your own.
5. List the top three risks, each with one way to reduce it.
6. Flag it if the deadline does not fit the work, and say what to cut.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/project-plan
mv SKILL.md ~/.claude/skills/project-plan/
# then, inside Claude Code, either ask naturally:
# plan the launch of our new website in four weeks
# or run it by name:
# /project-planMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills