Reconstruct a finished project's backlog in Linear
At a glance
A solo builder used Claude Code to document a completed blog project as a structured Linear backlog. This workflow is listed under Coding, Documents.
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Give Claude Code access to the finished project's codebase, commit history and relevant earlier project conversations. The author created separate Linear accounts for himself and Claude and connected them through Linear's API. 2) Ask Claude to act as a product manager and reconstruct the actual work in a Linear project, grouping it by type and chronology. 3) Specify the contents of each issue: context, user story, measurable outcome, acceptance criteria, technical notes and definition of done. Ask it to add planning notes and decisions as comments. 4) Inspect the resulting phases and tickets as documentation of the shipped work and its decisions.
How it went
The author reported a board with 86 tickets across 15 phases, including technical decisions that had previously lived in code or conversations.
Worth knowing
This is a retrospective reconstruction from the material available to Claude, not a record of a backlog that existed before the build.