---
name: Feature or change
about: Problem, behavior spec, acceptance criteria, and boundaries for implementers or agents
labels: enhancement
---

## Summary

One sentence: the outcome you want.

## Problem

What is wrong, missing, or expensive today? Who is affected?

## User story (optional)

As a …, I want …, so that …

## Specification

Numbered, observable behaviors. Prefer “when X then Y” over vague goals.

1. 
2. 
3. 

## Acceptance criteria

Checkboxes define done. Keep each item verifiable without guessing intent.

- [ ] 
- [ ] 
- [ ] 

## Non-goals

What this issue must not do or solve (prevents scope creep for humans and agents).

- 

## Constraints

Technical, UX, accessibility, performance, compatibility, or data rules that must hold.

- 

## Dependencies

Blocked by or blocks other work. Link issues or PRs.

- 

## Open questions

Decisions still needed. Mark resolved items as you go.

- 

## Verification

How a reviewer or agent should confirm the spec (manual steps, test level, or “N/A for design-only”).

- 

## Related

Design docs, prior discussion, or comparable products (links).
