better-skills

better-skills

한국어 문서 (Korean)

An autonomous development pipeline plugin for Claude Code.

Feed it a spec, and it automatically handles planning, TDD development, verification, and skill maintenance.

/dev Implement a user authentication system. I need login, signup, and password reset.

Requirements

• Claude Code CLI must be installed.

Installation

# Install with project scope (available only in the current project)
claude plugin install /path/to/better-skills --scope project

# Install with user scope (available across all projects)
claude plugin install /path/to/better-skills

# Install directly from GitHub
claude plugin install github:ohdowon064/better-skills --scope project

After installation, Claude Code automatically recognizes the skills/ and agents/ directories.

Quick Start

Develop an entire feature end-to-end

# Pass a spec as text
/dev Implement a user authentication system. I need login, signup, and password reset.

# Pass a markdown file
/dev docs/auth-spec.md

# Resume interrupted work
/dev PLAN_auth

You only need to intervene at 3 points:

1. Plan approval — Confirm the phase breakdown is appropriate
2. FAIL action selection — Auto-fix / individual review / skip
3. Unexpected blockers — Decide on resolution

Quick tasks without the full pipeline

# Bug fix
/quick Fix login error message not showing on failure

# Bulk rename
/quick Rename userName to username across src/

# Small feature
/quick Add dark mode toggle button

No phases, no plan document — just fix, verify, commit.

Call individual skills directly

# Create a plan only
/feature-planner

# Update an existing plan
/feature-planner update PLAN_auth

# Mark a plan as complete
/feature-planner complete PLAN_auth

# Run verification only
/verify-implementation
/verify-implementation phase-1
/verify-implementation --current-phase

# Check skills
/manage-skills

# Code review
/code-review
/code-review --staged
/code-review --branch feature/auth

Pipeline Flow

Spec Input → Planning → TDD per Phase → Verification → Code Review → Integration Review → Completion → Skill Cleanup
                │              │            │              │              │
                │              │            │              │              └─ code-reviewer (integration)
                │              │            │              └─ code-reviewer (phase)
                │              │            └─ verify-implementation
                │              └─ RED → GREEN → REFACTOR
                └─ feature-planner

/dev automatically orchestrates this entire flow.

Skills

Skill	Description
/dev	Full pipeline orchestrator. Spec → finished feature, fully automated
/quick	Lightweight tasks without phases. Bug fixes, small features, bulk renames
/feature-planner	Breaks features into 3-7 phases. CREATE / UPDATE / COMPLETE modes
/verify-implementation	Runs verify skills in parallel via subagents, generates unified verification report
/manage-skills	Detects and fixes verify skill drift in response to code changes
/code-review	Code review. Supports recent changes, specific paths, staged, and branch diffs

Subagents

Agent	Role	Used By
codebase-scanner	Unified project environment analysis (structure, tests, linters, CI/CD, git changes)	feature-planner, manage-skills
skill-writer	Creates/updates verify skills (parallel execution)	feature-planner, manage-skills
test-runner	Runs individual verify skills + TDD order validation	verify-implementation
code-reviewer	Design/security/performance review (per-phase + integration)	dev, code-review

Key Concepts

Built-in TDD

TDD is not a recommendation — it's a mandatory pipeline stage.

• Every phase follows the RED → GREEN → REFACTOR cycle
• Test-first order is automatically verified via git history
• REFACTOR effectiveness is quantitatively measured (file length, function count, average function length, duplication)

Skill Lifecycle

Skill status is determined by registry presence:

• In registry = active (target for verify-implementation)
• Not in registry = inactive (history preserved in git)

When a phase completes, verify-phase-N-* skills are consolidated into general verify-* skills (new skill created + old ones removed). Unnecessary skills are deleted from both the registry and filesystem; they can be recovered via git log if needed.

Automatic Exception Suggestions

When you skip an issue during verification, you're immediately asked whether to add that check to the skill's Exceptions. If approved, the skill is auto-updated so the same false positive doesn't recur.