Step 07 of 9 3-5 weeks (faster than slice 1)· advanced
Step 7: Migrate Slice 2 (Apply Lessons from Slice 1)
Take the next slice. Most infrastructure is built. The team knows the patterns. Slice 2 should ship faster than slice 1.
Recommended prompts
Use one of these to do the work in your IDE
Open the template to read it in full. Click Copy prompt to grab it (with your stack values pre-filled where they apply) — then paste into Claude Code, Cursor, or wherever you build.
Recommended skills
Drop these into Claude Code for this phase
Skills auto-trigger on the right kind of request. Install once; they apply to every prompt that fits.
Recommended MCP configs
Wire these tools into Claude Code first
MCP servers give Claude Code direct access to external systems (Jira, browsers, databases). Configure once.
When you're done
Verify these in your own work before moving on
This is a checklist for you to mentally tick off in your repo and IDE — the site doesn't track it, you do.
- Slice 2 ships through the same flow as slice 1, ramped to 100%
- Slice 1 retrospective items addressed for slice 2
- Playbook templates updated if patterns emerged
- Rollback procedure re-tested in staging
Common pitfalls
What goes wrong at this step
- Ignoring slice 1 lessons — every slice is a learning opportunity
- Skipping the retrospective — between slices, retro to capture lessons
- Scope creep — "while we're rewriting it, let's also..." (no)