pdlc-os
28 verified skills23 total stars
ship
Run the Operation phase (Ship → Verify → Reflect) for the current feature
testing1
distill
Compress large markdown artifacts into a dense inline digest that preserves every fact, verified by round-trip reconstruction. Use this whenever an agent writes a markdown file that sub-agents will re-read in later sessions.
documentation1
init
Initialize PDLC for this project (run once)
tools1
release
Force-release a stuck roadmap-level feature claim (admin command)
data-ai1
doctor
Comprehensive health check of PDLC state, docs, tasks, and code alignment
development1
hotfix
Emergency compressed build-ship cycle for production issues
development1
build
Run the Construction phase (Build → Review → Test) for the current feature
development1
override
Bypass the deploy-before-Operation guardrails block with a single confirmation
devops1
pause
Pause the current feature and save full state for later resume
tools1
skills/variant-convergence
# Variant Convergence **Topic slug:** `variant-convergence` **Triggers:** - **Inception path — Brainstorm Design Step 10.7:** after Step 10.6 (Design-Laws Audit) completes, before Step 11 (PRD design-doc link updates) and the Step 12 design approval gate. Variants are HTML mockups Muse generates. - **Construction path — Build Review Step 12.5:** after Party Review (Step 12) writes its review file and Muse appends the *As-Built Audit* section to `ux-review.md`, before the Step 13 Review approval
development1
skills/reflect
# Retrospective Protocol ## When this skill activates Activate at the start of the **Reflect sub-phase** of Operation, after the Verify sub-phase is complete and the human has signed off on smoke tests. This skill generates the full retrospective for the completed feature cycle — from Inception through Ship. Before starting, gather all required inputs: - The active episode file: `docs/pdlc/memory/episodes/[episode-id].md` - The episode index: `docs/pdlc/memory/episodes/index.md` - The PRD: `d
testing1
resume
Resume a paused feature from its saved checkpoint
testing1
skills/safety-guardrails
# Safety Guardrails — Reference ## When this skill activates This skill is the canonical reference for PDLC's safety model. It is consulted by: - The PreToolUse guardrails hook (`hooks/pdlc-guardrails.js`) on every Bash, Edit, and Write tool call. - The `/override` command, when a user wants to bypass the deploy-before-Operation block. - Every other PDLC skill, when surfacing intent before a potentially-dangerous action (see "Agent norms" below). When in doubt about what the guardrails hook
tools1
rollback
Revert a shipped feature and conduct a post-mortem
tools1
skills/test
# Test Execution Protocol ## When this skill activates Activate at the start of the **Test sub-phase** of Construction, after the Review sub-phase is complete and the human has approved the review file. This skill governs the full test execution run for a completed Beads task. Before starting, read `docs/pdlc/memory/CONSTITUTION.md` — specifically the "Test gates" section. This defines which layers are required to pass before Operation can begin, and which layers (if any) are pre-configured a
development1
abandon
Abandon the current feature and clean up all artifacts
tools1
skills/review
# Multi-Agent Code Review ## When this skill activates Activate at the start of the **Review sub-phase** of Construction, immediately after all tests for the active Beads task have passed. Do not run review before tests pass — this is a hard ordering constraint. This skill governs one full review cycle per task. If the human requests revisions after reading the review file, re-run only the affected reviewer domains (or all, if the change is broad), regenerate the review file, and re-present f
development1
skills/repo-scan
# Repo Scan — Brownfield Initialization ## When this skill activates During `/setup` when the repository contains existing source code (brownfield project). The goal is to deeply review the existing codebase and produce pre-populated drafts of all memory bank files, so initialization reflects reality rather than starting from blank templates. --- ## Protocol Execute every step below in order. Do not skip any step. Collect all findings before writing any memory files. --- ### Step 1 — Map
development1
brainstorm
Run the Inception phase for a feature (Discover → Define → Design → Plan)
data-ai1
whatif
Explore a hypothetical scenario with a read-only team analysis
research1
decide
Record an architectural or product decision in the PDLC Decision Registry
testing1
night-shift
Run a feature autonomously from approved-PRD to shipped, evaluated by a per-turn Sentinel hook. Requires bypass-permissions mode and Agent Teams mode.
data-ai1
condense
Syntactic compression ruleset for prose. Drops articles, filler, pleasantries, hedging, imperative softeners, and connective fluff without modifying code, paths, IDs, numbers, or proper nouns. Invoked by `distill` as its Pass 1 pre-compression step; also usable standalone when a prose block needs to shrink in place without restructuring.
development1
decision
Record an architectural or product decision in the PDLC Decision Registry
testing
override-tier1
Override a Tier 1 safety block with double-RED confirmation
tools
writing-clearly-and-concisely
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
testing
skills/tdd
# Test-Driven Development ## When this skill activates Activate during the **Build sub-phase** of Construction whenever a Beads task is claimed and implementation work is about to begin. This skill governs every line of implementation code written during the Build sub-phase. It does not apply to scaffolding (e.g. `npm init`, directory creation) or config-only tasks, but applies to all logic, handlers, routes, components, services, hooks, and utilities. If the task is infrastructure-only (e.g.
development
your-skill-name
One-line description of what this skill does
tools