pdlc

pdlc-skills

English · 中文

Author: kanfu-panda Repo: github.com/kanfu-panda/pdlc-skills License: MIT

pdlc-skills turns AI software engineering into an auditable, on-disk state machine. It's a Claude Code plugin shipping a staged PDLC (Product Development Life Cycle) workflow — PRD → design → TDD → implement → review → ship → retro — where every stage enforces hard contracts (artifacts persisted to docs/, per-feature state machine, tests-before-code, mandatory self-check, single-shot auto-repair), so AI work produces real, reviewable files instead of chat-only output.

Three things fall out of that state machine:

• Auditable — every artifact lands on disk; you git diff exactly what the AI did.
• Autonomous — checks come from real command exit codes (never model self-report), so an autonomous loop can drive tdd → implement → review to convergence unattended, with fail-stop, stuck-stop, and budget guards.
• Portable — the state machine lives in your repo, so it's tool-agnostic. Claude Code has the richest integration (36 slash commands + statusline + in-plugin loop engine); Codex and others drive the same methodology via adapters. See Multi-platform.

---

Why PDLC

Without this plugin, an AI assistant working on a feature typically:

• Says it built the feature, but the PRD lives only in the chat transcript.
• Writes code without writing tests first.
• Skips the design step, which means architectural drift accumulates silently.
• Has no memory between sessions of which stage a feature is in.

PDLC turns those soft conventions into hard contracts:

Hard contract	What it gives you
Every artifact lands on disk under docs/	You can git diff what the AI did
Every stage updates a per-feature state machine	/pdlc-status always knows where you are
Tests must exist (and fail) before implementation	Real TDD red-light gate, not a suggestion
Each stage runs a self-check before handing off	Catch drift at stage boundary, not in review
Auto-repair runs at most once	No infinite "fix → check → fix" loops
Each stage declares its next_step	Multi-stage flows are command-driven, not memorized

---

Quick demo

A typical end-to-end flow looks like this:

$ # In Claude Code:
$ /pdlc-feature add phone-number verification to user login

→ Allocating feature ID F20260502-090000 (user-auth-phone)
→ Stage 1: writing PRD
   ✓ docs/01_requirements/prd/F20260502-090000-user-auth-phone-prd.md
   ✓ self-check 8/8 passed
→ Stage 2: technical design
   ✓ docs/02_design/api/F20260502-090000-user-auth-phone-api.md
   ✓ docs/02_design/database/F20260502-090000-user-auth-phone-db.md
→ Stage 3: TDD red light
   ✓ 14 tests written, all failing as expected
→ Stage 4: implementation
   ✓ 14/14 tests now passing
→ Stage 5: code review + auto-repair
   ✓ 3 lint issues auto-fixed
   ✓ docs/07_reviews/code/F20260502-090000-user-auth-phone-review.md
→ Stage 6: handoff
   📦 docs/.pdlc-state/F20260502-090000.json updated
   👉 Next: /pdlc-ship

Every artifact above is a real file you can git diff. Run /pdlc-status any time to see where each feature stands. (Output above is illustrative — actual Claude Code output is markdown, not ASCII.)

---

Install

One-liner — no clone needed. Pulls the latest published release from GitHub.

# Global (~/.claude/plugins/pdlc/)
curl -fsSL https://raw.githubusercontent.com/kanfu-panda/pdlc-skills/main/install.sh \
  | bash -s -- --global

# Project-scoped (<project>/.claude/plugins/pdlc/)
curl -fsSL https://raw.githubusercontent.com/kanfu-panda/pdlc-skills/main/install.sh \
  | bash -s -- --project /path/to/my-project

That's it. The installer downloads the matching release tarball, extracts it, and copies only the plugin files to your .claude/plugins/pdlc/ directory.

Upgrade

curl -fsSL https://raw.githubusercontent.com/kanfu-panda/pdlc-skills/main/install.sh \
  | bash -s -- --upgrade --global

Uninstall

curl -fsSL https://raw.githubusercontent.com/kanfu-panda/pdlc-skills/main/install.sh \
  | bash -s -- --uninstall --global

Check your version

curl -fsSL https://raw.githubusercontent.com/kanfu-panda/pdlc-skills/main/install.sh \
  | bash -s -- --version

Equivalent native commands

If you'd rather call Claude Code's plugin CLI directly: