agentmods.dev

prd-archive

prd-archive is a skill for Claude Code from jpoutrin/product-forge. It costs 10 tokens per session (1,256 once invoked), scanned A, original, MIT.

A command for filing completed or cancelled product requirements documents (PRDs) in an archive. It adds archive details and moves each document into a year-based folder.

In plain words
What is it for?
Use it to archive eligible PRDs, record why they were archived, calculate linked task completion when available, and handle cancelled projects.
Why use it?
It removes finished or cancelled documents from active work while preserving their history and completion information.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Claude Code.

Part of the product-design plugin — 43 skills, 8 agents shipped together

not rated 15 6mo ago A scan 10 tokens original MIT
View the source file jpoutrin/product-forge
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/jpoutrin/product-forge/prd-archive
Any agent
npx skills add jpoutrin/product-forge --skill prd-archive
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code.

Or install product-design, the plugin that ships this one along with the rest of its 43 skills, 8 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for prd-archive

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/prd-archive.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/prd-archive)
Your own site
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/prd-archive"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/prd-archive.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,256 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.01256
Opus 5 $0.00005 $0.00628
Sonnet 5 $0.00002 $0.00251
Haiku 4.5 $0.00001 $0.00126

Measured 2d ago against content hash f92d9cc714d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

prd-archive scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/product-design/skills/prd-archive/SKILL.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.

prd-archive

Category: Product & Strategy

Usage

prd-archive <prd-file> [--reason <reason>] [--force]

Arguments

  • <prd-file>: Required - Path to the PRD file to archive
  • --reason: Optional - Reason for archiving (default: "Implementation complete" or "Project cancelled")
  • --force: Optional - Archive even if status is not COMPLETE or ARCHIVED

Execution Instructions for Claude Code

When this command is run, Claude Code should:

  1. Read the PRD file and validate it exists
  2. Check current status:
    • If COMPLETE: proceed with archiving
    • If ARCHIVED: warn that it's already archived
    • If other status and no --force: ask for confirmation
  3. If PRD has a linked task file, calculate final completion percentage
  4. Add archive metadata to the PRD:
    • archive_date
    • archive_reason
    • final_task_completion (if applicable)
    • implementation_duration (if dates available)
  5. Determine archive location:
    • Extract year from last_updated or use current year
    • Create path: product-docs/prds/archive/YYYY/
    • For cancelled PRDs: product-docs/prds/archive/YYYY/cancelled/
  6. Move the PRD file to archive location (use git mv if in git repo)
  7. Update status to ARCHIVED
  8. Optionally archive the linked task file to the same location
  9. Create an archive summary file if this is the first archive of the month

Archive Metadata

Add to PRD header before moving:

status: ARCHIVED
archive_date: 2025-01-06
archive_reason: Implementation complete - v1.0 released
final_task_completion: 100%
implementation_duration: 15 days
original_location: product-docs/prds/active/feature-prds/

Archive Directory Structure

product-docs/prds/archive/
├── 2025/
│   ├── Q1/
│   │   ├── completed/
│   │   │   ├── user-auth-frd.md
│   │   │   └── user-auth-frd-tasks.md
│   │   ├── cancelled/
│   │   │   └── experimental-feature-frd.md
│   │   └── 2025-Q1-archive-summary.md
│   └── Q2/
└── 2024/

Output Format

📦 Archiving PRD: user-authentication-frd.md

Current Status: COMPLETE
Task Completion: 100% (20/20 tasks)

✅ Adding archive metadata:
   - archive_date: 2025-01-06
   - archive_reason: Implementation complete - v1.0 released
   - final_task_completion: 100%
   - implementation_duration: 15 days

📁 Moving to archive:
   From: product-docs/prds/active/feature-prds/user-authentication-frd.md
   To: product-docs/prds/archive/2025/Q1/completed/user-authentication-frd.md

📄 Also archiving linked task file:
   To: product-docs/prds/archive/2025/Q1/completed/user-authentication-frd-tasks.md

✅ Archive complete!

📊 Archive Summary:
   - Implementation started: 2024-12-22
   - Implementation completed: 2025-01-06
   - Total duration: 15 days
   - Final status: Successfully delivered

Read the full file on GitHub · 168 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 168 lines · 10 tokens per session scan A f92d9cc714d6

Subscribe to this mod's changes

prd-archive is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 1,256 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Project management
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens