Phased Dev Workflow

phased-dev-workflow

A [Claude Code](https://claude.com/product/claude-code) / [Codex CLI](https://developers.openai.com/codex/) skill for feature and bug-fix work: it breaks large changes into reviewable phases, asks before assuming anything, and closes every phase by showing the real code, the reasoning behind it, and the alternatives that were considered.

Companion skill: [`explain-the-code`](https://github.com/Yefee8/explain-the-code) — an on-demand `/explain-the-code` deep dive for when this skill's phase report isn't enough.

What it does

• Asks before assuming. Resolves ambiguity (edge cases, naming, data shape, backward compatibility, etc.) before writing code, instead of guessing.
• Splits non-trivial work into phases. When a change spans multiple areas, bundles unrelated concerns, or would produce a diff too large to review in one pass, it proposes a phase plan and waits for your go-ahead between phases — no auto-continuing.
• Reports properly at the end of every phase, including a small unphased task: what changed, the actual code (not a paraphrase), why that approach was chosen, at least one alternative that was considered, and what's next.

Install

Claude Code

# Personal — available in every project
git clone https://github.com/Yefee8/phased-dev-workflow ~/.claude/skills/phased-dev-workflow

# This project only — from the project root
git clone https://github.com/Yefee8/phased-dev-workflow .claude/skills/phased-dev-workflow

Start a new Claude Code session (or run `/skills` if your version supports it) to pick it up.

Codex CLI

git clone https://github.com/Yefee8/phased-dev-workflow ~/.codex/skills/phased-dev-workflow

Start a new Codex session. Skills are matched automatically against your prompt; if it doesn't trigger, check `codex --help` for a skills-related flag on your installed version.

Update

Since installation is a plain `git clone`, updating is a plain `git pull` from inside the ins