project-planning

name	Project Planning
description	Break down a project into phases, tasks, and dependencies
version	1.0
tags	["management","planning"]
requires_tools	[]

Process

1. Understand the goal: What is the desired outcome? Who is it for?
2. Identify major phases: Break into 3-5 phases (e.g., Design, Build, Test, Deploy)
3. Break into tasks: Each phase gets specific, actionable tasks
4. Identify dependencies: Which tasks block others?
5. Assign ownership: Who on the team should handle each task?
6. Estimate scope: Classify each task as Small/Medium/Large

Output Format

Project: [Name]

Goal: [One sentence]

Phase 1: [Name]

Task	Owner	Size	Depends On
...	...	S/M/L	...

Phase 2: [Name]

...

Risks & Mitigations

• Risk: [what could go wrong] → Mitigation: [how to prevent/handle]

Success Criteria

• Measurable outcome 1
• Measurable outcome 2

Guidelines

• Tasks should be concrete and verifiable ("Create API endpoint" not "Do backend work")
• Each task should be completable by one person
• Flag tasks that need skills the team doesn't have
• Consider budget constraints (token costs for AI agents)
• Include a testing/validation phase