phase-start

Orchestrate and verify all tasks in a project phase.

39|5|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/benjaminshoemaker/ai_coding_project_base --skill phase-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-start
Source: https://github.com/benjaminshoemaker/ai_coding_project_base/tree/main/.claude/skills/phase-start
Command: npx skills add https://github.com/benjaminshoemaker/ai_coding_project_base --skill phase-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates and verifies execution of all tasks for a phase from EXECUTION_PLAN.md, ensuring consistent progress and automatic verification.

Core Features & Use Cases

  • Phase orchestration: automatically runs all tasks in a phase, enforces git branching per phase, and records progress.
  • Verification integration: triggers /verify-task after each task and updates phase-state.
  • Context and guardrails: checks prerequisites using AGENTS.md and EXECUTION_PLAN.md, handles blocked tasks and stuck-detection workflows.
  • Use Case: Manage a complex feature rollout across multiple tasks with automatic checkpointing.

Quick Start

Use the phase-start skill to run Phase 1 as part of your project workflow:

  • Ensure you are in the project directory containing EXECUTION_PLAN.md and AGENTS.md
  • Run /phase-start 1
  • Optionally run with Codex: /phase-start 1 --codex
  • After completion, run /phase-checkpoint 1

Frequently Asked Questions about phase-start

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

FAQPage Schema
How do I automate task execution for a project phase using a git workflow?

Phase orchestration automates task execution by running all tasks from EXECUTION_PLAN.md, enforcing git-based phase branching, and recording progress automatically to ensure consistent phase-wide completion.

What is the best way to run automatic verification after each task in a development phase?

Automatic verification triggers /verify-task after each task completes and updates the phase-state, ensuring every executed task meets workflow requirements before moving to the next one.

Do I need an EXECUTION_PLAN.md file to orchestrate phase-based workflows?

Yes, you need EXECUTION_PLAN.md and AGENTS.md in your project directory. These files provide the necessary context, prerequisites, and guardrails for checking blocked tasks and handling stuck-detection workflows.

Can I use Codex to execute tasks within an automated phase orchestration workflow?

Yes, you can request Codex-based execution by appending the --codex flag to the phase-start command, enabling automated task execution through the Codex environment.

How do I handle blocked tasks and stuck-detection during automated phase orchestration?

Phase orchestration handles blocked tasks by checking prerequisites using AGENTS.md and EXECUTION_PLAN.md, applying context and guardrails to manage stuck-detection workflows and maintain phase progress.

What should I do after completing automated task execution and verification for a phase?

After completing task execution and verification, you should run a phase checkpoint to save the phase state, ensuring all automated progress and git branching updates are properly recorded.