← ClaudeAtlas

openspec-daem0n-bridgelisted

Bridges OpenSpec (spec-driven development) with Daem0n-MCP memory - auto-imports specs, informs proposals with past outcomes, converts archived changes to learnings
aiskillstore/marketplace · ★ 329 · Testing & QA · score 79
Install: claude install-skill aiskillstore/marketplace
# OpenSpec-Daem0n Bridge ## Overview This skill creates a bidirectional bridge between: - **OpenSpec**: Spec-driven development with formal change proposals - **Daem0n-MCP**: AI memory system with semantic search and outcome tracking **The feedback loop:** ``` OpenSpec specs ──────► Daem0n patterns/rules ▲ │ │ ▼ Future specs ◄────── Past outcomes/failures ``` ## Auto-Detection **On session start, after `get_briefing()`:** Check if `openspec/` directory exists in the project root: ```bash ls openspec/specs/ 2>/dev/null ``` **If OpenSpec detected AND specs not yet imported:** 1. Announce: "OpenSpec detected. Syncing specs to Daem0n memory..." 2. Execute Workflow 1 (Import) automatically 3. Report summary of imported specs and rules **How to check if already imported:** ``` recall(topic="openspec", tags=["spec"], limit=1) ``` If results exist with recent timestamps, skip import. ## Workflow 1: Import Specs to Memory **Triggers:** - Auto: OpenSpec directory detected on first session - Manual: "sync specs to memory", "import openspec", "refresh openspec" ### Steps 1. **List all spec directories** ```bash ls openspec/specs/ ``` 2. **For each spec, read the spec.md file** ```bash cat openspec/specs/[name]/spec.md ``` 3. **Parse requirements using these patterns:** | Pattern | Extract As | |---------|------------| | `MUST`, `SHALL`, `REQUIRED` | rule.must_do | | `MUST NOT`, `SH