CtrlK
BlogDocsLog inGet started
Tessl Logo

engram-sdd-flow

Spec-Driven Development workflow for Engram. Trigger: When user requests SDD or multi-phase implementation planning.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/sdd-flow/SKILL.md
SKILL.md
Quality
Evals
Security

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
Repository
Gentleman-Programming/engram
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.