mem_saveLABSCO SUMMARY
Memory plus a specification flow you can enter at any point.
sdd_clarify runs an 8-dimension ambiguity analysis and blocks until the score clears its threshold — 70 in guided mode, 50 in expert — which is the stage that stops an agent building something nobody asked for. For a repo with no specs at all, sdd_reverse_engineer reads the code and writes nothing; files appear only when you run sdd_bootstrap.
What it is
A single Go binary that adds five systems to any MCP-compatible AI tool: persistent memory, an adaptive change pipeline, a full project pipeline, codebase bootstrap, and standalone review tools.
What you get
- Memory across sessions —
mem_save,mem_search,mem_contextandmem_timelineover SQLite with FTS5 full-text search - A knowledge graph:
mem_relateconnects observations with typed edges such asdepends_on,caused_by,implementsandsupersedes - A change pipeline (5 tools) whose
sdd_context_checkstage scans existing specs, completed changes, memory and convention files like CLAUDE.md for conflicts before work starts - A project pipeline (10 tools) running init → principles → charter → specify → business-rules → clarify → design → tasks → validate
- Bootstrap for code that has no specs:
sdd_reverse_engineerproduces a read-only evidence report,sdd_bootstrapwrites the missing requirements, business rules and design files - Four standalone tools that need no active pipeline —
sdd_explore,sdd_suggest_context,sdd_reviewandsdd_audit
Requirements
Install the binary — brew install HendryAvila/hoofy/hoofy, the install script, or go install github.com/HendryAvila/Hoofy/cmd/hoofy@latest (Go 1.25+). Then register it in one command: claude mcp add --scope user hoofy hoofy serve. One binary, no external runtime dependencies.
Setup effort
One command — brew install HendryAvila/hoofy/hoofy
USE CASES
01
Picking up work you left three weeks ago
Search past sessions by full text, then pull recent observations into the new session before the agent starts guessing at context.
02
Adding a feature to a codebase that already has conventions
Open a change, and the conflict scanner checks existing specs, completed changes and your convention files first — zero issues advances, issues found must be resolved.
03
Giving a legacy repo the specs it never had
Scan the codebase into a structured evidence report — stack, architecture, conventions, data model, business logic — then write the missing artifacts for review.
04
Reviewing a change against what was actually agreed
Generate a review checklist tied to specific requirement and business-rule ids, or compare the specs against the source and list the drift.
34 tools
Listed in project docs. Your client may show a different list.
mem_sessionmem_searchmem_contextmem_timelinemem_getmem_relatemem_statsmem_deletemem_updatemem_suggest_topic_keymem_progressmem_compactsdd_changesdd_context_checksdd_change_advancesdd_change_statussdd_adrsdd_reverse_engineersdd_bootstrapsdd_exploresdd_suggest_contextsdd_reviewsdd_auditsdd_init_projectsdd_create_principlessdd_create_chartersdd_generate_requirementssdd_create_business_rulessdd_clarifysdd_create_designsdd_create_taskssdd_validatesdd_get_contextBEFORE YOU INSTALL
What to know first
Tools you get
34 tools named in the project's documentation.
Requires
hoofy on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
brew install HendryAvila/hoofy/hoofyMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --scope user hoofy hoofy serveClaude Code — plugin
CLAUDE CODE — PLUGIN · IN CLIENT
/plugin marketplace add HendryAvila/hoofy-plugins
/plugin install hoofy@hoofy-pluginsCursor, Gemini CLI
JSON
{
"mcpServers": {
"hoofy": {
"command": "hoofy",
"args": [
"serve"
]
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"hoofy": {
"type": "stdio",
"command": "hoofy",
"args": [
"serve"
]
}
}
}OpenCode
OPENCODE · JSON
{
"mcp": {
"hoofy": {
"type": "local",
"command": [
"hoofy",
"serve"
],
"enabled": true
}
}
}
