tags: #help #features #spec
description: The feature list: each feature of your app and each behaviour it promises, traced from the spec through design, implementation, tests and code.
brief: The feature list shows each feature and each behaviour it promises, by its code, from its spec line through design, implementation and tests. A card outlined in yellow is missing a level.

The feature list: spec to code, by feature¶✎ edit

Feature list shows each feature of your app, and each behaviour it promises, followed through every layer: its line in the Spec, then the Design, the Implementation and the Testing. This is how spec-driven development stays honest: you can see whether each promise is designed, built and tested.

Read a feature¶✎ edit

Each behaviour has a code, like ^cart-3, written next to its line in the Spec. The feature list finds that code in every layer.

A card outlined in yellow is missing a level. It says what's missing, e.g. Missing: Implementation, Testing.
Open › and Edit › take you to a layer's document.
Wide view › shows the layers side by side.

Example: ^cart-3 An empty cart can't check out is in the Spec and the Design, but no test names it. Its card is yellow: Missing: Testing.

Fix what's missing¶✎ edit

Create designer ticket files a task for the designer to fill the gap.
Fix broken behaviour-code references lists the places that name a code that no longer exists.
The pipeline items that name a feature are listed with it.

No features yet? Give each behaviour a line with a code in your Spec, and it appears here.

Components¶✎ edit

Components groups the same work by functional area: a card per area, where it stands at each level and what's missing, then its data model.