archive-prd

Archive completed stories from prd.json into .claude/archives and update summaries.

2|Updated Jan 12, 2026

Search Tags:#archive #prd #sprint #token-optimization #data-management #archive-management

Ready to run

npx skills add https://github.com/djnsty23/claude-auto-dev --skill archive-prd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: archive-prd
Source: https://github.com/djnsty23/claude-auto-dev/tree/main/skills/archive-prd
Command: npx skills add https://github.com/djnsty23/claude-auto-dev --skill archive-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives completed stories from prd.json to reduce token usage and keep datasets small and fast.

Core Features & Use Cases

Archive completed stories: classify ACTIVE vs COMPLETED and move completed items to an archive file.
Update main prd.json with a concise summary and keep a QA dataset for re-testing.
Keep only the last 3 sprints active, removing older data from the main file.

Quick Start

Run the archive command to prune prd.json and generate an archive under .claude/archives.

Frequently Asked Questions about archive-prd

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

FAQPage Schema

How do I reduce token usage in prd.json by archiving completed stories?▼

Archiving completed stories from prd.json reduces token usage by classifying items as ACTIVE or COMPLETED, moving completed entries to an archive file under .claude/archives, and replacing them with a concise summary in the main file.

What is the best way to keep only the current sprint active in a product requirements document?▼

The best way to keep only the current sprint active is to apply an automated archiving workflow that removes older sprint data from the main prd.json file, retaining only the last 3 sprints to keep datasets small and fast.

How does archiving completed stories affect QA data for re-testing?▼

Archiving completed stories maintains QA data for re-testing by moving full story details to archive files while keeping a summarized archive section in the main prd.json, ensuring test data remains accessible without increasing token load.

Can I validate prd.json file size and integrity after archiving completed sprints?▼

Yes, the archiving process validates the resulting prd.json file size and integrity after classifying active versus completed stories, creating archive files, and updating the main file with summarized archive sections.

Do I need any external dependencies to automate prd.json archiving?▼

No external dependencies are required to automate prd.json archiving. The process reads the file, classifies stories, creates archives under .claude/archives, and updates the main file independently.