Add Parallel change pattern as Skill -> 055-design-parallel-change (Skill dedicated to Database migration scenarios)

[jabrena]

User Story

As a Java Enterprise developer maintaining database-backed applications
I want to add a dedicated 055-design-parallel-change skill for database migration scenarios
So that I can apply the Parallel Change pattern safely when evolving database schemas and application code.

Source References

• Martin Fowler: Parallel Change
  • https://martinfowler.com/bliki/ParallelChange.html
• DORA: Database Change Management
  • https://dora.dev/capabilities/database-change-management/

Existing Skill References

Use the existing framework-specific Flyway parallel-change references as source material:

• Spring Boot Flyway parallel change
  • https://github.com/jabrena/cursor-rules-java/blob/main/skills-generator/src/main/resources/skill-references/313-frameworks-spring-db-migrations-flyway-parallel-change.xml
• Quarkus Flyway parallel change
  • https://github.com/jabrena/cursor-rules-java/blob/main/skills-generator/src/main/resources/skill-references/413-frameworks-quarkus-db-migrations-flyway-parallel-change.xml
• Micronaut Flyway parallel change
  • https://github.com/jabrena/cursor-rules-java/blob/main/skills-generator/src/main/resources/skill-references/513-frameworks-micronaut-db-migrations-flyway-parallel-change.xml

Acceptance Criteria

Feature: Parallel Change skill for database migration scenarios

  @acceptance-test
  Scenario: Provide a dedicated design skill for database parallel change
    Given the project contains framework-specific Flyway parallel-change skill references
    When the new `055-design-parallel-change` skill is defined
    Then it explains the Parallel Change pattern for database migration scenarios
    And it references Martin Fowler's Parallel Change guidance
    And it references DORA database change management guidance
    And it consolidates reusable guidance from the existing Spring Boot, Quarkus, and Micronaut Flyway parallel-change references

Notes

• Edit XML sources under skills-generator/src/main/resources/, not generated skill output.
• Keep the new skill focused on database migration scenarios.
• Use the existing framework-specific references as inputs for shared pattern guidance.