sync-pdlc

sync-pdlc is a skill for Claude Code from tomzx/agents. It costs 44 tokens per session (695 once invoked), scanned A, original, MIT.

A project-maintenance workflow that checks the `.pdlc/` folder against the product's current state and repairs missing structure and context files. PDLC means product development life cycle: the work of deciding what to build and why.

In plain words
What is it for?
Use it to create or repair the `.pdlc/` directory, detect drift in product artifacts, maintain local-state exclusions, and keep the product context files and agent instructions current.
Why use it?
It helps keep product documents aligned with reality and makes missing or outdated planning structure visible without rewriting initiative content.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to create or repair the .pdlc/ directory, detect drift in product artifacts, maintain local-state exclusions, and keep the product context files and agent instructions current.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tomzx/agents/sync-pdlc
View source ↗ tomzx/agents
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add tomzx/agents --skill sync-pdlc
Clone the repo
git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sync-pdlc

README.md
[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/sync-pdlc/github.svg)](https://agentmods.dev/skills/tomzx/agents/sync-pdlc)
Your own site
<a href="https://agentmods.dev/skills/tomzx/agents/sync-pdlc"><img src="https://agentmods.dev/badge/skills/tomzx/agents/sync-pdlc/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sync-pdlc

Your own site · 80×15
<a href="https://agentmods.dev/skills/tomzx/agents/sync-pdlc"><img src="https://agentmods.dev/badge/skills/tomzx/agents/sync-pdlc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 695 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00695
Opus 5 $0.00022 $0.00347
Sonnet 5 $0.00009 $0.00139
Haiku 4.5 $0.00004 $0.00069

Measured 6d ago against content hash 42965a8975ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

sync-pdlc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pdlc/skills/sync-pdlc/SKILL.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sync PDLC

Analyzes the current state of the product/project against .pdlc/ and reconciles it: creates the structure if absent (via initialize-pdlc-directory), detects drift between artifacts and reality, and ensures the PDLC anchor and context files are present and current. Read-mostly; it reports drift and only writes to heal structure, not to rewrite initiative content.

Prerequisites

  • Apply the shared PDLC conventions in skills/pdlc/references/shared.md.
  • Write access to the project root.

Steps

  1. If .pdlc/ does not exist, run initialize-pdlc-directory and then continue.
  2. Verify the directory tree matches the canonical structure (context, initiatives, decisions, learnings, templates). Create any missing subdirectories.
  3. Ensure .pdlc/.gitignore excludes local-only state (state.yml, initiatives/*/progress.md); create or repair it if missing or stale.
  4. Ensure the PDLC anchor exists in the repo's primary agent-instruction file (per references/shared.md); create or refresh it if missing.
  5. Ensure context files exist (product-overview.md, vision.md, goals.md, roadmap.md, vocabulary.md); seed any missing ones from templates without overwriting existing content.
  6. Detect drift:
    • Orphaned initiatives: directories whose artifacts reference phases that have moved on, or that have no decision records.
    • Stale decisions: gate decisions whose verdict no longer matches the artifacts (e.g., a proceed to Define with no prd.md).
    • Missing artifacts: initiatives whose current phase implies an artifact that is absent.
    • Unmirrored writes: when PDLC_DIR is set, context/initiative artifacts missing from the mirror.
  7. Write a reconciliation report to .pdlc/sync-meta.yml (repo-only) plus a human-readable summary. Regress stale gate decisions to pivot where the artifacts no longer support proceed, so the forward loop resyncs them.

Output Format

## PDLC sync

Structure: ok / repaired (<list>)
Anchor: present / created / refreshed
Context files: <missing ones seeded>

### Drift
| Initiative | Finding | Action |
|---|---|---|
| INIT-3 | stale: validate:proceed but no experiment-result.md | regressed to pivot |

### Mirror (PDLC_DIR)
<paths written to repo / mirror / both>

Read the full file on GitHub · 61 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 61 lines · 44 tokens per session scan A 42965a8975ca

Subscribe to this mod's changes

sync-pdlc is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 695 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens