Definition & Specification
Turning agreed direction into personas, requirements, and specs a team can build
About this domain
Definition & Specification is where an agreed direction becomes something a team can actually build. It spans writing requirements and specs, developing the personas the work is aimed at, describing intended behavior and its edge cases, and defining what done means through acceptance criteria.
Its purpose is to remove ambiguity before it turns into rework. A well-specified item lets a delivery team pick the work up and build with confidence, without guessing at edge cases or reverse-engineering intent — it is the bridge between a prioritized idea and a delivery team’s backlog.
Trigger, mindset & exit
A prioritized item that is agreed in principle but not yet specified clearly enough for a team to build.
Precise and empathetic — thinking through edge cases and acceptance criteria while keeping the user the artifacts describe firmly in view.
The work is specified clearly enough — requirements, personas, acceptance criteria — that a delivery team can pick it up and build with confidence.
How the workflows connect
Open one to see its agents.