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

Step 6: First Domain (Vertical Slice)

Migrate / build one complete business domain end-to-end (Customer or Sales is typical). Bronze + Silver + Gold + DQ + a Power BI semantic model. Validates everything from Phases 3-5 against a real use case.

What you're doing in this step

Pick one domain that cross-cuts source systems, has a clear business owner, has a visible BI consumer, and isn't on the critical path (room to make mistakes). Build Bronze for all source systems contributing to the domain. Build Silver with conformed entities. Build Gold with 1-2 dimensional models. Wire DQ tests at every layer. Publish a Power BI semantic model. Reconcile against legacy reports.

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

azurepysparkfabricdatabricks
View template
Template· Template 1-2 days per dimension

Slowly Changing Dimensions (SCD) Implementation in PySpark

Implement SCD Type 1, 2, 3, and 6 patterns in PySpark with Delta Lake MERGE — for dimensional modeling in modern data platforms.

Use this when: The domain has slowly-changing dimensions (customer, product, employee, etc.)

azurepysparkdelta-lakefabric
View template
Template· Template 1-2 days for initial setup

Data Quality Test Suite

Generate comprehensive data quality tests for ETL pipelines: schema validation, freshness checks, null/duplicate/range checks, and business invariants.

Use this when: Adding domain-specific DQ checks

azurepysparkfabric
View template
Template· Template 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.

Use this when: Cutting consumers over from a legacy reporting source to the new domain

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

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

  • Domain Bronze layer complete (all sources ingested)
  • Domain Silver layer complete (conformed entities, SCD where needed)
  • Domain Gold layer complete (1-2 dimensional models)
  • DQ tests pass for all layers
  • Power BI semantic model published
  • Reconciliation with legacy reports passes (counts and key metrics match)
  • Documentation complete (lineage, SLAs, ownership)
  • Stakeholder validation passed
Common pitfalls

What goes wrong at this step

  • Domain too big — pick the smallest valuable domain
  • Skipping reconciliation with legacy — discovers issues months later
  • No semantic model — the platform is incomplete without consumption
  • Stakeholder absent — they need to validate definitions in Silver
  • Performance neglect — hot-path queries should be fast or users won't adopt
← Previous step

Command Palette

Search for a command to run...