New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Prd Close

by vfarcic in vfarcic/dot-agent-deck

Close a PRD that is already implemented or no longer needed. An agent skill from vfarcic/dot-agent-deck.

MITAuto-check passedProduct & Project Management

Install Prd Close

skills CLI
$ npx skills add vfarcic/dot-agent-deck --skill prd-close -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vfarcic/dot-agent-deck prd-close --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vfarcic/dot-agent-deck.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prd-close .claude/skills/prd-close && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prd-close
GitHub stars
109
Token cost
~2.5k tokens
SKILL.md length
901 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Close a PRD that is already implemented or no longer needed. An agent skill from vfarcic/dot-agent-deck.

  • Works in 4 steps: Identify PRD and Reason → Read and Validate PRD → Close It — Issue PRD (SOURCE=issue, or… → …
  • Tasks that involve PRD writing
  • SKILL.md covers When to Use This Command, Usage, Workflow Steps and Example Scenarios, plus 2 more sections
  • Calls gh, git and bash

What it does

Prd Close is an agent skill from vfarcic/dot-agent-deck. Close a PRD that is already implemented or no longer needed

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing. It works with GitHub. The repository describes itself as: A rich terminal dashboard for monitoring and controlling multiple AI coding agent sessions. The licence is MIT.

When your agent uses it

  • Tasks that involve PRD writing

Example prompts

  • “/prd-close”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Identify PRD and Reason
  2. Read and Validate PRD
  3. Close It — Issue PRD (SOURCE=issue, or none)
  4. Close It — File PRD (SOURCE=file)

What it can do on your machine

Read from SKILL.md and the folder at commit 793c0d6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • cli.github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prd Close loads about 2.5k tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 901 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~17
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vfarcic/dot-agent-deck at commit 793c0d6, republished under its MIT licence (© vfarcic). 901 words, ~2,535 tokens.

Download SKILL.mdSave it as .claude/skills/prd-close/SKILL.md (or your agent's skills folder).
name
prd-close
description
Close a PRD that is already implemented or no longer needed
user-invocable
true

Close PRD

Close a PRD that is already implemented (in previous work or external projects) or is no longer needed. This workflow records why, closes the GitHub issue, and — for an older PRD that has a file — archives the file.

Where the PRD lives. Since issue #1591 a new PRD is its GitHub issue, and closing it is closing the issue with a closing comment: no file move and no commit. An older PRD keeps its prds/<n>-*.md file, and archiving that file is a commit — which here goes through a PR, because main is protected (CLAUDE.md rule 8): a direct push is refused with GH013 (or, for an admin, silently bypasses the review). bash .claude/skills/prd-start/prd-source.sh <n> says which case you are in, and ../prd-start/issue-prd.md has the issue conventions.

When to Use This Command

Use /prd-close when:

  • ✅ PRD functionality is already implemented in a separate project or previous work
  • ✅ PRD is no longer relevant (superseded, requirements changed, out of scope)
  • ✅ PRD requirements are satisfied by existing functionality
  • ✅ No new code implementation is needed in this repository

DO NOT use /prd-close when:

  • ❌ You just finished implementing the PRD (use /pr-create instead)
  • ❌ PRD has active implementation work in progress
  • ❌ There are uncommitted code changes that need to be part of a PR

Usage

bash
# Interactive mode - will prompt for PRD number and closure reason
/prd-close

# With PRD number
/prd-close 20

# With PRD number and reason
/prd-close 20 "Already implemented by PRs #<a> and #<b>"

Note: If any gh command fails with "command not found", inform the user that GitHub CLI is required and provide the installation link: https://cli.github.com/

Workflow Steps

Step 1: Identify PRD and Reason

If PRD number not provided:

  • Check conversation context for recent PRD discussion
  • Check git branch for PRD indicators (e.g., feature/prd-X)
  • If unclear, prompt user for PRD number

Closure Reason Categories:

  • Already Implemented: Functionality exists in external project or previous work
  • No Longer Needed: Requirements changed, out of scope, or superseded
  • Duplicate: Another PRD covers the same functionality
  • Deferred: Moved to future version or different project

Required Information:

  • PRD number
  • Closure reason (brief description)
  • Implementation reference (if already implemented): link to repo, PR, or documentation
Step 2: Read and Validate PRD

Locate it with bash .claude/skills/prd-start/prd-source.sh [number], then read it: the file it names for SOURCE=file, or the issue body and its collaborator comments for SOURCE=issue. For SOURCE=none the issue carries no PRD; closing it is then an ordinary issue close, which this skill can still do through the issue path below, but say so to the user.

Validation checks:

  • PRD exists and is readable (its file, or its issue)
  • Confirm with user that this PRD should be closed
  • Verify closure reason makes sense given PRD content
  • Ask user for implementation evidence (if "already implemented")

Present PRD summary to user:

markdown
## PRD #X: [Title]
**Status**: [Current Status]
**Created**: [Date]

**Summary**: [Brief description of what PRD requested]

**Proposed Action**: Close as [reason]
**Implementation Reference**: [If applicable]

Proceed with closure? (yes/no)
Step 3: Close It — Issue PRD (SOURCE=issue, or none)

No file, no branch, no commit.

  1. Post the closure comment — the Step F4 template below, headed ### PRD closed — [YYYY-MM-DD] instead, and with its ### Files section replaced by "PRD: this issue's body". Write it to .dot-agent-deck/prd-[number]-comment.md with your file-writing tool and post it with gh issue comment [number] --body-file .dot-agent-deck/prd-[number]-comment.md (../prd-start/issue-prd.md, "Comments").
  2. Close the issue with the reason that matches:
    bash
    gh issue close [number] --reason completed          # Already Implemented
gh issue close [number] --reason "not planned"      # No Longer Needed / Deferred
gh issue close [number] --duplicate-of [other]      # Duplicate
  3. Leave the body as it is. It is the PRD as it stood when it closed, and the closing comment says why.
Step 4: Close It — File PRD (SOURCE=file)
Show full SKILL.md (370 more words)Show less
F1: Update PRD File

Update the PRD metadata:

Metadata Updates:

markdown
**Status**: Complete [or] No Longer Needed [or] Duplicate
**Last Updated**: [Current Date]
**Completed**: [Current Date] [or] **Closed**: [Current Date]
F2: Move PRD to Archive

Work on a branch, never on main (CLAUDE.md rule 1 says to ask whether the user wants a worktree or a branch). Move the PRD file to the done directory and update roadmap:

bash
git mv prds/[number]-[name].md prds/done/

Note: If the move fails because prds/done/ doesn't exist, create it with mkdir -p prds/done and retry.

Update ROADMAP.md (if it exists):

  • Check if docs/ROADMAP.md exists
  • Remove the closed PRD from the roadmap (search for "PRD #[number]")
  • Remove the entire line that references this PRD
  • Closed PRDs should not appear in future roadmap as they're no longer being worked on
F3: Update GitHub Issue

Update issue description with new PRD path and status (the link resolves once the PR merges):

bash
gh issue edit [number] --body "$(cat <<'EOF'
## PRD: [Title]

**Problem**: [Original problem statement]

**Solution**: [Original solution statement]

**Detailed PRD**: See [prds/done/[number]-[name].md](./prds/done/[number]-[name].md)

**Priority**: [Original Priority]

**Status**: ✅ **[COMPLETE/CLOSED]** - [Brief reason]
EOF
)"
F4: Record the Closure on the Issue

Post the comprehensive closure comment now, but do not close the issue here: the PR's Closes #[number] closes it when the archival merges, so the issue and the file cannot disagree about whether the PRD is closed.

bash
gh issue comment [number] --body "$(cat <<'EOF'
## ✅ PRD #[number] Closed - [Reason Category]

[Detailed explanation of why PRD is being closed]

### [If "Already Implemented"]
**Implementation Details**

This PRD requested [functionality]. **All core requirements are satisfied** by [implementation reference].

| Requirement | Implementation | Status |
|-------------|----------------|--------|
| [Requirement 1] | [Where implemented] | ✅ Complete |
| [Requirement 2] | [Where implemented] | ✅ Complete |

**Implementation Reference**: [Link to project/repo/PR]

[If there are gaps]
**Not Implemented** (deferred or out of scope):
- [Feature X] - [Why not needed or deferred]

### [If "No Longer Needed"]
**Reason for Closure**

[Explain why requirements changed, what superseded this, or why it's out of scope]

**Alternative Approach**: [If applicable]
[What replaced this PRD or how needs are met differently]

### Files

**PRD Location**: `prds/done/[number]-[name].md`
**Status**: [Complete/Closed]
**Closed**: [Date]
EOF
)"
F5: Commit on a Branch and Open a PR

Run the gates CLAUDE.md rule 2 names before committing, then:

bash
git add prds/
git status   # only the moved PRD and its in-repo link fixes

git commit -m "docs(prd-[number]): close PRD #[number] - [brief reason]

- Moved PRD to prds/done/ directory
- Updated PRD status to [Complete/Closed]
- [Implementation details or reason]

Closes #[number]"

Then run /pr-create, with Closes #[number] in the PR body. No [skip ci]: the required checks have to report for the PR to merge.

Example Scenarios

Example 1: Already Implemented by Earlier Work
bash
/prd-close 20 "Implemented by PRs #<a> and #<b>"

Closure Comment:

markdown
## ✅ PRD #20 Closed - Already Implemented

This PRD requested exporting a session's history so it can be shared or archived.
**All core requirements are already implemented** by work that shipped under other
issues, in PRs #<a> and #<b>.

| Requirement | Implementation | Status |
|-------------|----------------|--------|
| Export a session's history | PR #<a> | ✅ Complete |
| Choose the export format | PR #<a> | ✅ Complete |
| Export from the desktop app | PR #<b> | ✅ Complete |

**Not Implemented** (deferred, may be a future PRD):
- Scheduled automatic exports
Example 2: Duplicate PRD
bash
/prd-close 45 "Duplicate of PRD #44"

Closure Comment:

markdown
## 🔄 PRD #45 Closed - Duplicate

This PRD covers the same functionality as PRD #44. Consolidating all work
under PRD #44 to avoid fragmentation.

**Action**: Continue work on PRD #44 instead.
Example 3: No Longer Needed
bash
/prd-close 12 "Requirements changed, out of scope"

Closure Comment:

markdown
## ⏸️ PRD #12 Closed - No Longer Needed

After discussion, this approach no longer aligns with project direction.
Requirements have evolved and this PRD is out of scope.

**Alternative Approach**: Using [different solution/approach] instead.

Success Criteria

Issue PRD: ✅ Closure comment posted on the issue ✅ GitHub issue closed with the matching reason ✅ Nothing committed

File PRD: ✅ PRD file updated with completion/closure metadata ✅ PRD archived to prds/done/ directory, on a branch ✅ GitHub issue updated with new PRD path and the closure comment ✅ PR opened with Closes #[number], so the merge closes the issue

Notes

  • No PR for an issue PRD: closing one is two gh calls and touches nothing in the repository
  • A PR for a file PRD: archiving the file is a commit, and main takes commits only through an approved PR (CLAUDE.md rule 8)
  • Comprehensive documentation: Ensure issue comment clearly explains closure reason
  • Implementation references: Link to external projects, repos, or PRs where functionality exists
  • Gap acknowledgment: Be honest about what's implemented vs. what's missing

© vfarcic, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/prd-close of vfarcic/dot-agent-deck.

Open the folder on GitHubat commit 793c0d6

Compare with similar skills

Prd Close next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prd Close compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prd Close this skillvfarcic/dot-agent-deck109—~2.5kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Ouroboros PM InterviewQ00/ouroboros6.2k1 repos~5.7kAutomated safety check: PassMIT
To Issuessmallnest/pigo475—~1.9kAutomated safety check: PassMIT
Write A Prdbestofjs/bestofjs3.1k1 repos~722Automated safety check: PassMIT
Write Update Tidb Docspingcap/docs616—~2.3kAutomated safety check: PassCustom licence

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub starsUsed in 1 repo~5.7k tokens
    Product & Project ManagementAuto-check passed

  • To Issues

    smallnest/pigo

    Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe).

    475 GitHub stars~1.9k tokensUpdated 25 days ago
    Product & Project ManagementAuto-check passed

  • Write A Prd

    bestofjs/bestofjs

    Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue.

    3.1k GitHub starsUsed in 1 repo~722 tokens
    Product & Project ManagementAuto-check passed

  • Write Update Tidb Docs

    pingcap/docs

    Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions.

    616 GitHub stars~2.3k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Write Product Spec

    bholmesdev/hubble.md

    Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.

    1.5k GitHub stars~966 tokensUpdated 6 days ago
    Product & Project ManagementAuto-check passed

More from vfarcic/dot-agent-deck

All 23 skills in this repo

  • Dispatch Shape

    vfarcic/dot-agent-deck

    Choose the shape of a unit you are about to dispatch in this repo — one agent (--single) or a team (--orchestration '<name') — from divisibility criteria instead of asking, and report the shape you…

    109 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Docs Screenshots Review

    vfarcic/dot-agent-deck

    Check that a change to the user-facing docs covers both clients (the TUI and the desktop app) unless the feature exists in only one, and decide whether it needs a new or updated screenshot, then…

    109 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Dot AI Request Dot AI Feature

    vfarcic/dot-agent-deck

    Generate a feature request prompt for another dot-ai project.

    109 GitHub stars~679 tokensUpdated today
    Auto-check passed

  • PR Create

    vfarcic/dot-agent-deck

    Take committed work from a branch to a verified pull request — push, open the PR, settle CI and the automated review, answer and resolve every finding, and hand off.

    109 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Publish Docs

    vfarcic/dot-agent-deck

    Publish the docs site to GHCR with a main-<sha tag and bump site/helm/values.yaml so Argo CD picks it up — without cutting a SemVer release.

    109 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Run Dot Agent Deck

    vfarcic/dot-agent-deck

    Run, build, smoke-test, and screenshot the dot-agent-deck binary against an isolated sandbox.

    109 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Prd Close

What does Prd Close do?

Close a PRD that is already implemented or no longer needed. An agent skill from vfarcic/dot-agent-deck. Prd Close is an agent skill from vfarcic/dot-agent-deck.

When should I use Prd Close?

Prd Close fits situations like: tasks that involve PRD writing.

How do I install Prd Close in Claude Code?

Run `npx skills add vfarcic/dot-agent-deck --skill prd-close -a claude-code`. Or copy the skill folder (.claude/skills/prd-close in vfarcic/dot-agent-deck) into .claude/skills/prd-close in your project. Claude Code loads it when a task matches its description.

How do I install Prd Close in Codex?

Run `npx skills add vfarcic/dot-agent-deck --skill prd-close -a codex`. Or copy the skill folder (.claude/skills/prd-close in vfarcic/dot-agent-deck) into .agents/skills/prd-close in your project. Codex loads it when a task matches its description.

Can I use Prd Close in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vfarcic/dot-agent-deck --skill prd-close -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prd-close, .gemini/skills/prd-close, .github/skills/prd-close and .opencode/skills/prd-close in your project.

What does Prd Close need to run?

Going by SKILL.md and its folder, Prd Close needs the command-line tools its instructions call (gh, git and bash).

Does Prd Close access the network?

SKILL.md names 1 domain. As links in the text: cli.github.com. This is read from the text; nothing was executed.

Is Prd Close safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prd Close use?

Prd Close is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prd Close use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prd Close?

Skills that share tags, products or a category with Prd Close: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), To Issues (smallnest/pigo, 475 stars) and Write A Prd (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prd Close?

vfarcic (a GitHub user) maintains it in vfarcic/dot-agent-deck, which has 109 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 8, 2026.

Source: vfarcic/dot-agent-deck on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.