Skip to content

Product

Grooming, scopes, personas and canvas — shaping requirements before they become stories.

Updated View as Markdown

Grooming is the front door to a project. You describe the product; the business analyst agent elicits what’s missing and writes structured requirements rather than a wall of prose. You review and edit them like any other artefact.

Scopes

Scopes group requirements into deliverable slices, so a large brief can be cut into releases instead of landing as one undifferentiated pile. Assign requirements to a scope once they’re stable.

Personas

Personas capture who the software is for. They feed story generation, so the stories come out phrased around a real user rather than an abstract “user”.

Canvas

Canvas is a free-form space for mapping flows and sketching structure next to the formal artefacts — useful while a feature is still taking shape.

From requirements to a backlog

Approved requirements generate a backlog: epics first, then user stories under them. The agent can also review a requirement set and flag gaps before you commit to building it.

Generated stories land in Delivery → Backlog, where you groom them further and pull them into a sprint.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close