Users run structured ideation (core needs captured), receive multiple concept directions and Generated Concepts in 2b (scroll, select baseline, refine + breakout, carry-back), then Organize with initial designs + concept + core needs visible, link visuals to themes, and confirm AI-proposed groupings before analysis.
As a user, I want a full-team guided ideation session that runs the Kitchen Sink Discovery Framework and produces four structured deliverables, So that my idea is captured comprehensively before visuals, and every downstream step has a tethered source of intent.
Maps to: FR14.
Acceptance Criteria:
Given step 1 active and the full team (John, Kinsley, Winston, Mary) engaged
When the user progresses through prompts across the 8 discovery categories (Core Idea, Features & Functionality, Look & Feel, Visual Identity, User & Audience, Reference Examples, Copy & Voice, Constraints)
Then each question surfaces with its conversational prompt and concrete examples so the user is never staring at a blank field
And inputs are validated and stored as structured session data
And at session close the system produces four structured deliverables: (1) Problem & Solution Framing (problem, users, why-now, NOT, hypothesis, JTBDs, friction, delight, key insight), (2) Features & Capabilities (core / supporting / delight / deferred + personalization + error/empty-state + accessibility), (3) Master Design Prompt (tool-agnostic), (4) per-Screen Prompts (onboarding, home/dashboard, core features, empty state, error state, settings/profile)
And empty states use "team ready" tone per UX principles
And when the team proposes more than one concept direction, each is labeled and distinguishable in the transcript or summary (feeds FR46)
As a user, I want several concept options, the ability to work in another tab or window, and a clear way to bring results back into Quorum, So that I can explore freely without losing the team room or methodology state.
Maps to: FR46, FR15 (handoff), UX-DR15, NFR-I3.
Acceptance Criteria:
Given ideation has produced one or more concept directions (prompts / briefs)
When the user views the handoff area
Then each direction appears as a distinct card or row (title, short rationale, status: Not started / Exploring externally / Brought back)
And each has Open in new tab (or Copy link + open) for the external surface (e.g. Figma Make) without navigating away from Quorum as the only option
When the user returns from external work
Then they can attach URL, paste link, or upload (per product policy) to that direction and mark Brought back
And Quorum persists workspace session; returning to the Quorum tab does not lose pipeline position (FR13 alignment)
And at least two concurrent “exploring” directions can show in-progress state without corrupting each other’s attachments
As a user, I want tool-agnostic design prompts tied to each concept direction, downloadable in my choice of formats, So that I can generate concept frames in any design tool I use (Figma Make, Claude, v0, Midjourney, etc.).
Maps to: FR15, NFR-I3 (stable link field).
Acceptance Criteria:
Given ideation outputs exist
When the step completes
Then each concept direction has copy/export for its prompt artifact
And the prompt is tool-agnostic — not locked to Figma Make, usable in any generative design tool
And the user can download the prompt in any combination of Doc, HTML, and PDF formats via checkbox or dropdown selection
And the user can paste a returned link from any tool back per direction (feeds Stories 3.4, 3.6)
As a user, I want to scroll through concept variations, select a baseline, and refine the chosen direction (including in a breakout window), So that 2c Organize and step 3 start from tangible designs—not a blank list.
Maps to: FR46 (2b surface), FR15, FR17–FR18 (link/update), UX-DR16, NFR-I3.
Acceptance Criteria:
Given Kinsley (or workflow) has produced two or more concept variations for the workspace
And each variation covers the full product surface — not just a landing/hero page — including dashboard, core feature screens, settings, onboarding, empty states, and error states
When step 2b is active
Then the center surface shows Generated Concepts with a horizontally scrollable (or equivalent) series of preview cards, each labeled (e.g. direction name) and showing all screens per variation (e.g. thumbnail strip or screen carousel within each card)
When the user selects a card
Then a Refine region appears for that selection: natural-language input (placeholder guides concrete tweaks), Breakout window (opens external design surface in new tab/window), and submit to send refinement instructions
And the user can attach / paste link / import carried-back updates without losing Quorum session state
And baseline selection (and any retained alternates) is persisted and passed to Organize as part of the handoff bundle with concept labels and core needs from ideation
As a user, I want to align on aesthetics early without DS overhead, So that concepts match my intent.
Maps to: FR16.
Acceptance Criteria:
Given concept direction fields (mood, references)
When saved
Then they appear on concept artifact and feed orchestration context
As a user, I want to link concept visuals to features/flows and update them, So that the vision stays tangible.
Maps to: FR17, FR18.
Acceptance Criteria:
Given a Figma URL or attachment policy
When user adds or updates links/thumbnails
Then artifact panel shows Concept with last updated metadata
And broken link state is visible with retry guidance
As a user, I want the system to propose a full product sitemap AND themed feature groups with dependencies, So that I can review both the overall structure (every section + contents + relationships) and the thematic clustering before the filter.
Maps to: FR19, ARCH-4 (job may be async).
Acceptance Criteria:
Given vision data including the 2b handoff bundle (designs, concept framing, core needs)
When organize job completes
Then user sees a full product sitemap — every section of the product mapped out, each with per-section contents (screens, capabilities, data flows) and relationships to adjacent sections (think product's table of contents with annotations)
And user sees grouped themes with dependency hints alongside the sitemap
And both outputs are tethered to the baseline concept set and core needs so the filter starts from tangible context
And job states show queued/running/failed (NFR-P3)
As a user, I want to edit and lock organization, So that the filter runs on my approved structure.
Maps to: FR20.
Acceptance Criteria:
Given proposed groups
When user drags/edits or accepts
Then lock action enables next step
And checkpoint triggers celebration microcopy (UX principles §5)