skills.rest
vfarcic
vfarcicCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dot-ai-prd-close

Close Product Requirement Documents by updating status, archiving files, and managing GitHub issues.

2|Updated Dec 8, 2025
Search Tags:#project management#documentation#workflow automation#github issues#prd#close
One-click install
npx skills add https://github.com/vfarcic/dot-ai-website --skill dot-ai-prd-close
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dot-ai-prd-close
Source: https://github.com/vfarcic/dot-ai-website/tree/main/.claude/skills/dot-ai-prd-close
Command: npx skills add https://github.com/vfarcic/dot-ai-website --skill dot-ai-prd-close

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of closing Product Requirement Documents (PRDs) that are no longer needed or have been implemented, streamlining project management and documentation.

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 Issue Management: Updates and closes associated GitHub issues with detailed closure notes.
  • Use Case: When a PRD's requirements are met by an existing feature or are no longer relevant, use this Skill to formally close it, update its documentation, and inform stakeholders via the GitHub issue.

Quick Start

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

Frequently Asked Questions about dot-ai-prd-close

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

FAQPage Schema
How do I automatically close PRDs and update 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 detailed closure notes to inform stakeholders.

What are the use cases for closing a Product Requirement Document?▼

Closing a Product Requirement Document is necessary when the project requirements have been fully implemented by a feature, are no longer relevant, or the document is identified as a duplicate. This process keeps project documentation streamlined and accurate.

Do I need GitHub CLI to manage PRD workflow automation?▼

Yes, GitHub CLI is required for issue management when automating PRD closure. Git is also necessary for file operations such as moving outdated or completed documents to a designated archive directory.

How do I archive completed product requirement documents?▼

To archive completed product requirement documents, workflow automation tools update the PRD status and use Git file operations to move the documents from their active directory into a designated archive folder.

What is the best way to handle duplicate or unnecessary PRDs in project management?▼

The best way to handle duplicate or unnecessary PRDs is to formally close them by marking their status as 'No Longer Needed', archiving the files, and closing the linked GitHub issues with notes explaining the specific reason for rejection.

Related Skills

Explore More Product & Management Skills→
themachinagodthemachinagod

submit-prds

Submit PRDs and discovery materials to a CI/CD pipeline via GitHub pull requests.

Community
Advanced
seabbsseabbs
7

repo-activity

Analyze GitHub issues, pull requests, and contributor activity to generate markdown reports.

Community
Intermediate
joshukrainejoshukraine
421

plan-phase

Convert product requirements documents into structured development plans and GitHub issues.

Community
Advanced
glhewettglhewett

issues-close

Close TOML issues by updating metadata, appending comments, and committing.

Community
Intermediate