auto-phase

Execute multi-phase releases from PHASE-PLAN.md with validation and critique gates.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/SamyakJhaveri/loam --skill auto-phase-samyakjhaveri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-phase
Source: https://github.com/SamyakJhaveri/loam/tree/main/seed/.claude/skills/auto-phase
Command: npx skills add https://github.com/SamyakJhaveri/loam --skill auto-phase-samyakjhaveri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomous multi-phase release execution that reads a PHASE-PLAN.md with stages 1-N and executes them end-to-end, applying validation and critique gates, while committing changes with clean scope. Halts only when a validation gate fails twice or a critique surfaces an unresolvable issue. Use for numbered-phase releases, phased restructures, or any task that requires staged automation.

Core Features & Use Cases

  • Stage-driven automation: reads PHASE-PLAN.md and executes each stage with isolated changes.
  • Gate-driven quality: runs /validate and /session-critique between stages, with automatic retry on first failure and halting on second if issues persist.
  • Audit-friendly commits: commits one stage at a time with a clear scope and updates progress tracking.

Quick Start

Place PHASE-PLAN.md at your project root and start the auto-phase workflow to execute all stages.

Frequently Asked Questions about auto-phase

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

FAQPage Schema
How do I automate phased release execution with validation gates between stages?

Automate a multi-phase release by creating a PHASE-PLAN.md at your project root to define stages 1-N, then execute the workflow to process each stage sequentially with validation and critique gates before committing.

What is autonomous multi-phase release execution and how does it handle validation failures?

Autonomous multi-phase release execution reads a PHASE-PLAN.md and applies validation and critique gates between stages. It automatically retries the first validation failure and halts execution only if a second failure or unresolvable critique issue occurs.

Do I need a PHASE-PLAN.md to run staged automation for restructuring tasks?

Yes, you need a PHASE-PLAN.md at your project root to run staged automation. This file defines the numbered phases and clean scope boundaries required for the workflow to implement, validate, and commit each stage in sequence.

Can I use session critique and validate commands to gate commits in a phased workflow?

Yes, the workflow requires access to /validate and /session-critique commands to gate commits in a phased workflow. It runs these checks between stages to ensure quality before committing the isolated changes for each phase.

When should I not use autonomous stage-driven automation for sequential commits?

You should not use autonomous stage-driven automation if your sequential commits cannot be cleanly isolated by stage, or if your project lacks a PHASE-PLAN.md to define the required stage-by-stage execution scope.