pdlc
A development lifecycle harness: intents become specs, specs become small changes, changes become verified, traceable code.
Plugin pdlc from marketplace pskills in ptetau/pskills. Commands read from the repo's manifest — 13 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
What it installs
Skills (13)
acceptanceWrites, locks, and reviews the acceptance checks of a pdlc intent, before its first change starts. The pdlc:test-writer agent writes black-box checks of each acceptance line, through what a user uses, and an independent reviewer judges them. Use when the user says "/pdlc:acceptance", or when the cha
boardShows the state of pdlc on a board, for example a GitHub project or Linear, through the tracker port. Each intent and each change has one card, in the column for its status. pdlc is the truth, and the board only shows the truth. Use when the user says "/pdlc:board", or wants to update the board. Pas
changeMakes one or more change specs from a ready pdlc intent. Each change covers exactly one job, one capability, or one design spec. Each change lists the interface that its checks are permitted to call, and only the files that it is permitted to touch. Capability changes come before the jobs that need
conventionsMakes or changes a pdlc convention together with the user, and writes it as a design spec. When an existing convention changes, adds one migration intent for each job or capability that the change has an effect on. Use when the user says "/pdlc:conventions", or wants to set or change how the project
dashboardInstalls the optional live dashboard of pdlc. The dashboard-builder agent keeps one HTML page with tasks, questions for the user, deliverables, and anything that is stuck. A rule in the CLAUDE.md of the user tells each session to use the dashboard for all work in progress. Installs only after the us
initPrepares a project of any kind, new or existing, for pdlc. Creates the pdlc folder, maps the existing code with the recon agent, agrees the default conventions with the user, and selects the adapters. Use when the user says "/pdlc:init", "set up pdlc", or wants to start to use pdlc in a project. Wit
intakeTakes one intent into pdlc, and makes spec patches from it: new jobs, new capabilities, new conventions, or changes to existing specs. Marks each new requirement as proposed. Does not write code. Use when the user says "/pdlc:intake", or tells you about something to build or change in a pdlc project
readyMakes sure that the spec patches of a pdlc intent are clear enough to build. Asks the user about each unclear item, one question at a time, looks for contradictions in the specs, and marks requirements ready. Use when the user says "/pdlc:ready", or asks if an intent is ready to build.
shipRuns pdlc from start to end, alone: each stage of the intent and of each change, with the changes stacked and each merge proposed. Continues from the point where it stopped. Use when the user says "/pdlc:ship", "ship it", or wants pdlc to run all the way alone.
showRecords a verified pdlc change, has the recording reviewed, and proposes its merge. Plays each acceptance check in the real app: a browser for web apps, and a terminal for CLIs and libraries. Saves review.gif and the key frames in the folder of the change. A fresh, independent reviewer judges the fr
traceFollows the trace links of pdlc in the two directions. Answers "why does this code exist?": from a file and a line to its commit, requirement, intent, and ticket. Answers "what did this intent change?": the opposite direction. Use when the user says "/pdlc:trace", or asks why some code exists. Also
upgradeBrings the pdlc files of a project up to the installed pdlc version. Refreshes each file that the project did not edit. Keeps each edited file and shows its diff. Records the version, and reports each spec that needs a newer form. Use when the user says "/pdlc:upgrade", "upgrade pdlc", or "update th
verifyExamines a built pdlc change before the merge. Runs each check, and sends one packet for each review remit (specification, security, quality, compliance, privacy) to a fresh, independent reviewer, all at the same time. When all pass, marks the requirements verified. Then /pdlc:show records the chang
Subagents (4)
builderWrites the app code of a pdlc change until its locked checks pass. Does not change checks or pdlc files. The pdlc build skill uses this agent.
reconRead-only scout for pdlc. Maps an existing codebase of any type, or one area of the codebase, into draft job, capability, and design specs. The pdlc init skill uses this agent for a thin map. The pdlc intake skill uses this agent for a deep look at one area.
reviewerIndependent pdlc reviewer. Judges one review packet for one remit (tests, specification, security, quality, compliance, privacy, or visual), and writes the result next to the packet. Sees only its packet. The `/pdlc:acceptance`, `/pdlc:tests`, `/pdlc:verify` and `/pdlc:show` skills use this agent.
test-writerWrites pdlc checks from the specs only, before anyone writes app code. Writes the acceptance checks of an intent, or the component checks of a change. Does not see app code. The pdlc acceptance and tests skills use this agent.
Hooks (12)
- UserPromptSubmit
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/version.py"
- UserPromptSubmit
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/shiplog.py"
- PreToolUse
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/guard.py"
- PreToolUse
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/stdin.py"
- PreToolUse
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/shiplog.py"
- PostToolUse
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/commits.py"
- PostToolUse
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/shiplog.py"
- PostToolUse
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/shiplog.py"
- PostToolUseFailure
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/shiplog.py"
- Stop
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/shiplog.py"
- StopFailure
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/shiplog.py"
- SubagentStop
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/shiplog.py"
Maintain pdlc?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.