pdda

Validate project documentation standards and repository state consistency via shell utilities.

2|Updated Jun 24, 2026

Search Tags:#automation #workflow #documentation #compliance #roadmap #pdda

Ready to run

npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill pdda

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pdda
Source: https://github.com/Hypercart-Dev-Tools/pdda/tree/main/.claude/skills/pdda
Command: npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill pdda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates project drift by enforcing a strict, deterministic contract for project documentation, ensuring that both humans and agents can reliably navigate the repository's current status and roadmap.

Core Features & Use Cases

Deterministic Enforcement: Automatically validates frontmatter, status tables, and roadmap pointers to prevent documentation rot.
Context Re-orientation: Provides an immediate, high-level summary of active work and routing instructions, replacing manual file hunting.
Use Case: Use this at the start of a coding session to verify that your current task is correctly tracked in the project roadmap and that all documentation meets the repository's quality standards.

Quick Start

Invoke the pdda skill to re-orient your session and run the full suite of deterministic repository checks.

Frequently Asked Questions about pdda

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce project documentation standards and prevent documentation rot?▼

To enforce documentation standards and prevent rot, use deterministic shell-based validation to automatically check frontmatter, status tables, and roadmap pointers. This ensures both humans and agents can reliably navigate the repository's current status without manual file hunting.

How do I synchronize project state with my active work tracking and roadmap?▼

Synchronize project state by validating documentation lifecycles, including inbox management and active work tracking. This provides an immediate, high-level summary of active work and routing instructions, ensuring your current task is correctly tracked in the project roadmap.

Do I need a specific repository structure to validate project documentation consistency?▼

Yes, validating project documentation consistency requires a valid PDDA-installed repository structure. This environment must include executable shell utilities to enable deterministic status reporting and strict contract enforcement across the project lifecycle.

What is the best way to re-orient a coding session and verify task tracking?▼

The best way to re-orient a coding session is to invoke deterministic validation at the start. This provides an immediate summary of active work and routing instructions, verifying that your current task is correctly tracked and all documentation meets repository quality standards.

Why does project drift occur and how can I eliminate it?▼

Project drift occurs when documentation contracts are not strictly enforced, causing repository status to become unreliable. Eliminate drift by applying deterministic shell-based validation to frontmatter and roadmap pointers, ensuring both humans and agents navigate current status accurately.

Can I use shell utilities to automate compliance checks for project roadmaps?▼

Yes, you can use executable shell utilities to automate compliance checks for project roadmaps. This deterministic validation automatically enforces strict documentation contracts, preventing documentation rot and ensuring roadmap pointers remain accurate across the repository.