strict
The /strict command activates RIPER protocol enforcement, a structured workflow system that constrains Claude's responses into five operational modes (Research, Innovate, Plan, Execute, Review) with specific permitted actions for each. Use this command when working on projects requiring controlled progression through defined stages, from initial research through planning to execution and validation, with built-in safeguards preventing actions outside the current mode.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/tony/claude-code-riper-5/HEAD/.claude/commands/riper/strict.md -o ~/.claude/commands/strict.mdstrict.md
# RIPER STRICT MODE ACTIVATED From this point forward, I MUST follow the RIPER protocol strictly: ## Current Status **MODE**: [NO MODE] - Awaiting mode assignment ## Protocol Rules 1. **Mode Declaration**: Every response begins with `[MODE: X]` or `[NO MODE]` 2. **Mode Transitions**: Only you can authorize mode changes 3. **Mode Restrictions**: Each mode has specific allowed actions 4. **Violation Handling**: Any out-of-mode action triggers a block warning ## Available Commands (RIPER Architecture) To enter a mode, use one of these commands: - `/riper:research` - Enter RESEARCH sub-mode (read-only) - `/riper:innovate` - Enter INNOVATE sub-mode (brainstorming) - `/riper:plan` - Enter PLAN sub-mode (specifications) - `/riper:execute` - Enter EXECUTE sub-mode (requires approved plan) - `/riper:review` - Enter REVIEW mode (validation) Note: RIPER uses 3 consolidated agents with sub-modes for improved performance Or say explicitly: - "Enter RESEARCH mode" - "Enter INNOVATE mode" - "Enter PLAN mode" - "APPROVE PLAN and enter EXECUTE mode" - "Enter REVIEW mode" ## Mode Capabilities | Mode | Read | Write | Execute | Plan | Validate | |------|------|-------|---------|------|----------| | RESEARCH | ✅ | ❌ | ❌ | ❌ | ❌ | | INNOVATE | ✅ | ❌ | ❌ | ❌ | ❌ | | PLAN | ✅ | 📄* | ❌ | ✅ | ❌ | | EXECUTE | ✅ | ✅ | ✅ | ❌ | ❌ | | REVIEW | ✅ | 📄* | ✅** | ❌ | ✅ | *Only plan/review documents in `.claude/memory-bank/` **Only for running tests, not modifications ## Violation Response If I attempt an action outside my current mode: ``` ⚠️ ACTION BLOCKED: Currently in [CURRENT MODE] Attempted action: [WHAT WAS ATTEMPTED] Required mode: [WHAT MODE IS NEEDED] To proceed: Switch to [REQUIRED MODE] mode ``` ## Status RIPER Strict Mode is now ACTIVE. Awaiting mode assignment to begin work. Current context: $ARGUMENTS
Planning and execution phase - specifications and implementation
Research and innovation phase - information gathering and brainstorming
Enter REVIEW mode to validate implementation
List all memories across branches
Recall memories from current branch's memory bank
Save context to branch-aware memory bank
Rebase current branch onto trunk (origin/master or origin/main), predict and resolve conflicts
Enter EXECUTE mode to implement approved plan