vincentbirot is drafting Mike's path from solo assistant to firm platform

A documentation-only PR lays out the full Lexnova AI roadmap before a single feature is built.

workflowknowledge-management

The fork's owner has dropped fourteen design documents into the repo - a design-system audit and twelve feature briefs - with zero code changes. Together they sketch the productisation of the codebase: rebranding Mike to Lexnova AI, then layering in concurrent request queueing, matter status and assignees, per-matter tasks, time tracking, lightweight DOCX collaboration, Gmail and Slack hooks, an admin panel, user profiles, a partner dashboard, and finally a firm-wide memory layer that lets the AI draw on the whole firm's prior work.

The briefs are sequenced into seven sprints and written to be fed to design AI tools for wireframes, then to coding AI to implement. Each one carries user stories, screen descriptions, edge cases, and acceptance criteria - explicitly drafted as build inputs, not just plans for humans.

So what Worth watching for anyone curious how a single-user legal assistant gets turned into a multi-seat firm platform, and how an AI-first dev workflow plans before it builds.

View this fork on GitHub →

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