OpenSkillIndex← back to search
claude-codedevelopment

Claude-skill-registry describe-good-phase

Phase sizing, scope boundaries, and anti-patterns. Load when evaluating whether a phase is well-formed or needs splitting.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/describe-good-phase" ~/.claude/skills/majiayu000-claude-skill-registry-describe-good-phase && rm -rf "$T"
manifest: skills/data/describe-good-phase/SKILL.md
tags
#phase-evaluation#iteration-planning#task-splitting
source content

What Makes a Good Phase

A Phase is:

  • Small enough to complete in one tight iteration loop
  • Large enough to produce visible, testable progress
  • Reviewable against explicit acceptance criteria
  • Internally coherent, with one primary intent

A Phase is NOT:

  • An open-ended milestone
  • A roadmap
  • A grab-bag of unrelated tasks
  • A substitute for architecture decisions

If a requested Phase is too large, split it into multiple sequential Phases.