sdd

Engineering Community

Skill notes

The SDD Philosophy

Core principle: Specifications are the single source of truth. Everything flows from specs, guided by principles. Why SDD matters: Principles establish the guardrails before work begins Specifications force you to think before coding Tests derived from specs verify BEHAVIOR, not implementation

Workflow Entry Point

When invoked, first determine the user's situation: If $ARGUMENTS is empty or describes a feature: → Check for existing principles first (Phase 0) → If principles exist, summarize them and ask if review is needed → If no principles, guide user through establishing them

PHASE 0: Principles Establishment

Goal: Establish or review the guiding principles that will govern all decisions Your approach: Before gathering requirements, ensure the project has clear principles. These act as constraints and quality gates throughout development. Do this: Check for existing principles:

PHASE 1: Requirements Discovery

Goal: Understand WHAT the user wants to build before writing anything Your approach: You are a requirements analyst. Your job is to extract a complete understanding of what needs to be built through conversation. Do this: Ask the user to describe what they want to build in plain language

PHASE 2: Specification Writing

Goal: Transform requirements into precise, testable specifications Your approach: You are helping the user write a contract. Specifications must be: Precise: No ambiguity about what should happen Testable: Each criterion can be verified programmatically

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@diegosouzapw · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
PHASE 0: Principles Establishment

Goal: Establish or review the guiding principles that will govern all decisions Your approach: Before gathering requirements, ensure the project has clear principles. These act as constraints and quality gates throughout development. Do this: Check for existing principles:

02
PHASE 1: Requirements Discovery

Goal: Understand WHAT the user wants to build before writing anything Your approach: You are a requirements analyst. Your job is to extract a complete understanding of what needs to be built through conversation. Do this: Ask the user to describe what they want to build in plain language

03
PHASE 2: Specification Writing

Goal: Transform requirements into precise, testable specifications Your approach: You are helping the user write a contract. Specifications must be: Precise: No ambiguity about what should happen Testable: Each criterion can be verified programmatically

04
PHASE 3: Test Derivation

Goal: Systematically generate tests from specifications Your approach: Tests are NOT creative work in SDD. They are mechanical translations of specifications into code. Each acceptance criterion becomes one or more test cases. Do this: Read SPEC.md and identify all acceptance criteria

05
PHASE 4: Implementation Guidance

Goal: Guide user through implementing code that satisfies the tests Your approach: Implementation is where SDD hands off to TDD's red-green-refactor cycle. But SDD adds a constraint: implementation must satisfy the SPECS, not just pass the tests. Do this: Run tests to confirm they fail (red state)

06
PHASE 5: Validation

Goal: Verify complete alignment between specs, tests, and implementation Your approach: Validation is the quality gate. You're checking that the triad (specs ↔ tests ↔ implementation) is consistent. Do this: Run all tests and record results

07
PHASE 6: Iteration (Handling Changes)

Goal: Properly propagate changes through the system Your approach: Changes MUST flow: Spec → Test → Implementation. Never skip steps. When user reports a change needed: Identify the change type:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.