/sdd-flow
Spec-Driven Development workflow for Engram. Trigger: When user requests SDD or multi-phase implementation planning.
$ npx -y skills add Gentleman-Programming/engram --skill sdd-flow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/sdd-flow
Context preview
The summary Claude sees to decide when to auto-load this skill.
Spec-Driven Development workflow for Engram. Trigger: When user requests SDD or multi-phase implementation planning.
SKILL.md
sdd-flow.SKILL.mdname: engram-sdd-flow description: > Spec-Driven Development workflow for Engram. Trigger: When user requests SDD or multi-phase implementation planning. license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"
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
Persistent memory system for AI coding agents. Agent-agnostic Go binary with SQLite + FTS5, MCP server, HTTP API, CLI, and TUI.
Repo: Gentleman-Programming/engram
Other skills on gentleman-programming-engram.
- /memory
ALWAYS ACTIVE — Persistent memory protocol. You MUST save decisions, conventions, bugs, and discoveries to engram proactively. Do NOT wait for the user to ask.
Open skill - /memory
ALWAYS ACTIVE — Persistent memory protocol. You MUST save decisions, conventions, bugs, and discoveries to engram proactively. Do NOT wait for the user to ask.
Open skill - /architecture-guardrails
Architecture guardrails for Engram across local store, cloud sync, dashboard, and plugins. Trigger: Any change that affects system boundaries, ownership, state flow, or cross-package responsibilities.
Open skill - /backlog-triage
Backlog triage protocol for Engram: audit open issues and PRs, classify each item, infer maintainer ideology from comments, and produce an actionable disposition report. Trigger: Auditing open issues or PRs, triaging the backlog, reviewing contributor submissions as a
Open skill - /branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
Open skill - /business-rules
Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.
Open skill