One-click install
npx skills add https://github.com/CamiloAndresGTRUniandes/lucy-ai --skill sdd-camiloandresgtruniandes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd
Source: https://github.com/CamiloAndresGTRUniandes/lucy-ai/tree/main/skills/sdd
Command: npx skills add https://github.com/CamiloAndresGTRUniandes/lucy-ai --skill sdd-camiloandresgtruniandes

SYSTEM DOCUMENTATION & REQUIREMENTS

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.”

Frequently Asked Questions about sdd

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

FAQPage Schema
What is spec-driven development for feature planning and implementation?

Spec-driven development is a workflow that enforces structured requirements gathering and architectural decisions before coding, coordinating an end-to-end cycle from Explore through Archive to reduce rework and misalignment.

How do I start a spec-driven workflow for a new feature with unclear requirements?

Start a spec-driven workflow by triggering the Explore phase to gather requirements, then generate 2–3 architectural proposals for direction approval before moving into the Spec and Design phases.

When should I use a spec-first workflow instead of just building a feature?

Use a spec-first workflow when building new capabilities, implementing non-trivial changes, or making architectural decisions where requirements are unclear or technical risk is high.

Does spec-driven development require phase-gated approval before implementation?

Yes, spec-driven development satisfies phase-gated approval requirements by enforcing reviews at the Propose, Spec, and Design stages, and mandates tests during the Apply phase before changes are verified.

How does technical memory persistence work for architectural decisions?

Technical memory persistence uses Engram-backed storage to capture architectural trade-offs, search prior decisions, and enforce critical review when new design conflicts arise with existing engineering memory.

What are the limitations of enforcing strict workflow orchestration for feature delivery?

Strict workflow orchestration limits rapid prototyping by requiring phase-gated approvals and test mandates, making it less suitable for trivial changes where the overhead of full spec-driven development outweighs the risk.