Sdd flow
Spec-Driven Development workflow for Engram. Trigger: When user requests SDD or multi-phase implementation planning.From its SKILL.md
npx -y skills add LuchoC-Dev/agent-kits --skill sdd-flowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.1 KB, 206 tokens by cl100k_base, as published. Nobody here has run it
When to Use
Use this skill when:
- Starting non-trivial changes
- Coordinating spec, design, implementation, and validation
- Running command-based SDD flow
Canonical Phase Order
explore- understand existing behavior and constraintspropose- define intent and scopeapply- implement tasks from approved planverify- validate behavior against spec and regressionsarchive- capture completion and close loop
Never skip a phase without explicit rationale.
Artifacts per Phase
- Explore: findings and risks
- Propose: change proposal with scope boundaries
- Apply: code + tests
- Verify: evidence of validation
- Archive: finalized summary and follow-ups
Exit Criteria
- Scope and risks understood before implementation
- Tests prove expected behavior
- Verification covers regressions
- Session summary captures learnings for next work