Skip to main content
skill CX Codex

055-design-parallel-change — Claude Code skill

The 055-design-parallel-change skill guides you through designing safe database schema changes when old and new application versions must run simultaneously. It breaks complex migrations into three separately deployable phases.

Apache-2.0 172 installs ★ 465 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 055-design-parallel-change -a claude-code
Open on GitHub

What 055-design-parallel-change does

055-design-parallel-change teaches Parallel Change design — a pattern for database migrations that require compatibility between versions. It helps classify migration risk, choose between Parallel Change and simpler approaches, then plan three stages: expand (add new structure), migrate (move data), contract (remove old structure).

The skill covers column renames, type changes, large-table backfills, relationship modifications, status transitions, timezone updates, and index changes. For each scenario, it explains tradeoffs: temporary dual code paths, extra migrations, verification effort, and deferred cleanup.

Once you settle on an approach, the skill routes implementation to framework-specific Flyway skills for Spring Boot, Quarkus, or Micronaut. It requires reading the reference document references/055-design-parallel-change.md before applying guidance.

What it helps with

  • plan a zero-downtime database schema migration
  • split a column rename into safe deployable steps
  • coordinate rollout of old and new application versions
  • design database rollback with minimal data loss
  • decide whether this schema change needs a compatibility window

Example prompts for the agent

  • Design a column rename using expand-migrate-contract phases
  • Check if this schema change requires Parallel Change
  • Plan zero-downtime deployment for this Flyway migration

How to install 055-design-parallel-change

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 055-design-parallel-change -a claude-code

2Manually: put the files in place

~/.claude/skills/055-design-parallel-change/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/055-design-parallel-change/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 055-design-parallel-change

How do I install 055-design-parallel-change in Claude Code?

Run npx skills add jabrena/plinth --skill 055-design-parallel-change -a claude-code, then check ~/.claude/skills/055-design-parallel-change/SKILL.md.

What does 055-design-parallel-change do?

It helps you plan safe database schema changes by breaking them into three deployable phases: expand (add new structure), migrate (transform data), and contract (remove old structure). This lets old and new app versions coexist during rollout.

When should I use Parallel Change instead of a simple migration?

When old and new app versions must run together, when changes affect large tables, or when rollback is critical. For additive, immediately safe changes, the skill recommends a simpler single migration.

Source text

SKILL.md · Apache-2.0
---
name: 055-design-parallel-change
description: Use when a database schema or data-meaning change needs Parallel Change, including expand, migrate, and contract sequencing for column renames, type or data reinterpretation, large-table backfills, relationship-table changes, enum/status transitions, timezone/default changes, and index or uniqueness changes. This should trigger before framework-specific Flyway implementation guidance when deciding whether a migration needs a compatibility window or whether a simpler migration is sufficient. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# Parallel Change Design

Guide Java Enterprise developers through Parallel Change for database migration scenarios. **This is an interactive SKILL**.

**What is covered in this Skill?**

- Deciding whether a database migration needs a compatibility window
- Sequencing database changes as expand, migrate, and contract deployable steps
- Preserving old and new application versions during rollout and rollback windows
- Handling column renames, type or data reinterpretation, large backfills, relationship-table changes, and index or uniqueness changes
- Explaining tradeoffs such as temporary dual paths, extra migrations, verification effort, and delayed cleanup
- Routing framework-specific implementation to Spring Boot, Quarkus, or Micronaut Flyway skills after the design approach is clear

## Constraints

Use Parallel Change as a database migration design pattern, then hand off implementation details to the framework-specific migration skill when needed.

- **MUST** read `references/055-design-parallel-change.md` before applying Parallel Change guidance
- **MUST** explain expand, migrate, and contract as separate deployable steps when recommending Parallel Change
- **MUST** decide whether Parallel Change is needed before recommending framework-specific Flyway implementation details
- **MUST** recommend a simpler single migration when the change is additive, immediately safe, and does not require old and new application versions to coexist
- **MUST** describe the compatibility, data-preservation, verification, and cleanup tradeoffs of the chosen approach
- **MUST** use framework-specific Flyway skills for Spring Boot, Quarkus, or Micronaut implementation details after the migration strategy is selected

## When to use this skill

- Apply Parallel Change to this database migration
- Use expand migrate contract for this schema change
- Plan a safe column rename migration
- Plan a zero-downtime database migration
- Should this Flyway migration use Parallel Change?
- Design a safe backfill and contract migration
- Decide if this schema change needs a compatibility window

## Workflow

1. **Classify the Migration Risk**

Read `references/055-design-parallel-change.md`, then identify the schema shape, data meaning, application read/write path, rollout window, rollback expectation, and production-data risk affected by the migration.

2. **Choose Parallel Change or Simpler Migration**

Recommend Parallel Change when old and new application versions or data interpretations must coexist. Recommend a simpler forward-only migration when the change is additive, small, immediately safe, and does not require a compatibility window.

3. **Design Expand, Migrate, Contract**

For Parallel Change, separate expand, migrate, and contract into independently deployable steps. Keep the old shape valid during expand and migrate; contract only after all deployed code and data have moved to the new shape.

4. **Plan Verification and Operations**

Define previous-release fixture checks, row-count expectations, duplicate detection, backfill monitoring, rollback behavior, and cleanup ownership. Prefer production-dialect migration tests and production-like data samples where feasible.

5. **Route Framework Implementation**

After the strategy is clear, use `313-frameworks-spring-db-migrations-flyway`, `413-frameworks-quarkus-db-migrations-flyway`, or `513-frameworks-micronaut-db-migrations-flyway` for framework-specific Flyway dependencies, configuration, migration locations, and tests.

6. **Report the Migration Plan**

Report the chosen approach, rejected alternative, expand/migrate/contract sequence or simpler migration, verification evidence, cleanup trigger, tradeoffs, skipped checks, and remaining risks.

## Reference

For detailed guidance, examples, and constraints, see [references/055-design-parallel-change.md](references/055-design-parallel-change.md).

© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth

Similar skills

All skills for Data and databases →

From the same set123

The whole set →
500-frameworks-micronaut-create-project The 500-frameworks-micronaut-create-project skill scaffolds a Micronaut 4.x Maven project with SDKMAN-managed tools and checks the generated build. Use it when starting a Micronaut service. CX Codex +1 211installs 054-design-tdd 054-design-tdd — a skill that walks Java developers through red-green-refactor cycles with test-driven development. Write a failing test first, implement just enough code to pass, then refactor while tests stay green. CX Codex +1 177installs 707-technologies-hexagonal-architecture 707-technologies-hexagonal-architecture is a Claude Code skill that reviews and improves Hexagonal architecture boundaries in Java projects without coupling to Spring Boot, Quarkus, or Micronaut. CX Codex +1 174installs 056-design-avoid-breaking-changes 056-design-avoid-breaking-changes reviews plans, OpenSpec changes, and APIs for breaking changes and migration risks before release. CX Codex +1 172installs 052-design-hamburger-method 052-design-hamburger-method splits oversized user stories and specs into thin vertical slices using the Hamburger Method. Delivers end-to-end observable value instead of isolated technical tasks. CX Codex +1 172installs 053-design-simple-rules 053-design-simple-rules is a Claude skill that checks Java design and refactoring decisions against Kent Beck's four rules, in order. CX Codex +1 172installs 057-design-feature-toggles 057-design-feature-toggles — an interactive skill for designing and reviewing feature toggles in Java services, including kill switches, staged rollouts, experiments, and cleanup. CX Codex +1 171installs 051-design-two-steps-methods The 051-design-two-steps-methods skill splits complex or risky code changes into two steps: first refactor to improve design while preserving behavior, then apply the intended behavior change. CX Codex +1 170installs

Project sponsors

Companies that keep this analytics open