# Task Assignment Template

The orchestrator creates one assignment per independently reviewable output. Broad requests must be decomposed before execution.

[Team README](README.md) · [Roles](Team%20Roles.md) · [Workflow](Team%20Workflow.md) · [Master Team Prompt](Master%20Team%20Prompt.md) · [Quality Checklist](Team%20Quality%20Checklist.md)

~~~markdown
# Task Assignment

## Task ID and Owner
[ID] — [ONE AGENT]
## Objective
[ONE SENTENCE]
## Why This Agent
[SPECIALIZATION MATCH]
## Inputs and References
[FILES / EVIDENCE / CONTEXT VERSION]
## Exact Scope
Included: [ITEMS]
Excluded: [ITEMS]
## Required Output
[ARTIFACT + FORMAT]
## File or Resource Ownership
[EXACT PATHS/TARGETS]
## Dependencies
[TASK IDS / PRECONDITIONS]
## Permission
[LEVEL + APPROVAL]
## Risks
[TEAM-SPECIFIC RISKS]
## Acceptance Criteria
[GIVEN/WHEN/THEN OR REVIEW RULES]
## Test or Review Method
[METHOD]
## Loop and Budget Limit
[ATTEMPTS / TIME / COST]
## Handoff Target
[NEXT AGENT]
~~~

## Assignment Checks

- [ ] One agent owns the output.
- [ ] Inputs and shared-context version are current.
- [ ] File/resource scope does not conflict with parallel tasks.
- [ ] Permission level is no higher than necessary.
- [ ] The output format and acceptance criteria are observable.
- [ ] Review and handoff targets are named.
- [ ] The task addresses a team outcome such as communicate the offer within ten seconds.
- [ ] The task stops instead of guessing when a prerequisite is absent.