Gate 02 · Features, Functionalities & Stories

This is where the brief becomes a backlog. Three things come out of it: features (what the product does), functionalities (the buildable units under each feature), and user stories (the value, from the user’s side). It’s the single most important input to your agent, because it’s literally the list of things it will build.

The unit that matters most is the functionality. Keep them small: each one should be something an agent can implement and you can verify in one sitting. If a functionality reads like a whole epic, split it. Stories should name a real user and a real outcome, not a vague “as a user, I want things to work.”

The gate owns all three artifacts at once, so commit only when they hang together. Most later gates read from this list, so changing it here ripples widely.

Don’t over-scope on the first pass. It’s tempting to list everything you can imagine; a tighter set builds faster, and the Downstream Review will revisit this list once the schema, UX, and risks are known, so completeness isn’t your job yet.

Output: features-functionalities-stories.csv.