execute-phased-plan

Execute multi-phase software development plans with phase-boundary stops and handover prompts.

Updated Apr 17, 2026

Search Tags:#automation #workflow #planning #development #context #handover

Ready to run

npx skills add https://github.com/xinye1/xl-skills --skill execute-phased-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: execute-phased-plan
Source: https://github.com/xinye1/xl-skills/tree/main/skills/execute-phased-plan
Command: npx skills add https://github.com/xinye1/xl-skills --skill execute-phased-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents context degradation and quality loss during long, multi-phase development projects by enforcing strict, chat-level pacing and clean handovers between phases.

Core Features & Use Cases

Phase-Boundary Enforcement: Automatically stops execution at the end of a phase to maintain context hygiene.
Structured Handover: Generates self-contained prompts that allow the user to start the next phase in a fresh, optimized chat.
Subagent Orchestration: Integrates with subagent-driven development to ensure each phase is validated against specific exit criteria before moving forward.

Quick Start

Invoke the execute-phased-plan skill to begin executing the implementation plan located at path/to/plan.md starting with the first phase.

Frequently Asked Questions about execute-phased-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain context window efficiency during long-term software development tasks?▼

To maintain context window efficiency during long-term software development tasks, enforce strict phase-boundary stops and generate context-preserving handover prompts. This prevents context degradation by starting each phase in a fresh, optimized chat.

What is the best way to orchestrate multi-phase coding plans with subagent-driven development?▼

The best way to orchestrate multi-phase coding plans with subagent-driven development is to enforce structured handovers. This validates each phase against specific exit criteria before moving forward, ensuring task-specific focus and clean context transitions.

How do I execute a development plan located in a markdown file phase by phase?▼

To execute a development plan located in a markdown file phase by phase, invoke the skill targeting path/to/plan.md. It orchestrates the execution by automatically stopping at phase boundaries to preserve context hygiene.

Why does context degradation cause quality loss in complex, long-running coding workflows?▼

Context degradation causes quality loss in complex, long-running coding workflows because the context window becomes overloaded over time. Enforcing strict, chat-level pacing and clean handovers between phases prevents this degradation and maintains task-specific focus.

Can I use phase-based pacing for automation workflows without defined exit criteria?▼

You cannot use phase-based pacing for automation workflows without defined exit criteria. The mechanism requires adherence to defined exit criteria for each phase to validate subagent-driven development before moving forward.