auto-phase

Name: auto-phase
Availability: InStock
Author: ChazzCoin

Expand phase stubs into complete specs with resolved decisions.

Updated Apr 28, 2026

Search Tags:#autonomy #development-process #ai-assisted #spec-generation #phase-management #phase-walkthrough

Ready to run

npx skills add https://github.com/ChazzCoin/claude-kit --skill auto-phase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: auto-phase
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/auto-phase
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill auto-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically expands every stub in a named phase into a full, implementation-ready spec, removing questions during planning and surfacing decisions as explicit assumptions.

Core Features & Use Cases

Expand each stub into a complete spec with reconnaissance, open questions resolved as decisions, and a recommended working order.
Operate across named phases defined in tasks/PHASES.md, enabling hands-off spec generation for entire phase work.
Accelerate planning and reduce coordination overhead by delivering ready-to-implement specs in a single phase pass.

Quick Start

Activate /auto-phase to autonomously expand every phase stub into a full spec set and propose an execution order.

Frequently Asked Questions about auto-phase

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

FAQPage Schema

How do I autonomously generate implementation-ready specs for a whole development phase?▼

You can autonomously generate phase specs by activating a command that expands every stub defined in tasks/PHASES.md into complete specs without user prompts, resolving decisions automatically as explicit assumptions.

What is autonomous phase spec expansion and how does it handle open questions?▼

Autonomous phase spec expansion is a planning process that fully develops stubs into implementation-ready specifications, automatically resolving open questions by surfacing them as explicit decisions and assumptions within the generated spec.

Do I need a PHASES.md file to use autonomous phase spec generation?▼

Yes, autonomous phase spec generation operates over named phases defined in a tasks/PHASES.md file, requiring this file structure alongside autonomy-rules.md and spec-phase reference rules to function correctly.

Can I automate planning across multiple named phases without manual intervention?▼

Yes, you can automate planning across multiple named phases defined in tasks/PHASES.md, enabling hands-off spec generation that delivers a full spec set and a recommended working order for the entire phase.

What is the best way to reduce coordination overhead during phase planning?▼

The best way to reduce coordination overhead is to use autonomous phase spec generation, which removes planning questions by automatically expanding stubs into complete specs and proposing an execution order in one pass.

Are there limitations to autonomous spec generation for complex phases?▼

A limitation of autonomous spec generation is that it resolves open questions automatically as assumptions, meaning users must review the generated specs to validate these assumptions before implementation begins.