convez.ai
SkillProdutividadeAvançado
kanfu-panda

PDLC Skills — Workflow de Desenvolvimento Completo

kanfu-panda/pdlc-skills

Ciclo de vida completo de produto com contratos obrigatórios e artefatos auditáveis

Ver no GitHub
BomPluginScore · de 0 a 100

Skill com 31 comandos slash que implementa um ciclo de vida completo de desenvolvimento de produtos (PRD → TDD → implementação → review → ship) no Claude Code. Força contratos duros para persistência de artefatos, testes antes do código e auto-verificações, eliminando entregas vagas e sem auditoria.

Instalação

$npx convez-ai kanfu-panda/pdlc-skills

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
18
Forks
2
Acompanhando
4
Saúde
100%
Último commit
há 5 dias
Versão
v1.7.17
Issues abertas
1
Contribuidores
2

Casos de uso

  • Gerenciar fluxos de features de ponta a ponta com estado persistente
  • Garantir TDD real com testes falhando antes de implementação
  • Manter PRD, design, testes e código sincronizados em arquivos auditáveis
  • Automatizar revisão de código e auto-reparo com gates entre estágios

Veredito

Ferramenta madura e bem-estruturada que converte conversas vagas em artefatos duros com ciclo de vida rastreável. Excelente para quem quer rigor de engenharia em workflows IA, mas requer disciplina e Claude Code para funcionar.

README

A tradução para o português deste README ainda está na fila.

PDLC Plugin

English · 中文

CI License: MIT Version Claude Code

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

PDLC is a Claude Code plugin that gives Claude a complete Product Development Life Cycle workflow — 33 standardized stages exposed as slash commands /pdlc-feature, /pdlc-prd, /pdlc-tdd, /pdlc-implement, /pdlc-review, /pdlc-ship, etc.

Each stage enforces hard contracts (artifacts persisted to docs/, per-feature state machine, tests-before-code, mandatory self-check, single-shot auto-repair) so AI-driven engineering produces real, auditable files instead of chat-only output.

Currently Claude Code only. The plugin lives at ~/.claude/plugins/pdlc/ after install.


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 contractWhat 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 implementationReal TDD red-light gate, not a suggestion
Each stage runs a self-check before handing offCatch drift at stage boundary, not in review
Auto-repair runs at most onceNo infinite "fix → check → fix" loops
Each stage declares its next_stepMulti-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-01 (user-auth-phone)
→ Stage 1: writing PRD
   ✓ docs/01_requirements/prd/F20260502-01-user-auth-phone-prd.md
   ✓ self-check 8/8 passed
→ Stage 2: technical design
   ✓ docs/02_design/api/F20260502-01-user-auth-phone-api.md
   ✓ docs/02_design/database/F20260502-01-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-01-user-auth-phone-review.md
→ Stage 6: handoff
   📦 docs/.pdlc-state/F20260502-01.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:

claude plugin marketplace add kanfu-panda/pdlc-skills
claude plugin install pdlc@pdlc-skills

For contributors / template customization

git clone https://github.com/kanfu-panda/pdlc-skills.git
cd pdlc-skills
# edit references/templates/*.md or skills/pdlc-*/SKILL.md
bash install.sh --global   # installs from your local clone

Verify the install

claude plugin list | grep pdlc
# expected: pdlc@pdlc-skills  Version: 1.1.0  Status: ✔ enabled

In Claude Code (after restarting the session), type / and start typing pdlc- — you should see all 33 sub-commands (/pdlc-feature, /pdlc-prd, /pdlc-tdd, ...) in autocomplete.


Stage catalog (three layers)

Layer 1 · Entry points (3)

One-sentence prompts drive the whole chain.

Slash commandPurpose
/pdlc-featureEnd-to-end new feature (PRD → Design → TDD → Implement → Review → Ship)
/pdlc-fixEnd-to-end bug fix (locate → reproduce → fix → test → document)
/pdlc-statusShow the project's PDLC state at a glance

Layer 2 · Stages (11)

Use when you want fine-grained control over one stage.

Slash commandPurpose
/pdlc-prdAuthor a PRD
/pdlc-designTechnical design
/pdlc-tddWrite failing tests first
/pdlc-implementImplement code against the design
/pdlc-reviewCode + doc review
/pdlc-e2eEnd-to-end tests
/pdlc-refactorRefactor code
/pdlc-shipRelease workflow (tests → VERSION → CHANGELOG → tag → CI)
/pdlc-deployDeployment doc
/pdlc-retroIteration retrospective with trend comparison
/pdlc-taskIn-stage task tracking

Layer 3 · Tools (19)

Specialized stages you can invoke explicitly.

  • 🎨 Design (4): /pdlc-ui-design · /pdlc-ui-design-pro · /pdlc-db-design · /pdlc-arch
  • 🔍 Quality (3): /pdlc-lint · /pdlc-perf · /pdlc-security
  • 🔧 Engineering (7): /pdlc-code-gen · /pdlc-add-service · /pdlc-add-app · /pdlc-api-mock · /pdlc-db-migrate · /pdlc-i18n · /pdlc-changelog
  • 🔗 Governance (2): /pdlc-standard · /pdlc-relate
  • 🏗️ Project lifecycle (3): /pdlc-bootstrap · /pdlc-adopt · /pdlc-onboard

3-step quick start

  1. Install (one-line, no clone):
    curl -fsSL https://raw.githubusercontent.com/kanfu-panda/pdlc-skills/main/install.sh | bash -s -- --global
    
  2. Ship a feature: in Claude Code, run /pdlc-feature add a captcha to login
  3. Fix a bug: /pdlc-fix the pagination crash on empty lists

Check progress anytime: /pdlc-status.


Target-project contract

When a stage runs, it reads and writes these paths in your project:

docs/ARCHITECTURE.md                                        # surface · whole-system overview (pdlc-arch, in-place)
docs/GLOSSARY.md                                            # surface · project vocabulary
docs/00_standards/                                          # surface · team conventions (pdlc-standard; read by prd / implement / tdd / code-gen / onboard)
docs/01_requirements/prd/                                   # PRDs
docs/02_design/{api,database,architecture,ui-ux}/           # technical design
docs/03_development/                                        # developer manuals (onboard writes here)
docs/04_testing/{unit-tests,e2e-tests,defects,security,perf}/   # tests & defects
docs/05_deployment/                                         # deployment docs
docs/06_tasks/                                              # in-stage task tracking
docs/07_reviews/{doc,code,design,retro}/                    # review records
docs/.pdlc-state/<feature-id>.json                          # state machine + relations (one per feature, e.g. F20260419-01.json)
docs/.pdlc-state/_relations.json                            # auto · reverse index of feature relations (pdlc-relate)
docs/.pdlc-state/_graph.md                                  # auto · mermaid relation graph

Document templates

references/templates/ ships 11 standard document templates that Claude fills in per feature:

  • prd-template.md — Product Requirements Document
  • api-design-template.md — API design
  • arch-design-template.md — Architecture design (per-feature, ledger)
  • architecture-overview-template.md — Whole-system architecture overview (surface)
  • db-design-template.md — Database schema design
  • db-migrate-template.md — DB migration script
  • test-plan-template.md — Test plan
  • deploy-doc-template.md — Deployment manual
  • changelog-template.md — Changelog entry
  • glossary-template.md — Project glossary (surface)
  • adopt-report-template.md — Legacy-project adoption report

The Iron Law

Every Layer 1 / Layer 2 stage that produces artifacts enforces five invariants. Read-only stages (such as /pdlc-status) are exempt.

  1. Persist to disk — every artifact is a real file, not just chat output
  2. Update the state machine — every completed stage writes docs/.pdlc-state/<feature-id>.json
  3. Tests first — code cannot be implemented until a failing test exists (TDD red light)
  4. Self-check — every stage runs a self-audit before handing off
  5. One-shot repair — auto-fix loops run at most once; stubborn failures get flagged for humans

Questions / discussion

For usage questions, design discussions, or "is this a bug or am I holding it wrong" — please use GitHub Discussions rather than opening an Issue.

For confirmed bugs and feature requests, open an Issue with the bundled templates.

For private security concerns, see SECURITY.md.


Development

Run the tests locally:

bash tests/frontmatter-check.sh   # validate every sub-skill's frontmatter
bash tests/install-smoke.sh       # end-to-end install + layout checks

See CONTRIBUTING.md for PR workflow and coding conventions.

User manual: docs/usage-guide.md · Release notes: CHANGELOG.md.


💖 Support this project

PDLC is built and maintained in spare time. If it saves you hours (or sanity), consider supporting its development.

Donation channels:

  • 🇨🇳 Afdian (爱发电) — for users in China; Alipay / WeChat Pay; native support for monthly tiers and one-time tips.
  • 🌍 PayPal — for international users; any amount, one-time.

Tiers (Afdian — choose monthly or one-time at the same amount):

TierAfdianPayPal equivalentWhat you get
☕ Tip¥10 one-time$1+ one-timeThank-you. Not listed.
🌱 Backer¥30/month$5+ one-timeYour name on SPONSORS.md
🌳 Sponsor¥66/month$20+ one-timeName + avatar + link on SPONSORS.md
🏢 Enterprise¥888/month$100+/monthLogo + link at the top of README.md

If you donate via PayPal, please drop your GitHub handle in a SPONSORS issue so we can add you to the list. The list is updated monthly — see SPONSORS.md.


License

MIT — use it, fork it, ship it.

Ver o original no GitHub

Bom para

Relacionados