hnaymyh123-henry

Claude Dev Skill — Testing skill for Claude Code

Testing community

A Claude Code custom skill that turns Claude into a Tech Lead — coordinating parallel Worker Agents through a full dev workflow: PRD alignment, architecture, coding, QA, and PR review.

How to install Claude Dev Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open hnaymyh123-henry/claude-dev-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Dev Skill does

A Claude Code custom skill that turns Claude into a Tech Lead — coordinating parallel Worker Agents through a full dev workflow: PRD alignment, architecture, coding, QA, and PR review.

Alternatives in Testing

  • Project PRD — Jesteś doświadczonym menedżerem produktu, którego zadaniem jest stworzenie kompleksowego dokumentu wymagań pro 265 ★
  • Spec Based Claude Code — Implementation of a Spec-Driven Development workflow in Claude Code using custom slash commands 117 ★
  • Spawn Fs Team — Boot a 5-agent full-stack Flotion team as a new workspace in the cmux window (reuse the open window; only crea 107 ★

README

/dev — AI-Assisted Multi-Agent Development SOP for Claude Code

[中文版](./README.zh.md)

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) [![Claude Code](https://img.shields.io/badge/Claude%20Code-compatible-blue)](https://claude.com/claude-code) [![Skill Type](https://img.shields.io/badge/type-slash%20command-purple)](https://docs.anthropic.com/en/docs/claude-code/slash-commands)

A custom skill for [Claude Code](https://claude.com/claude-code) that turns Claude into a **Tech Lead** coordinating multiple AI Worker Agents through a complete software development workflow — from requirements alignment to PR merge.


Why /dev?

Most AI coding tools give you a smart autocomplete. `/dev` gives you an **engineering process**.

Without /dev With /dev
Claude writes code directly in chat Claude acts as Tech Lead — never writes code itself
No structure, easy to lose track 6-phase SOP from PRD to merge
Single-threaded, one thing at a time Multiple Worker Agents develop in parallel worktrees
You catch conflicts at merge time Pre-coding conflict scan catches overlaps before they start
Security review is manual bandit + pip-audit / npm audit run mandatorily before every Review

How It Works

You: /dev I want to build a Todo app with user auth and task management

Claude (Tech Lead)
  │
  ├─ Phase 0 ── Classify request → New Project
  ├─ Phase 1 ── Align on PRD (2-round confirmation)
  ├─ Phase 2 ── Architecture decisions + GitHub Issues
  │
  ├─ Phase 3 ── Spawn Worker Agents (parallel worktrees)
  │              ├─ Worker A: Auth module
  │              ├─ Worker B: Task CRUD API
  │              └─ Worker C: Frontend components
  │
  ├─ Phase 3.5 ── QA Agent static verification
  ├─ Phase 4 ── Code Review + merge (7-item checklist)
  └─ Phase 5 ── Retro + next iteration loop

What It Does

`/dev` is a **multi-agent software development SOP** covering:

  • **Phase