prd-close

Close PRDs by updating status, archiving documents, and managing GitHub issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jeremysball/alfred --skill prd-close-jeremysball
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-close
Source: https://github.com/jeremysball/alfred/tree/main/skills/prd-close
Command: npx skills add https://github.com/jeremysball/alfred --skill prd-close-jeremysball

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of closing Product Requirement Documents (PRDs) that are either already implemented or no longer relevant, ensuring project documentation and issue tracking remain up-to-date.

Core Features & Use Cases

  • Automated Status Updates: Updates PRD status to 'Complete' or 'No Longer Needed'.
  • Archiving: Moves closed PRDs to a designated archive directory.
  • GitHub Integration: Updates and closes associated GitHub issues with comprehensive closure notes.
  • Use Case: You have a PRD for a feature that was implemented in a previous project. Use this Skill to formally close the PRD, archive its documentation, and update the corresponding GitHub issue to reflect its completed status.

Quick Start

Use the prd-close skill to close PRD number 20 with the reason "Already implemented by dot-ai-controller".

Frequently Asked Questions about prd-close

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

FAQPage Schema
How do I automate closing Product Requirement Documents and updating associated GitHub issues?

Automating PRD closure involves updating the document status to Complete or No Longer Needed, moving it to an archive directory, and closing linked GitHub issues with closure notes. This workflow requires the GitHub CLI for issue tracking updates.

What is the best way to archive implemented PRDs in a project management workflow?

Archiving implemented PRDs requires updating their status and moving the documentation files to a designated archive directory. This ensures project records remain accurate while keeping active workspaces uncluttered by completed or no longer relevant requirements.

Does closing PRDs and managing GitHub issues require any specific environment setup?

Closing PRDs and managing GitHub issues requires the GitHub CLI for updating issue states. The process also commits changes directly to the main branch while skipping CI checks, requiring appropriate repository write permissions.

How do I handle duplicate or no longer needed Product Requirement Documents?

Handling duplicate or obsolete PRDs involves marking their status as No Longer Needed and archiving the documentation. Associated GitHub issues are closed with comprehensive notes explaining the resolution context to maintain accurate project tracking.

Why does PRD closure involve direct commits to the main branch?

PRD closure uses direct commits to the main branch with CI skipping to immediately update repository state and archive files. This approach bypasses standard review pipelines to ensure documentation status changes are applied instantly without triggering build workflows.