skills.rest
Raynos
RaynosCOMMUNITY
Explore all skills by this author →
𝕏@RaynosGitHub

prd-ripple

Classifies built-system design changes and ripples required updates into the PRD.

1|Updated Jun 29, 2026
Search Tags:#requirements#drift detection#adr#game design#prd#documentation sync#change classification
One-click install
npx skills add https://github.com/Raynos/kami-kakushi --skill prd-ripple-raynos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-ripple
Source: https://github.com/Raynos/kami-kakushi/tree/main/.claude/skills/prd-ripple
Command: npx skills add https://github.com/Raynos/kami-kakushi --skill prd-ripple-raynos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a code change alters a shipped system, narrative beat, or content registry, the product requirements document silently goes stale. This Skill removes the guesswork of deciding which PRD sections need edits by classifying the change and rippling only what that class demands. ## Core Features & Use Cases - Four-way change classification: Sorts any diff into balance number, system/narrative, intent-level, or frontier classes, each with a defined ripple scope. - Drift detection workflow: Runs the prd:drift report to surface spec-altitude gaps between the built game and the PRD, then clears only the gaps the change caused. - Guardrails for autonomy: Stops and routes intent-level changes to a human decision, and prefers transcluded gen-regions over re-typed prose so facts cannot drift again. - Use Case: After tuning a crafting recipe registry entry in src/core/content, use this Skill to classify the edit, write the ADR, update the affected PRD subsection, and verify with prd:drift before committing. ## Quick Start Tell the agent to run the prd-ripple skill on the design change you just committed and update the PRD accordingly.

Frequently Asked Questions about prd-ripple

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

FAQPage Schema
How do I keep a PRD in sync with code changes?▼

Classify each built-system change into balance, system/narrative, intent, or frontier, then edit only the PRD subsections that class demands. Run the prd:drift report afterward to catch any remaining gaps your change introduced.

When does a design change require a PRD edit versus no edit?▼

Balance-number tuning (values only) requires no PRD edit since magnitudes are sim-owned. System or narrative changes require an ADR plus targeted PRD ripple, while intent-level changes stop for a human decision.

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

prd-ripple handles day-to-day Flow 1 design changes with targeted subsection edits. prd-compress is Flow 2, a human-signed event that compresses an entire tier's prose to intent and acceptance criteria after its taste review closes.

Can this skill decide intent-level product changes autonomously?▼

No. Intent-level changes that alter what the game is, such as vision values or acceptance criteria, always stop for a human decision recorded in an ADR. The skill only handles classification and agent-safe ripples.

Why does the prd:drift report not block commits?▼

The report is one-directional (game to PRD) and heuristic, so it warns rather than gates. A pre-commit check prints a reminder when content registries change without PRD edits, but it never blocks the commit.

Related Skills

Explore More Product & Management Skills→
InditexTechInditexTech
195

writing-beats

Guide writers through beat-by-beat narrative construction from raw material.

Official
Intermediate
mpazarynampazaryna
1

prd

Generate a Product Requirement Document from a milestone gap in a project roadmap.

Community
Intermediate
johnatas-henriquejohnatas-henrique

propagate-design-change

Scan ADRs and traceability index to classify GDD change impacts.

Community
Advanced
JoaovsalesJoaovsales
1

prd

Generate structured PRDs, ordered backlogs, and project-context briefings from interview responses.

Community
Advanced