Playbook
0 / 10 complete0%
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07
  8. 08
  9. 09
  10. 10
Step 07 of 10 1-3 years (the dominant phase)· advanced

Step 7: Continue Migrating Slices

Migrate the remaining capabilities — backend, UI, and tests in parallel. Track progress visibly: % programs migrated, % transactions on new, % 5250 screens replaced, % users on new UI.

What you're doing in this step

Slice by slice. Common slicing patterns: by module (orders → inventory → shipping), by user role (CS team → sales → warehouse), by interaction style (inquiries → transactions → batch), by location (multi-site rollout). UI work parallels backend work. Each slice has its own backend service, frontend, parity tests, and phased rollout.

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.

Primary recommendation 0.5 day

Feature Flag Rollout Strategy for Migrations

Use feature flags to safely route traffic between legacy and new systems during migration with controlled rollout and instant rollback.

View template
Template· Template reference document

RPG to Java/.NET Translation Checklist

Pattern-by-pattern translation guide for RPG IV constructs to modern Java or .NET — including indicators, the cycle, native I/O, and the patterns that should be replaced rather than translated.

Use this when: Working through unfamiliar RPG idioms in a slice's source programs

rpgibm-ijavadotnet
View template
Template· Template 1-2 days per major job stream

AS/400 CL Program Decomposition

Decompose CL (Control Language) programs and job streams into modern orchestration — Spring Batch, Step Functions, Airflow, or message-driven architectures.

Use this when: A slice's batch orchestration is buried in CL that needs explicit decomposition

rpgibm-ijavadotnet
View template
Template· Template 10 min

shadcn/ui Component Builder

Generate a custom React component composed of shadcn/ui primitives with proper accessibility and types.

Use this when: Building reusable UI components for the SPA replacement

reacttypescripttailwindshadcn-ui
View template
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.

Skill· Skill 5 min setup

Spec-Driven Builder Skill

Tool-neutral skill that walks developers through PRD → stories → schema → API → tests for any new feature, producing real artifacts at each step. The methodology is identical on every supported tool.

claude-codecopilotcursor
View skill
Skill· Skill 5 min setup

Migration Planner Skill

Flagship migration skill that walks Claude Code through audit → strategy → slicing → cutover for any legacy system migration.

claude-code
View skill
Skill· Skill 5 min setup

Test Generator Skill

Claude Code skill that picks the right test type (unit/integration/E2E) based on context and applies Evoke's testing patterns automatically.

claude-code
View skill
Skill· Skill 5 min setup

Code Reviewer Skill

Claude Code skill that performs comprehensive code review on PRs and diffs, prioritized by severity with concrete fixes.

claude-code
View skill
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.

MCP config· MCP config 10 min setup

Azure DevOps MCP for Evoke

Pre-configured Azure DevOps MCP server for Claude Code — work items, repos, PRs, and pipelines from chat.

claude-codemcp
View config
MCP config· MCP config 10 min setup

GitHub MCP for Evoke

Pre-configured GitHub MCP server for Claude Code — issues, PRs, code search, and Actions from chat.

claude-codemcp
View config
MCP config· MCP config 5 min setup

Filesystem MCP for Evoke

Pre-configured filesystem MCP server for Claude Code — safe, scoped read/write access to project files.

claude-codemcp
View config
MCP config· MCP config 10 min setup

Postgres MCP for Evoke

Pre-configured Postgres MCP server for Claude Code — schema inspection and read-only queries to make database work safer and faster.

claude-codemcppostgres
View config
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.

  • All capabilities have a modern equivalent
  • IBM i traffic significantly reduced (target: <10% of original)
  • All scheduled batch migrated
  • All integrations updated
  • All users on the new UI (or hybrid is intentional)
Common pitfalls

What goes wrong at this step

  • Long-tail capabilities — last 10% takes 50% of the time
  • Burnout — multi-year projects need rotation
  • Scope creep — "while we're rewriting it..." → no
  • Stalling on rare-but-critical edge cases — annual processes only run once a year
← Previous step

Command Palette

Search for a command to run...