pdda-eod

Reconcile project documentation, roadmap pointers, and GitHub issue states.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of reconciliation drift between project documentation, GitHub issues, and the actual state of the repository, ensuring that work is only marked as complete when it has been verified and delivered.

Core Features & Use Cases

  • Iteration Wrap: Automates the end-of-work-unit process, including updating changelogs and roadmap pointers.
  • Issue Reconciliation: Safely synchronizes GitHub issue states with project documentation status, preventing premature closure of tasks.
  • Delivery Verification: Guides the operator through a safe, propose-then-confirm workflow for committing, pushing, and PR management.

Quick Start

Run the pdda-eod skill to reconcile your current project documentation with your GitHub issues and finalize your end-of-day status report.

Frequently Asked Questions about pdda-eod

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

FAQPage Schema
How do I automate GitHub issue reconciliation with project documentation?

Automate GitHub issue reconciliation by using a workflow that synchronizes issue states with project documentation status, preventing premature task closure. This ensures work is only marked complete when verified and delivered.

What is the best way to wrap up an iteration and update roadmap pointers?

Wrapping up an iteration requires automating the end-of-work-unit process, which includes updating changelogs and roadmap pointers. This verifies delivery integrity before finalizing the repository state.

Do I need local git access to reconcile project documentation and GitHub issues?

Yes, local git access is required to perform status checks and propose repository mutations. Optional GitHub CLI authentication can also be used to safely synchronize issue states with project documentation.

How does delivery verification work for end-of-iteration repository commits?

Delivery verification uses a propose-then-confirm workflow to safely guide operators through committing, pushing, and PR management. This prevents reconciliation drift between documentation and the actual repository state.

Why does my project documentation drift from GitHub issue states after delivery?

Documentation drift happens when project documentation, GitHub issues, and the repository state fall out of sync. Reconciliation automation safely synchronizes these elements, ensuring tasks are only marked complete upon verified delivery.

Can I use GitHub CLI to verify project delivery status before closing issues?

Yes, optional GitHub CLI authentication enables status checks to verify project delivery status. This ensures GitHub issue states are safely synchronized with your project documentation before closure.