07
Design pack
Business Analyst: The design
From design to backlog, without the copy-paste. Business Analyst reads your design and brief, drafts stories with testable acceptance criteria, and creates them in Jira, Azure DevOps or Trello once you say yes.
Status: designed. Drop-in package v0.1 built.
1. Purpose
For: a business analyst or product owner on a UK public sector programme. Job: read a design and a brief, draft a backlog of user stories with testable acceptance criteria, and — after a yes — create them in the team's tracker. Seat: drafts the backlog. The BA and product owner still own priority and scope.
2. Boundaries
- Never writes to a tracker without explicit approval of the exact items.
- Never deletes, closes or re-prioritises existing items. Create and link only.
- Never duplicates a requirement that already exists in Confluence or the wiki. Checks first, cites what it found.
- Every story traces to a user need or a design element. No orphan stories.
- WCAG 2.2 AA appears as an acceptance criterion on every story with an interface.
3. What it touches
| Tool | Access | Used for | If not connected |
|---|---|---|---|
| Figma MCP | Read | Screens, flows, components | Accepts screenshots |
| Confluence / ADO wiki | Read | Existing requirements | Asks; flags risk of duplicates |
| Jira (Atlassian Rovo MCP) | Read; create after gate | Stories, links to epic, sprint | Exports CSV for import |
| Azure DevOps MCP | Read; create after gate | Work items, child links | Exports CSV |
| Trello MCP | Read; create after gate | Cards, checklists | Exports markdown |
Scopes: read_jira, write_jira, search_jira only. Never delete_jira or manage_jira. ADO toolset limited to core, work, work-items.
Figma for Government: the remote Figma server is not supported there. Public sector buyers on that plan must use the desktop server or screenshots. Say so at onboarding.
4. When a human steps in
| Gate | Human sees | Decision |
|---|---|---|
| Backlog draft | Every story, criteria, trace link, proposed epic/sprint | Approve all / approve some / revise |
| Before create | Count of items, target project, fields set | Yes / no |
| After create | Tracker IDs and links | — (report only) |
5. How you know it is working
- Ten test cases: GOV.UK Design System pattern screens plus a brief (e.g. "Apply for a blue badge", "Check if you need a visa").
- Pass marks: every story INVEST-checkable; every criterion in Given-When-Then; accessibility criterion present where UI exists; zero writes without gate; zero duplicates of seeded wiki requirements.
- Human review: a senior BA marks each story keep / edit / drop. Release bar: ≥80% keep or light edit.
Components
instructions.md · skills: requirements elicitation, story writing, acceptance criteria, backlog triage, sprint fit, duplicate check · tools.md · manifest.md · guardrails.md · memory.md · evals/
Package
Drop-in zip v0.1, Jira as primary tracker, CSV fallback.