---
name: writing-good-tasks
description: Write tasks in the following format. You can exclude some parts if they do not make sense for the particular task.
---

## Writing good tasks

Write tasks in the following format.
You can exclude some parts if they do not make sense for the particular task

Template:

## Context

Why this task exists and what larger goal it supports.

## Role

Primary role responsible for this task.

## Required Role Perspectives

- Product:
- Scrum:
- Design:
- Backend:
- Frontend:
- QA:
- Documentation:

## Scope

What is included.

## Non-Goals

What is explicitly not included.

## Acceptance Criteria

- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3

## Implementation Notes

Technical, design, or process notes.

## QA Plan

How this should be validated.

## Documentation Impact

Docs to create or update.

## Dependencies

Related tasks, epics, docs, or blockers.

## Completion Evidence

What must be recorded before this can be marked Done.