prd-compress

Compresses a PRD tier's prose into intent summaries, acceptance criteria, and pointers with verbatim archival.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/Raynos/kami-kakushi --skill prd-compress-raynos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-compress
Source: https://github.com/Raynos/kami-kakushi/tree/main/.claude/skills/prd-compress
Command: npx skills add https://github.com/Raynos/kami-kakushi --skill prd-compress-raynos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Signed product requirement documents accumulate verbose prose that duplicates what the built code already expresses, making the PRD expensive to maintain and prone to drift. This Skill runs the once-per-tier compression sweep that reduces a tier's fat prose down to intent, acceptance criteria, and pointers while preserving the original text verbatim in an archive. ## Core Features & Use Cases - Gated compression sweep: Runs only after the tier's human taste review (HR-item) closes, and drafts surgical subsection-level edits across PRD sections rather than whole-section rewrites. - Verbatim archival: Moves demoted text unchanged into a dated archive file with a forward pointer, so the reasoning behind decisions is never lost. - Human-approved landing: Files the sweep as a reel-back plan plus an HR-item, and lands the result as a single commit only after human approval. - Use Case: After the T0 milestone demo's taste review closes, invoke this Skill to compress PRD sections 2-6 into intent plus acceptance criteria, archive the original prose, and insert generated regions where the build matches end-state intent. ## Quick Start Ask the AI to run the prd-compress sweep for tier T0 now that its taste review HR-item has closed.

Frequently Asked Questions about prd-compress

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

FAQPage Schema
How do I compress a PRD tier without losing information?

Run the compression sweep only after the tier's taste review HR-item closes. It drafts intent summaries, acceptance criteria, and pointers for each subsection, archives the original prose verbatim to a dated file, and lands the change as one commit after human approval.

When is the prd-compress skill allowed to run?

It is dormant until the tier's human taste review item in review.md closes, such as HR-1 for the T0 demo. Code shipping alone is not the trigger; if the HR-item is still open, the sweep must stop.

What is the difference between prd-compress and prd-ripple?

prd-compress handles the once-per-tier full compression event that reduces signed canon to intent and acceptance criteria. prd-ripple handles Flow 1, the per-change propagation when you make a single design change rather than compressing a whole tier.

Can I rehearse the PRD compression without changing canon?

Yes. Copy one PRD subsection to the git-ignored tmp directory, produce its compressed draft and verbatim archive file there only, and diff the result. Nothing in canon moves until a real HR-item-gated, human-approved sweep runs.

How does the sweep verify the compression preserved content?

It diffs in text mode with word-diff against HEAD so binary output cannot produce a false-clean result, asserts the archived verbatim file is NUL-free, and counts prose width in characters rather than bytes to handle CJK text correctly.