Feature Spec Report for mock-support-desk

Branch: main · Build: 127 · Commit: def5678 · Pull request: #42

Branch: main · Build: 234 · Commit: 0bbfda9

Generated 15th January 2026 at 12:30.

Specification layers

Context

Architecture, design, and domain vocabulary

1 document4/4 covered

Support desk

Modelactive

SUPPORT Support desk

active

Define the shared vocabulary for a small customer support workflow.

SUPPORT-M001: Ticket covered 1

A customer request that needs a response from an agent.

SUPPORT-M002: Agent covered 1

A team member who reviews tickets and sends replies.

SUPPORT-M003: Priority covered 1

An internal urgency label.

Rules

  • SUPPORT-M-R001: Tickets MUST keep a stable public reference. covered by direct test 1

Delivery surfaces

User-visible applications and workflows

2 documents4/4 covered

Ticket inbox

active
test playwrightscreenshots optional

Let agents find the next ticket to work on without losing context.

Rules

  • SUPPORT-INBOX-R001: The inbox MUST show open tickets first. covered by SUPPORT-INBOX-S001 1

Scenarios

SUPPORT-INBOX-S001: Agent reviews the queue covered 1

Rules covered by this scenario: SUPPORT-INBOX-R001

Given an agent has open tickets line 26 no screenshot captured

When they open the inbox line 27 no screenshot captured

Then open tickets are listed by age line 28 screen changed · screenshot captured

Inbox before priority badges
Inbox before priority badges

Ticket replies

draft
test playwrightscreenshots optional

Help agents answer a customer without leaving the ticket.

Rules

  • SUPPORT-REPLY-R001: The reply composer MUST preserve unsent text. covered by SUPPORT-REPLY-S001 1

Scenarios

SUPPORT-REPLY-S001: Agent drafts a reply covered 1

Rules covered by this scenario: SUPPORT-REPLY-R001

Given an agent has selected a ticket line 26 no screenshot captured

When they write a reply line 27 no screenshot captured

Then the draft remains visible line 28 no screenshot captured