rip

Review implementation plans for alignment with PRD requirements and business value.

12|2|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/alexandrbasis/wythm-claude-workflows --skill rip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rip
Source: https://github.com/alexandrbasis/wythm-claude-workflows/tree/main/.claude/skills/rip
Command: npx skills add https://github.com/alexandrbasis/wythm-claude-workflows --skill rip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that technical implementation plans directly support and align with the intended business value and requirements, preventing scope creep and missed objectives.

Core Features & Use Cases

  • Plan Validation: Reviews implementation steps against Product Requirements Documents (PRDs) and business goals.
  • Business Value Alignment: Assesses if each technical step contributes to a user-facing outcome or business objective.
  • Use Case: Before starting development, use this Skill to review your proposed implementation plan for a new feature, ensuring it meets all specified requirements and delivers the expected business value.

Quick Start

Use the rip skill to review my implementation plan located at 'path/to/plan.md'.

Frequently Asked Questions about rip

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

FAQPage Schema
How do I review an implementation plan for business value alignment?

To review an implementation plan for business value alignment, analyze technical steps against PRD requirements to identify scope mismatches and verify each step ties to a user-facing outcome. This prevents scope creep and ensures development meets intended objectives.

What is the best way to validate technical planning against PRD requirements?

Validating technical planning against PRD requirements involves assessing if each technical step contributes to a user-facing outcome or business objective. This process verifies alignment, identifies scope mismatches, and ensures the technical implementation delivers expected business value.

Can I use plan review to check if technical steps support user-facing outcomes?

Yes, plan review checks whether technical steps support user-facing outcomes by analyzing implementation plans against business goals. It verifies each step ties to a specific outcome and uses code verification tools to ensure technical accuracy and requirements alignment.

How do I prevent scope creep when reviewing an implementation plan?

Preventing scope creep during implementation plan review requires identifying scope mismatches between technical steps and business requirements. By verifying each technical action maps to a user-facing outcome, you ensure development directly supports intended business value without unnecessary expansion.

Does requirements alignment verification check existing code during plan review?

Requirements alignment verification uses Grep and Read tools for code verification during plan review. This ensures proposed technical steps in the implementation plan accurately reflect the current codebase and correctly map to PRD requirements and business value objectives.