Skip to content

Implementation Slice Template

Purpose

Use this template when defining work for an AI coding agent, engineer, or implementation team. The slice should be clear enough that the work can be completed without guessing.

A slice should define:

what is being changed
why it is being changed
which product behaviours it supports
which architecture areas it touches
what is in scope
what is out of scope
how the work will be verified
what AI is allowed to do

Template

# Implementation Slice

## Slice ID

`IMP-000`

## Name

Short name for the implementation slice.

## Status

Draft | Ready | In Progress | Review | Accepted | Rejected

## Purpose

Explain why this slice exists.

Describe the outcome this slice must produce.

## Linked Intent

Map this slice back to the product definition.

### Purpose

Reference the AIDD-17 purpose section if relevant.

### Users

List the users affected by this slice.

### Behaviours

List the behaviours this slice implements or changes.

### Features

List the features this slice contributes to.

### Success Criteria

List the success criteria this slice supports.

## Linked Shape

Map this slice back to the system design.

### Constraints

List the constraints that apply.

### System Context

List external systems, actors, or boundaries involved.

### Solution Strategy

Reference the selected technical approach.

### Building Blocks

List the components, services, modules, or packages involved.

### Data and Interfaces

List database tables, APIs, events, files, messages, or contracts involved.

### Runtime Behaviour

Describe the runtime flow this slice affects.

### Deployment and Operations

List deployment, configuration, logging, monitoring, or operational concerns.

## Applicable Rules

List the project rules that apply to this slice.

### Cross-Cutting Rules

Authentication, authorization, validation, errors, logging, security, privacy, performance, or coding standards.

### Decisions

Reference relevant decision records.

### Delivery Rules

List the delivery rules this slice must follow.

## Scope

Define exactly what this slice includes.

Use clear statements.

Example:

- Add `POST /documents`.
- Validate submitted text content.
- Store the document record.
- Return the created document ID.

## Out of Scope

Define exactly what this slice does not include.

Example:

- Do not implement text extraction.
- Do not implement embeddings.
- Do not change authentication.
- Do not change the document list page.

## Implementation Tasks

List the expected tasks.

Example:

1. Add backend endpoint.
2. Add request validation.
3. Add database migration.
4. Add unit tests.
5. Add integration tests.
6. Update relevant documentation.

## Expected Files or Areas to Change

List the files, folders, modules, or services that are expected to change.

If unknown, list the likely areas.

## Files or Areas Not to Change

List files, folders, modules, or services that must not be changed.

## Verification

Define how this slice will be accepted.

### Automated Tests

List required automated tests.

### Manual Checks

List required manual verification.

### Acceptance Criteria

List the conditions that must be true for this slice to be accepted.

### Definition of Done

Define when this slice is complete.

## AI Instructions

Define how AI may assist with this slice.

Example:

- AI may edit only the files listed in expected areas unless it explains why another file must change.
- AI must not implement out-of-scope items.
- AI must stop if required information is missing.
- AI must provide a summary of changes.
- AI must list tests added or changed.
- AI must list any assumptions made.
- AI must not invent product behaviour, architecture, or delivery rules.

## Review Notes

Use this section during review.

Include:

- what changed
- what was accepted
- what was rejected
- follow-up work
- risks found
- documentation updates required

Guidance

A good implementation slice is small enough to review and specific enough to prevent drift.

Minimum required fields

For small slices, use at least these fields:

# Implementation Slice

## Slice ID

## Name

## Purpose

## Linked Intent

## Linked Shape

## Applicable Rules

## Scope

## Out of Scope

## Verification

## AI Instructions

Core rule