What problem does it solve?
It prevents “just build it” development by forcing a spec-driven, decision-backed workflow before implementation, reducing rework and misalignment.
Core Features & Use Cases
- Explore → Propose → Spec → Design → Tasks → Apply → Verify → Archive: a structured end-to-end cycle for new features, architecture changes, and significant technical decisions.
- Engram-backed decision memory: captures architecture and trade-offs, searches prior decisions, and enforces critical review when conflicts arise.
- Strict guardrails: requires Camilo approval at key gates (Propose, Spec, Design, PR feedback routing) and mandates tests for Apply.
Real-world use case: when a team member wants to “add a feature” without clarity, SDD guides the effort from discovery and requirements through validated implementation and a documented archive of what changed and why.
Quick Start
Ask for an SDD plan by saying: “We need to build a new feature for OpenClaw—start with Explore and then propose 2–3 approaches so Camilo can approve direction.”