Task Specification

Use this template when defining a bounded implementation task for an engineer or AI agent. It provides structure for goals, references, instructions, acceptance criteria, and sub-task breakdown.

When to Use

Assigning a scoped piece of backend work with clear boundaries.
Defining acceptance criteria across code, tests, documentation, and CI.
Breaking a larger initiative into trackable sub-tasks.

Template

---
title: "Descriptive Title"
tags: [specification, task]
domain: process
maturity: published
author: Author Name
---

## Goal

Describe the goal of the task.

### GitHub Ticket References

- [Link to GitHub ticket]

## Reference Materials

### Requirements

### Design and Architecture

### Process and Quality

## General Instructions

1. Follow the `implementation-task` skill for execution workflow and expected byproducts.
2. Follow guidelines in the `instructions` directory for relevant tasks.

## Task-Specific Instructions

### Exclusions

- Specify any files or sections that should not be modified.

## Acceptance Criteria

### Code

- Expectations of the code to be implemented.

### Unit Tests

### Bruno Tests

### Documentation

### Build and Verify

At the end of each sub-task:
- Build succeeds
- All tests pass
- No regressions

### GitHub

- Create a GitHub ticket as a sub-issue of the parent issue.
- Add to the relevant project board with appropriate status, assignee, and iteration.

### Byproducts

See the `implementation-task` skill for additional artifacts.

## Open Questions and Decisions

| # | Question | Options | Recommendation | Decision |
|---|----------|---------|----------------|----------|

## Sub-Tasks

### Section 1

1. Sub-task 1
2. Sub-task 2

### Section 2

1. Sub-task 1
2. Sub-task 2