prd-clean

Archive merged and invalid user stories from prd.json to prd.archived.json.

4|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/brave-experiments/brave-core-bot --skill prd-clean
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-clean
Source: https://github.com/brave-experiments/brave-core-bot/tree/main/.claude/skills/prd-clean
Command: npx skills add https://github.com/brave-experiments/brave-core-bot --skill prd-clean

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of cleaning up the prd.json file by archiving stories that have been merged or marked as invalid, ensuring the main PRD file only contains active work.

Core Features & Use Cases

  • Automated Archiving: Moves completed (merged) or invalid stories from prd.json to prd.archived.json.
  • In-place Updates: Modifies prd.json directly, keeping it clean and up-to-date.
  • Consolidated Archive: Appends archived stories to an existing prd.archived.json, handling duplicates by prioritizing the latest entry.
  • Use Case: After a sprint, use this Skill to automatically clear out all the stories that were successfully merged, keeping your project's active task list focused and manageable.

Quick Start

Run the prd-clean skill to archive completed stories from the prd.json file.

Frequently Asked Questions about prd-clean

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

FAQPage Schema
How do I archive merged user stories from a prd.json file?

To archive merged user stories from a prd.json file, this Skill filters items by their 'status' field and moves completed or invalid entries to a prd.archived.json file, leaving only active work in the original file.

What is the best way to clean up a JSON PRD file after a sprint?

Cleaning up a JSON PRD file after a sprint involves moving merged and invalid stories to a separate archive. This Skill modifies prd.json directly, ensuring your active task list remains focused and manageable.

How does JSON story management handle duplicate archived entries?

JSON story management handles duplicate archived entries by consolidating them and prioritizing the latest entry. When appending to prd.archived.json, the Skill ensures deduplication to maintain a clean archive.

Does automated PRD archiving modify the original JSON file in place?

Automated PRD archiving modifies the original prd.json file in place. It directly updates the file to remove merged and invalid stories, keeping your active project data up-to-date without manual intervention.

Can I use this to filter user stories based on their status field in JSON?

Yes, you can use this to filter user stories based on their status field in JSON. It processes the JSON data to identify merged or invalid statuses, separating them from active stories automatically.

What happens to invalid stories in prd.json during the archiving process?

During the archiving process, invalid stories in prd.json are moved to a prd.archived.json file. This ensures the main PRD file only contains active work by filtering out stories marked as invalid or merged.