arib-wave-plan

Validate software development wave plans against codebase evidence and adversarial review.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-wave-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arib-wave-plan
Source: https://github.com/AribSudia/claude-code-methodology/tree/main/.claude/skills/arib-wave-plan
Command: npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-wave-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common failure of building software based on guessed requirements by enforcing an adversarial, evidence-based planning phase before any code is written.

Core Features & Use Cases

  • Evidence-Based Planning: Derives requirements directly from the codebase, architecture decisions, and memory files rather than relying on assumptions.
  • Adversarial Review: Uses an independent model to stress-test the plan for edge cases, security gaps, and missing requirements.
  • Merge Governance: Automatically flags waves for human review if an independent model is unavailable, ensuring high-stakes work is never merged without oversight.

Quick Start

Invoke the arib-wave-plan skill with your project goal to generate a locked plan and review log.

Frequently Asked Questions about arib-wave-plan

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

FAQPage Schema
How do I lock software requirements before coding to prevent building the wrong features?

Adversarial requirement locking prevents guessed requirements by validating project goals against codebase evidence and subjecting plans to independent model review. This ensures development tasks are auditable, secure, and compliant before coding begins.

How does adversarial review work for software development planning?

Adversarial review uses an independent model to stress-test your locked plan for edge cases, security gaps, and missing requirements. This ensures all development tasks are auditable and compliant with project-specific merge-hold policies before execution.

What is evidence-based planning and how do I derive requirements from an existing codebase?

Evidence-based planning derives requirements directly from the codebase, architecture decisions, and memory files rather than relying on assumptions. It ensures development tasks are auditable, secure, and compliant with project-specific merge-hold policies.

What happens to merge governance if an independent model is unavailable for plan review?

Merge governance automatically flags development waves for human review if an independent model is unavailable. This ensures high-stakes work is never merged without oversight and maintains compliance with project-specific merge-hold policies.

Can I use workflow automation to enforce merge-hold policies for high-stakes development tasks?

Workflow automation enforces merge-hold policies by automatically flagging waves for human review when an independent model is unavailable. This ensures high-stakes work is never merged without oversight and maintains compliance.