sdd-riper
Lightweight AI Agent Harness for agentic coding: let strong models explore while humans steer with minimal specs, checkpoints, approval, validation, and reverse
What is sdd-riper?
Lightweight AI Agent Harness for agentic coding: let strong models explore while humans steer with minimal specs, checkpoints, approval, validation, and reverse sync.
Overview of sdd-riper
What it is
SDD-RIPER Light is a lightweight AI agent harness designed for agentic coding workflows. It provides a control plane that lets strong models explore and implement code while humans retain ownership of goals, boundaries, permissions, checkpoints, evidence, and acceptance. The harness is repo-native and focuses on keeping work aligned, observable, recoverable, and provable without turning tasks into heavy process theater.
Key features
- Restate First: The agent must restate the task before planning or changing files.
- No Spec, No Code: A minimal source of truth is created or updated before implementation.
- No Approval, No Execute: Explicit human approval is required before code changes or high-impact actions.
- Done by Evidence: Completion must be proven by tests, logs, screenshots, manual checks, or equivalent evidence.
- Reverse Sync: Verified conclusions are written back into the spec, handoff, docs, or project memory when appropriate.
- Supports four complementary skills: sdd-riper-one-light, sdd-riper-one, codemap, and new-chat-ready.
Use cases
- Daily coding, documentation, bugfixes, and ordinary refactors with strong models.
- High-risk work, multi-file refactors, audit, training, or complex handoffs (using the heavier sdd-riper-one skill).
- Navigating unfamiliar codebases, legacy systems, or large modules (using the codemap skill).
- Preparing resume packs for new chats, handoffs, context compression, or recovered sessions (using the new-chat-ready skill).
Getting started
Use this prompt for ordinary coding or documentation work:```textUse sdd-riper-one-light for this task.Do not change files yet.First give me:- your understanding of the task- the core goal for this loop- a minimal spec / summary
- Done Contract: what counts as done, and what proves it- next actions- risks- validation methodWait for my approval before execution.```
License and pricing
The license is not stated.
Based on the project's public README and repository metadata.