Users generate stories with acceptance criteria, design/motion references, exports for external AI coding tools, progress tracking, and backend planning when needed.
As a user, I want stories generated from approved scope, So that build work is legible.
Maps to: FR33.
Acceptance Criteria:
Given approved scope state
When sprint planning runs
Then stories include Given/When/Then ACs
And stories are workspace-scoped and versioned
As a user, I want stories to reference design and motion artifacts, So that implementers have context.
Maps to: FR34, NFR-I3.
Acceptance Criteria:
Given story records
When user or system links artifacts
Then links are stable URLs or internal IDs with metadata
And missing link surfaces “blocked” hint for implementer
As a user, I want to export stories for Cursor/Claude Code-style workflows, So that external tools can implement.
Maps to: FR35, NFR-I1.
Acceptance Criteria:
Given a story
When export is triggered
Then bundle includes AC, links, architecture excerpt, file path hints per PRD buildArchitecture
And export JSON validates against published schema version field
As a user, I want to update story status in Quorum, So that the board reflects reality.
Maps to: FR36, UX-DR9.
Acceptance Criteria:
Given board columns
When user drags or sets status
Then persistence updates and audit-friendly history optional for later
And Blocked requires reason field
As a user, I want backend tasks when the definition demands infra, So that Damien-path work is explicit.
Maps to: FR37.
Acceptance Criteria:
Given product definition flags backend need
When planning completes
Then backend stories are generated with same rigor as frontend
And conditional activation matches PRD (Damien)