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 02 of 10 3-6 quarters (the longest phase)· advanced

Step 2: Business Rule Extraction

Convert each in-scope RPG program (and CL program) into structured business rule catalogs — including indicator analysis, the most RPG-specific concern.

What you're doing in this step

For every program in scope, extract business rules using rpg-business-rule-extraction. Each program produces a 30-100 rule catalog plus indicator analysis (intent, not usage), subroutine catalog, decision tables, calculation formulas, and edge-case notes. CL programs often hide business rules in IF statements — use as400-cl-program-decomposition. Run iteratively: tooling → senior engineer → BA → SME sign-off.

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 varies (per program)

RPG Business Rule Extraction

Extract business rules from RPG II/III/IV programs into a structured catalog — handling indicators, cycle programs, and the procedural patterns of IBM i development.

rpgibm-i
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: Extracting from CL programs (orchestration code that often hides business logic in IF statements)

rpgibm-ijavadotnet
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 (cycle, indicators, RPG II/III) alongside the rule extraction

rpgibm-ijavadotnet
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

Legacy Code Analyzer Skill

Claude Code skill that reads legacy .NET code (WebForms, VB.NET, classic ASP) and explains what it does — the foundation for any migration.

claude-codedotnet
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
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 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

Confluence MCP for Evoke

Pre-configured Atlassian Confluence MCP server for Claude Code — search, read, and write internal documentation pages from chat.

claude-codemcp
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 in-scope programs have rule catalogs
  • Rules validated by business analysts
  • SMEs signed off on critical-path rules
  • Indicator semantics documented (intent, not just usage)
  • Decision tables built for complex branching
  • Calculation formulas with rounding rules documented
  • Cross-program rule duplications identified
  • Open questions tracked and assigned
Common pitfalls

What goes wrong at this step

  • Treating indicators as boolean variables — they encode state machines; capture intent
  • Skipping cycle analysis for RPG II/III — the cycle IS the program for those
  • Letting CL programs go unanalyzed — they often hold business rules
  • SME availability gaps — SMEs are the scarcest resource; lock in commitments
  • Auto-extracted rules treated as final — human review is non-negotiable
← Previous step

Command Palette

Search for a command to run...