Everything that changed
Four modules rebuilt, a refreshed interface throughout, and a
release that covers the whole path from requirement to design.
Chat · Elicit · Documents · Mockup
Clarifying questions
A question card appears before generation, targeting the gaps that
would materially change the output — audience, dependencies,
compliance standards, sections to include. Questions arrive in
passes with a progress indicator. Any one can be skipped, or the
whole card at once.
Chat
Interactive widgets
Chat now renders live, actionable cards instead of plain text:
work item hierarchies, sprint and board summaries, WIQL results,
cumulative flow and velocity, pull requests, file diffs, commit
history. Write actions are supported, with explicit confirmation
required for anything destructive.
Elicit
Multi-level hierarchies
Generate Epic → Feature → User Story from a single source item in
one run, instead of a separate pass per level with manual
re-parenting afterwards. Use your project’s process template chain
or build a custom hierarchy, then save and share it across the
organisation.
Elicit
Coverage, not counts
Title generation continues until requirement coverage is
addressed, rather than producing a fixed number. Every
AI-generated title carries a relevancy score from 0 to 10,
sortable for triage — and you can add your own titles alongside
them.
SOP / Document Generator
Documents you can defend
Templates for SRS, SOP, Test Plan, Release Notes and User Guide.
Refine drafts through chat scoped to a whole document or a named
section. Every AI edit appears as a marked diff to apply or
discard, incrementing the version and recording the instruction
behind it. Publish to Azure DevOps Wiki, attach to a work item, or
export to Word, PDF or Markdown.
Mockup
Mockups that hand off
Theme, fidelity and platform controls above the prompt. Generate
variants to compare directions without losing the original. Select
any component to edit it with scoped chat. Preview across desktop,
tablet and mobile, then export as HTML, design tokens, CSS
variables or a Tailwind theme.
One source item in. An entire Epic → Feature → User Story hierarchy
out, published to Azure DevOps with every link type applied
top-down. That used to be a separate pass per level, then manual
re-parenting.