pdda-status

Reconcile GitHub issue states with local project lifecycle documentation.

2|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill pdda-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pdda-status
Source: https://github.com/Hypercart-Dev-Tools/pdda/tree/main/SKILLS/PDDA-STATUS
Command: npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill pdda-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This skill solves the problem of drift between GitHub issue tracking and local project documentation, ensuring that status updates, lifecycle movements, and roadmap pointers remain synchronized without manual oversight.

Core Features & Use Cases

  • Evidence-Based Reconciliation: Cross-references GitHub issue states, commit history, and checklist completion against local project files to calculate a confidence score for proposed changes.
  • Safe Lifecycle Management: Provides a preview-and-confirm workflow for moving documents between lifecycle buckets (e.g., 2-WORKING to 3-COMPLETED) and updating frontmatter status.
  • Use Case: Use this to audit the 10 most recently updated issues in your repository to identify which project documents are ready to be marked as complete or moved to the archive based on actual development activity.

Quick Start

Ask the assistant to reconcile recent GitHub issues against project docs to generate a status matrix and propose necessary document updates.

Frequently Asked Questions about pdda-status

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

FAQPage Schema
How do I reconcile GitHub issue states with local project documentation?

To reconcile GitHub issue states with local project documentation, cross-reference recent issue updates against commit evidence and checklist completion to calculate a confidence score for necessary document mutations.

How does evidence-based reconciliation work for project lifecycle documents?

Evidence-based reconciliation works by cross-referencing GitHub issue states, commit history, and checklist completion against local project files to calculate a confidence score for proposed lifecycle changes.

Do I need the GitHub CLI to synchronize issue tracking with project docs?

Yes, you need the GitHub CLI installed to synchronize issue tracking with project docs, as the skill depends on the gh tool to fetch recent repository issues for deterministic status reporting.

What is the best way to safely move project documents between lifecycle buckets?

The best way to safely move project documents between lifecycle buckets is using a preview-and-confirm workflow that updates frontmatter status only after operator verification of the proposed changes.

Can I audit recently updated GitHub issues to update my project roadmap?

Yes, you can audit the 10 most recently updated GitHub issues to generate a status matrix, identifying which project documents are ready to be marked complete or moved to the archive.

Why does my project documentation drift from actual GitHub development activity?

Project documentation drifts from GitHub development activity when status updates and lifecycle movements occur without synchronized local oversight, requiring automated cross-referencing to maintain alignment.