# Feature

## Key Ideas

- **Outcome Container**: a Feature groups Goals that together produce a larger result.
- **Ordered When Needed**: Feature Goal order matters when work has dependencies.
- **Editable Membership**: users should be able to add, remove, reorder, and transfer Feature work safely.
- **Rollup Visibility**: Features should summarize progress without hiding individual Goals.
- **Shared List Pattern**: Features should reuse the same dense table, filter, sort, and pagination patterns as other work views.

## Purpose

The Feature surface exists to help users manage larger software outcomes. It organizes related Goals, preserves their order, shows progress, and gives users a place to inspect and edit the shape of the work.

Features prevent large ideas from becoming vague. They keep the bigger purpose visible while letting agents execute smaller Goals.

## Expected Role

The Feature UI should show Feature identity, description, reporter, assignee, node, progress, current or next Goal, and state rollup. The detail modal should let users inspect the ordered Goal list and edit membership without losing context.

Current implementation details that matter to intent:

- Feature rows use shared table, filter, sort, bulk, and pagination behavior;
- Feature details include a rollup, one always-visible inline Goal composer, and an ordered Goal list;
- the state rollup treats done, failed, and cancelled Goals as final, so a non-empty Feature is done when every Goal has reached any of those final states while preserving the separate outcome counts;
- the same inline composer creates Goals and edits editable Goal metadata, prompts, priority, and sequence placement without nesting another modal;
- ordered placement expresses Feature dependencies as a visible “after” relationship while independent Goals remain unordered;
- completed or protected Goals should not be casually disrupted by Feature-level actions;
- large Feature-managed Goal collections need pagination or incremental loading;
- Feature work should reuse shared work item services rather than page-only rules.

The Feature surface should not become a parallel task system. It is a grouping and intent-preservation layer over Goals.

## Future Direction

Future Features may become higher-level composition plans. Agents may propose Feature decomposition, dependency ordering, risk grouping, and staged rollout plans.

The surface should preserve the relationship between large product intent and small executable work so future AI systems can scale software composition without losing why the work exists.