Ship backlog faster. From one sentence to real Azure Boards work items.

Vorsam AI Work Item Generator is an Azure Boards wizard powered by SAMi AI: choose work item type, team/area path, and sprint/iteration path, chat to generate and refine draft work items, then create and review results directly in Azure DevOps.

The Vorsam AI Work Item Generator brings SAMi AI directly into Azure Boards so your team can move from idea to executable backlog without leaving Azure DevOps. In one guided wizard, you set work item type, team/area path, and sprint/iteration path, generate structured draft work items through chat, refine and deselect before create, and publish selected items with a clear results view.

It is designed to speed up backlog shaping while keeping control with your team: you decide what gets created, where it lands, and how it is structured.

Stop translating ideas by hand

Backlog breakdown is repetitive: same patterns, same parent/child links, same second-guessing. Vorsam gives you a conversation-first path—describe what you want in plain language, get a structured draft that respects your process, then create only what you approve. Product owners get speed. Engineering gets clarity. Admins keep control with bring-your-own-key AI (OpenAI or Google Gemini) stored at organization scope.

What you get

• Ideas → hierarchy — Go from “we need export audit logging” to a draft tree of stories and tasks aligned to your work item types.
• Native Azure DevOps — Runs as a Boards hub contribution; work items land in your project, your process.
• You own the keys — BYOK: use your org’s API keys; the extension does not resell AI—your provider relationship stays yours.
• Review, then create — Trim, deselect, and refine before anything hits the board—no surprise bulk creates.
• Free extension — Install from the Marketplace at no charge; AI usage follows your provider’s billing.

See the flow—six steps, six clips

The GIFs below mirror the real wizard: configure → chat → review → trim → generate → create and confirm.
(Place the six .gif files in the extension videos/ folder before npm run pack—see videos/README.md for filenames and copy guidance.)

1 — Dial in context: type, team, sprint

Pick the root work item type and optional team and sprint so every generated item fits how your team works—not a generic template.

2 — Describe the outcome in chat

Tell the assistant what you’re building in natural language. It proposes a draft backlog shaped around your setup—so the first cut is already in your language.

3 — Review the draft hierarchy

Scan parents and children, sanity-check scope, and align the structure with your release or sprint before you commit to creating anything.

Step 3 review GIF will appear here once videos/03-review.gif is added.

4 — Deselect what you don’t need

Uncheck items that shouldn’t ship in this batch—so the create step matches the slice of work you actually want on the board.

5 — Generate and refine

Iterate until the breakdown matches what the team agrees to ship—tight feedback loops without leaving the hub.

6 — Create work items and read the results

One pass to create the selected items in Azure Boards, with a clear readout of what succeeded and what needs a quick fix.

Built for the people who live in Boards

• Product & BA — Faster first-pass decomposition and grooming prep.
• Engineering leads — Consistent child work under epics and features.
• Any team on Boards with OpenAI or Gemini — AI where you already plan work.

Get started in four steps

1. Install from the Marketplace.
2. Open Boards → Vorsam AI Work Item Generator in the work hub group.
3. Have a project admin set Organization AI settings (provider + API key) once per org.
4. Run Setup → Generate → Results and ship the slice you approved.

Questions? Use the publisher support link on this listing, or visit vorsam.com for product details.

Technical note (admins)

Collection-scoped Extension Data for global settings; OpenAI or Gemini; optional model override. Creation uses Azure DevOps REST APIs with hierarchy appropriate to your process. Keys are masked in the UI after save; outbound calls follow your provider’s policies and quotas.