---
name: Feature request
about: Propose a new behaviour, command, or workflow
title: ""
labels: enhancement
assignees: ""
---

### Problem

A clear description of the friction the proposed feature would
relieve. Concrete examples are stronger than abstract requirements.

### Proposed behaviour

What eeco would do after the change. If the proposal touches the
[public surface](../docs/ARCHITECTURE.md#public-surface) — commands,
flags, exit codes, config keys, queue or memory formats, builtin
workflow names — call that out explicitly.

### Constraint checklist

Confirm the proposal respects the non-negotiable constraints (mark
the box if respected, leave blank with a note if not):

- [ ] **Write-scope** — writes only inside the workspace.
- [ ] **No auto-commit / no auto-push** — does not invoke `git
      commit` or `git push` on the user's behalf.
- [ ] **Brand-free** — no third-party product names in user-facing
      output or docs.
- [ ] **Budget-capped AI** — any AI call routes through the existing
      Gate (consent + budget + park-on-skip).
- [ ] **Queue-mediated** — decision-bearing output goes through the
      queue, not directly to the tracked tree.

### Alternatives considered

Other approaches you weighed and why they were not chosen.

### Additional context

Workflow notes, a sketch of the UX, a draft of the CLI shape — any
detail that grounds the proposal.