Description

Adding skills for migrating non-Polylith Python projects into a Polylith workspace. These skills will be included in the polylith-cli releases.

Example prompt when I migrated the fastapi open source project (just to test these skills):

In this repo, there is @./.agents instructions about the Polylith Architecture and the "poly" tool.
There is also migration instructions, and those are important here.
I want to migrate the project #./project/fastapi according to the migration instructions.

Motivation and Context

To automate and simplify migration of non-polylith Python repos into a Polylith Workspace.

Refactoring and migration of entire code bases can be a good use of Agentic Engineering.

How Has This Been Tested?

The skills have been tested by migrating single-service repos into a new Polylith Workspace. During the migration, the skills have been updated with learnings from the migration. All skills are written by agents.

I have tested the skills with Claude (Opus 4.7, Claude Opus 4.8) and Mistral (mistral-large and devstral).

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I have read the code of conduct.
• I have read the contributing guide.
• I have updated the documentation accordingly (if applicable).