migrating-prompts-to-skills

To migrate prompt documentation, apply RED, GREEN, and REFACTOR phases to map legacy .prompt.md content into a standards-based SKILL.md format with proper frontmatter, scoping, and explicit environment testing.

The RED, GREEN, and REFACTOR migration rules define what legacy prompt content to KEEP, REWRITE, or DELETE, ensuring the resulting SKILL.md enforces explicit environment documentation, testing, and scoping to reduce drift.

You need to convert .prompt.md files into a SKILL.md format when you want to improve the discoverability, governance, and long-term maintenance of your existing prompt documentation across multiple domains.

Yes, migrating to a SKILL.md format requires documenting dependencies, components, and safety checks, while keeping each skill autonomous by avoiding cross-links to other skills within the structure.

The best way to structure frontmatter is by applying RED phase rules to your legacy prompt content, generating a compliant SKILL.md that maps existing instructions into a standards-based structure with explicit scoping.

You should avoid cross-linking other SKILLs during prompt migration to keep each SKILL autonomous, which reduces drift and ensures long-term maintenance without hidden dependencies across different domains.