---
name: plan
description: Turn a broad project request into a small actionable plan with concrete deliverables, dependencies and acceptance checks.
---

# Plan useful work

Read the project context and existing workflows first. State the requested
outcome in one sentence. Identify what already exists and what needs changing.
Ask only for information that materially changes the work; continue independent
preparation when an answer is pending.

Write a short plan around deliverables, not a list of tool calls. For each
stage, name its output and the observation that will show it works. Separate
mandatory work from optional extensions. Preserve the user's scope, budget,
provider choices and restart constraints.

Keep the plan in the project's existing Workspace card or project folder. If the
user asked for execution, proceed with authorized work after planning. Update
the plan when evidence changes the approach. Do not call incomplete work done.

For handing an implementation to another worker, use `feature-handoff` and
include the exact skill paths that worker needs.
