AutoSkillit: Skill for Claude Code

Phase Elaboration Skill

Elaborate a single phase from a high-level migration plan into a complete, self-contained implementation plan. The plan should contain all background context needed for implementation.

When to Use

• User says "elaborate phase", "elaborate phase 0", "elaborate phase 1", etc.
• User wants to create a detailed implementation plan for a specific migration phase
• User says "phase elaboration" or "detail phase N"
• After implementing a phase, when ready to elaborate the next one

Critical Constraints

NEVER:

• Modify any source code files
• Implement any part of the plan
• Add backward compatibility to the plan (unless a cleanup phase explicitly removes it)
• Add fallback mechanisms that hide bugs
• Add deprecation notes, stubs, warnings
• Include rollback mechanisms
• Add stakeholder sections or PR breakdowns
• Elaborate multiple phases at once - one phase per invocation
• Make assumptions about codebase state without verifying
• Read previous Phase#.md files unless you have a specific question that requires looking up a detail

ALWAYS:

• Assess current codebase state with subagents FIRST
• Write output to the plan directory (e.g., {plan_dir}/Phase#.md)
• Run /dry-walkthrough on the written Phase#.md to validate
• Make the plan self-contained with all background context needed
• Include verification commands and success criteria
• Report findings to terminal output
• Update the master plan if dry walkthrough reveals issues affecting subsequent phases

Plan Directory Structure

All plans live in a dedicated directory:

{plan_directory}/
├── {master_plan_name}.md    # Unique name (e.g., feature_migration_plan.md)
├── Phase0.md                # Elaborated phase 0 (if exists)
├── Phase1.md                # Elaborated phase 1 (if exists)
├── Phase2.md                # etc.
└── ...

• Master plan: Has a unique descriptive name, contains the high-level multi-phase plan
• Phase plans: All named Phase#.md, contain detailed implementation instructions