Engram Sdd Flow
- 86 installs
- 5.8k repo stars
- Updated July 30, 2026
- gentleman-programming/engram
Run a spec-driven development workflow for Engram that coordinates spec, design, implementation, and validation phases in a canonical order for non-trivial changes.
About
Provides a command-based spec-driven development flow that sequences spec, design, implementation, and validation for Engram work. A developer uses it when starting non-trivial changes or coordinating multi-phase implementation planning.
- Coordinates spec, design, implementation, and validation phases
- Enforces a canonical phase order for the SDD flow
Engram Sdd Flow by the numbers
- 86 all-time installs (skills.sh)
- Ranked #1,417 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/gentleman-programming/engram --skill engram-sdd-flowAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 86 |
|---|---|
| repo stars | ★ 5.8k |
| Last updated | July 30, 2026 |
| Repository | gentleman-programming/engram ↗ |
What it does
Run a spec-driven development workflow for Engram that coordinates spec, design, implementation, and validation phases in a canonical order for non-trivial changes.
Files
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
1. explore - understand existing behavior and constraints 2. propose - define intent and scope 3. apply - implement tasks from approved plan 4. verify - validate behavior against spec and regressions 5. archive - 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
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k