Lexnova drops 14 design briefs covering a seven-sprint productisation roadmap

vincentbirot landed ~2,000 lines of documentation-only design briefs that map the Lex Nova fork's full roadmap from single-user assistant to multi-user law-firm platform. No code changes - this is the spec layer that precedes implementation.

workflowknowledge-management

Fourteen markdown files cover a seven-sprint sequence. A pre-sprint phase handles the rebrand from Mike to Lexnova AI. From there, the sprints run through concurrent request queueing, matter status and assignee tracking, per-matter task management, time-clock and timesheet capture, lightweight DOCX collaboration, Gmail and Slack integrations, an admin panel, user profiles and templates, a partner dashboard, and a firm-wide RAG memory layer.

Each brief is structured explicitly as a build input rather than reference documentation. They carry user stories, screen wireframe descriptions, component additions, edge cases, accessibility notes, and acceptance criteria - the format chosen to feed directly into design tools (Claude with artifacts, v0, Lovable) and then into Claude Code for implementation. A design-system audit and a master index act as cross-cutting principles across all briefs.

The scope is the full productisation arc: transforming a single-user legal assistant into a multi-user firm platform with billing, collaboration, and shared knowledge. Nothing here has been built yet.

This PR exists to make the intent legible and the sequencing explicit before any code is written.

So what Worth a look if you want to understand the Lexnova fork's intended direction before committing to a merge strategy. The briefs make the full roadmap concrete - useful for evaluating whether vincentbirot's product vision overlaps with yours. Skip if you need running code; there is none here.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?