skills/vibe-task/SKILL.md

---
name: vibe-task
description: "Shape implementation tasks, validate scope, reconcile findings, decompose large objectives, or close an iteration. Use for requested planning and synthesis, not as a mandatory step before every edit."
---

# Tasks & synthesis

Read [the shared workflow](../../references/workflow.md) once per task, then the one recipe matching the requested operation and boundary. Do not load every recipe. The user's request controls scope and whether edits are allowed.

## Recipes

| Recipe | Operation |
|---|---|
| [Evolution & Improvement](references/evolution-improvement.md) | plan |
| [Iteration Closure](references/iteration-closure.md) | closure |
| [Map Synthesis](references/map-synthesis.md) | plan |
| [Synthesis](references/synthesis.md) | plan |
| [Task Shaping](references/task-shaping.md) | plan |
| [Validation & Clarification](references/validation-clarification.md) | plan |
| [Workstream Decomposition](references/workstream-decomposition.md) | plan |

For an explicit multi-stage request, follow the necessary stages without discarding requested work. For a single stage, deliver that result and stop. Use [the catalog](../../references/catalog.md) only if the requested boundary belongs elsewhere.