Step 07 of 9 1-3 quarters· advanced
Step 7: Continue Expanding Domains
Build out remaining domains, refining patterns. Common slicing: by business domain, by source system, by criticality, or by region.
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.
- All in-scope domains modeled in the platform
- All in-scope reports migrated
- DQ coverage acceptable (every Silver+ table has tests)
- Lineage tracked for all pipelines
- Documentation complete
Common pitfalls
What goes wrong at this step
- Long tail of low-value data — migration takes 50% of time on last 10% of value
- Burnout — multi-quarter projects need rotation and small wins
- Scope creep — "while we're modernizing, let's also add ML / streaming..."
- Pattern divergence — without governance, each domain reinvents patterns. Maintain code review and shared library