Azure DevOps Work Item Hierarchy From a Product Brief
Break a brief into epics, features, user stories and tasks.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Break this product brief into an Azure DevOps work item hierarchy: [PRODUCT_BRIEF]. Process template we use (Agile, Scrum, Basic or CMMI): [PROCESS_TEMPLATE]. Team and skills: [TEAM]. Target release: [RELEASE]. Return Epics, then Features under each, then User Stories (or Product Backlog Items under Scrum), then Tasks for the first sprint only, to avoid false precision. For each story give the title, an 'As a... I want... so that...' line, acceptance criteria as bullets, a suggested area path, tags and an iteration, but leave story points blank unless I give a scale. Show dependencies as Predecessor or Successor links by title, and show any release order the brief hints at. Use the work item type names of my process template and mark any you are unsure of [VERIFY]. Check three rules: every story belongs to a feature and every feature to an epic; each story can be completed in one sprint, otherwise split it by workflow step, rule or user type; each feature has an outcome describable in a sentence. Show an indented outline with counts at each level. Do not invent requirements. List parts of the brief you could not turn into work items and why, your assumptions about process template and area paths to be checked with the project administrator before anything is created [VERIFY], and the five questions that would most improve the backlog.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.