huisezhiyin/sdd-riper

Registry

Summary

SDD-RIPER is a lightweight AI agent harness designed for agentic coding, enabling powerful models to autonomously explore while humans steer through minimal specs, checkpoints, approval, validation, and reverse sync.

Key features

• Checkpoint-driven workflow for safe exploration
• Human approval and validation gates
• Reverse sync for bidirectional code updates
• Minimal specification requirements
• Lightweight harness for agentic coding

Use cases

• Autonomous code generation with human oversight
• Iterative development with checkpoint rollback
• Collaborative AI-human programming sessions
• Spec-driven development workflows

README excerpt

# SDD-RIPER Light: AI Agent Harness [English](./README.md) | [简体中文](./README.zh-CN.md) > Let the model move the work forward. > Let the human own goals, boundaries, permissions, checkpoints, evidence, and acceptance. SDD-RIPER is a context-first LLM task automation toolkit for working with strong coding agents. It is not a magic prompt and it is not heavyweight spec-driven development. It is a small set of controls and companion skills that make model-driven work observable, recoverable, reviewable, and safe to resume. The default entry is [`sdd-riper-one-light`](./skills/sdd-riper-one-light/SKILL.md). Use the heavier [`sdd-riper-one`](./skills/sdd-riper-one/SKILL.md) when the task needs stricter gates, denser artifacts, or training/audit-ready traces. The repository is organized around four complementary skills: - `sdd-riper-one-light` and `sdd-riper-one` control execution, checkpoints, validation, and reverse sync. - `codemap` turns unfamiliar code into an agent-facing context index. - `new-chat-ready` preserves recovery context for new chats, handoffs, and long pauses. ## Quick Start Use this prompt for ordinary coding or documentation work: ```text Use 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 method Wait for my approval before execution. ``` For unfamiliar code, first ask for a CodeMap: ```text Use codemap. Create a feature-level or project-level code terrain index before planning changes. Focus on entry points, call chains, risk points, validation entry points, and the smallest code slice to read next. ``` For a fresh-chat handoff: ```te

Topics