parallel-task-format

Task Specification Format

Compact YAML format for parallel task files in parallel/TS-XXXX-slug/tasks/.

Complete Task Example

---
id: task-001
component: users
wave: 1
deps: []
blocks: [task-004, task-005]
agent: python-experts:django-expert
skills: [python-experts:python-style, python-experts:django-dev, python-experts:django-api]
tech_spec: TS-0042
contracts: [contracts/types.py, contracts/api-schema.yaml]
---
# task-001: User Management

## Scope
CREATE: apps/users/{models,views,serializers,urls}.py, apps/users/tests/*.py
MODIFY: config/urls.py
BOUNDARY: apps/orders/*, apps/products/*, apps/*/migrations/*

## Requirements
- User model with email authentication
- UserSerializer with explicit fields
- UserViewSet (list, retrieve, create, update)
- Email uniqueness validation

## Checklist
- [ ] Model matches UserDTO in contracts/types.py
- [ ] API matches /api/users/* in contracts/api-schema.yaml
- [ ] pytest apps/users/ passes
- [ ] mypy apps/users/ passes
- [ ] ruff check apps/users/ passes
- [ ] No files modified outside scope

YAML Frontmatter Fields

Field	Required	Description
id	Yes	Task identifier (task-NNN or task-NNN-component)
component	Yes	System component name
wave	Yes	Dependency wave number (1, 2, 3...)
deps	Yes	Task IDs this depends on (empty list [] if none)
blocks	No	Task IDs this blocks (optional)
agent	Yes	Recommended agent type
skills	Yes	Skills the agent should invoke (list from agent-skills-mapping.yaml)
tech_spec	No	Tech Spec ID (if applicable)
contracts	Yes	Contract files to reference (relative paths)

Note: skills are stored in task files so prompt generation can include them in === REQUIRED SKILLS === sections. They are NOT stored in manifest.json.

Scope Section Format

Use compact notation with three directives:

CREATE

Files to create (use glob patterns). A file can only be in CREATE for ONE task.

CREATE: apps/users/{models,views,serializers,urls}.py, apps/users/tests/*.py