sdd-flow

Structure repository changes into explore, propose, apply, verify, and archive phases.

Updated May 17, 2026
One-click install
npx skills add https://github.com/cheetah-alo/NegritaOS --skill sdd-flow-cheetah-alo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-flow
Source: https://github.com/cheetah-alo/NegritaOS/tree/main/.codex/skills/sdd-flow
Command: npx skills add https://github.com/cheetah-alo/NegritaOS --skill sdd-flow-cheetah-alo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

sdd-flow eliminates risky, ad-hoc work by forcing every non-trivial change into a clear sequence of discovery, proposal, implementation, verification, and closure.

Core Features & Use Cases

  • Spec-Driven phased workflow: structures work into explore → propose → apply → verify → archive so intent, scope, and evidence are explicit.
  • Governance-first change control: ensures risks, acceptance criteria, and rule compliance are considered before and during implementation.
  • Artifact-based accountability: produces phase-specific outputs (findings, bounded plan, code/docs/tests, validation evidence, and durable learnings).
  • Use Case: You need to introduce a meaningful change (e.g., a new agent capability or a governance rule adjustment) without breaking existing behavior, and you want a repeatable audit trail from requirement to verification.

Quick Start

Use the sdd-flow skill to plan and execute your requested change with explicit acceptance criteria and verification evidence.

Frequently Asked Questions about sdd-flow

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

FAQPage Schema
What is spec-driven development for managing repository changes?

Spec-driven development structures non-trivial repository changes into phased planning, bounded scope, and evidence-based validation to prevent risky, ad-hoc work. It enforces explicit intent, scope, and rule compliance throughout the workflow.

How do I implement a governance update without breaking existing behavior?

To implement a governance update safely, apply a phased workflow of explore, propose, apply, verify, and archive. This ensures risks and acceptance criteria are considered, capturing validation evidence before finalizing changes.

How to plan a regression-safe refactor with explicit acceptance criteria?

Plan a regression-safe refactor by forcing the change into a structured sequence of discovery, proposal, implementation, and verification. This produces phase-specific artifacts like bounded plans and validation evidence for accountability.

Does spec-driven development work for adding new agent capabilities?

Yes, spec-driven development applies to adding new agent capabilities by enforcing a governance-first change control process. It produces a repeatable audit trail from requirement to verification, ensuring existing behavior remains unbroken.

When do I need a phased workflow for feature additions?

You need a phased workflow for feature additions when changes are non-trivial and require governance, bounded scope, and proof. It prevents unplanned changes by enforcing artifact capture and rule-compliance verification before finalizing.

What is the best way to ensure change management accountability in a repository?

Ensure change management accountability by using an artifact-based workflow that produces phase-specific outputs like findings, bounded plans, code, tests, and validation evidence. This creates a durable audit trail from requirement to closure.