# Task body profiles

Concise section contracts for planning task Markdown bodies. Profiles define which `##`
sections a task should include, in what order, and whether each is required.

Recorded tasks remain canonical Markdown + YAML front matter under `planning/tasks/`.
Each profile section value is markdown content; profiles only formalize structure.

| Profile | Use |
|---------|-----|
| [feature-minimal.yaml](feature-minimal.yaml) | Default feature tasks (Summary, Acceptance criteria) |
| [feature-expanded.yaml](feature-expanded.yaml) | Large AI-driven features (Context, Goal, Tests, …) |
| [bug.yaml](bug.yaml) | Bug reports with reproduction sections |

## Authoring shapes

Task draft JSON (`schemas/task-draft.schema.json`) accepts either:

- `body` — monolithic markdown string (existing), or
- `sections` — object keyed by profile section `key`, composed into markdown at import

Optional `profile` selects the contract (`feature-minimal` when omitted for feature tasks).

See [docs/task-body-profiles.md](../../docs/task-body-profiles.md) for the human guide and
[docs/task-authoring.md](../../docs/task-authoring.md) for the intake workflow.