Playbook
0 / 8 complete0%
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07
  8. 08
Step 05 of 8 6-10 weeks· advanced

Step 5: Pilot Migration (1-3 Representative Pipelines)

Validate the framework end-to-end on real pipelines: one simple, one medium, one complex. The pilot is where you discover what the framework didn't anticipate.

What you're doing in this step

Pick 1-3 pipelines spanning the complexity range. For each: document the legacy mapping, design the modern equivalent, build in ADF + PySpark, run parity tests, resolve discrepancies, deploy in shadow mode (parallel to legacy), cut over consumers when confident. Update the framework based on what you learn.

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 1-2 days

Behavior Parity Test Suite

Generate tests that lock down current legacy behavior so the new system doesn't accidentally change it during migration.

Use this when: The pilot needs new parity scenarios beyond what the framework has

View template
Template· Template 1 day to write

Migration Cutover Runbook

Detailed step-by-step runbook for the actual cutover from legacy to new system, including verification, communication, and rollback.

Use this when: Cutting consumers over from legacy to new — formal runbook drives the change

View template
Template· Template reference document; 1 day for initial setup

PySpark Transformation Standards

Standards for PySpark transformations in Bronze/Silver/Gold pipelines: idempotency, partitioning, Delta Lake patterns, and code organization.

Use this when: Implementation pattern reference while building the pilot pipelines

azurepysparkfabricdatabricks
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

Compatibility Layer Generator Skill

Claude Code skill that generates adapters, shims, and proxies for incremental coexistence between legacy and new systems.

claude-codedotnet
View skill
Skill· Skill 5 min setup

Data Validation Skill

Claude Code skill that compares old and new system outputs for parity — running validation queries on both DBs and reporting drift.

claude-codesql
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
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.

  • 1-3 pilot pipelines fully migrated
  • Parity tests pass for each
  • Shadow mode validation (parallel runs producing matching output)
  • Successful cutover to new pipelines
  • Lessons documented; framework updated based on findings
Common pitfalls

What goes wrong at this step

  • Pilot too easy — pick representative complexity; otherwise the framework isn't validated
  • Skipping shadow mode — first time the new pipeline runs alone is when bugs appear
  • No rollback drill — practice rolling back before you need to
  • Ignoring lessons — each pilot should update the framework or patterns
← Previous step

Command Palette

Search for a command to run...