Shape what gets built: features, epics, user stories, releases, milestones, and the dependencies between them.
featurev0.2.0When to run it
When discovery has surfaced opportunities that need to be turned into shippable scope, or when the team's existing backlog has lost its shape.
What you'll have at the end
A populated feature set, grouped into feature_area and epic records, decomposed into user_story items, scoped into release and milestone events. Dependencies declared via the appropriate edges.
Common starting point
The top three features the team is committing to in the next release. Surface their epics, stories, and dependencies.
Sequence summary
One step: run the product_spec creation sequence — features, epics, user stories, releases, milestones.
Name the units of value the product delivers. Each feature should be a thing a user can describe in plain language.
Group related features into epics that ship together. Epics are user-visible; tasks are not.
Write each feature from the user perspective. "As [persona], I want [job], so that [outcome]." Define acceptance criteria.
Decompose stories into the smallest unit of work an engineer can pick up. Surface the dependencies between them.
Bundle stories into releases. Milestones mark moments of strategic significance: first paying customer, first 1000 users.
Group releases into strategic themes. Maintain a changelog the team and customers can read together.