Plan a legacy system move with design docs, tickets and reviews
Idea + starter prompt, not run by us yet
For: Engineering leads planning to move an old product to a new stack
An engineer prepared context files in layers, then handed Claude Code the old repos, read-only database access and a reference build. Claude drafted the design, reviewer agents tested it, and it made tickets. Every ticket had a design doc and a plan doc for him to check, then ran in a separate git worktree while a loop watched CI.
Steps
- Write context files that explain the old system and the target.
- Give database access as read-only.
- Have it draft the design and get a second review before any code.
- Review the design and plan for each ticket before work starts.
- Plan for token costs and check what tools may cut off, since a docs tool overwrote two large pages.
Starter prompt
Read CLAUDE.md and the context files in [docs folder]. The old system is in [repos]. The target stack is [target]. Database access is read-only. 1. Draft a design for the move and list the risks. 2. Break it into tickets, each with a short design and plan. Show me the design before creating tickets. Do not write to any database or shared docs page. Do not merge anything. Tell me what you could not check.
Original post: DEV · found via agentusecases.ai. Written up in our own words. We haven't run it, so test it on made-up data first.