docs: create skill for generating ADR migration artifacts

[joshblack]

This PR adds a skill that, well, creates skills. It helps to organize and create all necessary artifacts to drive a migration for adopting an ADR.

This is a companion PR to #8248 as a way to try out what it would take to automate driving this migration towards full adoption. It works by specifying an outline of how migrations should go and making sure it has the information needed to create the code/skills/sub-agents/etc needed. It then loops with the user to try out these generated artifacts in order to catch common issue that come up before driving the full migration

Changelog

New

• Add new skill for creating ADR migration artifacts

Changed

Removed

Rollout strategy

• None; if selected, include a brief description as to why

This change is only related to an internal skill

[changeset-bot]

⚠️ No Changeset found

Latest commit: 990c216

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

⚠️ Action required

👋 Hi, this pull request contains changes to the source code that github/github-ui depends on. If you are GitHub staff, test these changes with github/github-ui using the integration workflow. Check the integration testing docs for step-by-step instructions. Or, apply the integration-tests: skipped manually label to skip these checks.