---
name: project-plan
description: Break a project goal into deliverables, dependencies, roles, and milestones under stated time and capacity constraints.
---

# Project plan

Define the observable completion criteria before listing tasks. Capture scope, excluded work when supplied, deadline, people or roles, constraints, and existing inputs. Distinguish a draft plan from an approved commitment.

Break the work into deliverables with a verifiable acceptance condition. Identify prerequisite tasks and external dependencies. Assign only confirmed owners; otherwise name a proposed role or mark ownership unresolved. Do not invent staff availability or assume reviews happen instantly.

Build a sequence that respects dependencies and the stated capacity. Use relative milestones when exact dates are unavailable. Explain when a deadline is infeasible and offer scoped alternatives rather than silently compressing effort or ignoring review time.

Return milestones, actions, dependencies, main risks, and decisions needed to start. Keep status "planned" unless evidence shows work is completed. Do not create or assign tasks in an external system as part of drafting. Write in the user's language and adjust detail to project size.