Agent skill · product strategy · aiskillstore
openspec-daem0n-bridge
Bridges OpenSpec (spec-driven development) with Daem0n-MCP memory - auto-imports specs, informs proposals with past outcomes, converts archived changes to learnings
Why this skill is useful
Adds executable workflows for auto-importing specs and creating memory rules that enhance the AI's capabilities in spec-driven development.
What it needs
Requires daem0n installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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: Auto-Detection On session start, after getbriefing(): Check if openspec/ directory exists in the project root: 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: 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 2. For each spec, read the spec.md file 3. Parse requirements using these patterns: Pattern Extract As --------- ------------ MUST, SHALL, REQUIRED rule.mustdo MUST NOT, SHALL NOT, PROHIBITED rule.mustnot SHOULD, RECOMMENDED pattern SHOULD NOT, NOT RECOMMENDED warning ## Purpose section pattern (overview) 4. Create memories via rememberbatch 5. Create rules from MUST/MUST NOT 6. Report summary Memory Mapping Reference OpenSpec Element Daem0n Category Tags ----------------- ----------------- ------ spec.md overview pattern openspec, spec, [name] MUST requirements rule.mustdo (in rule, not memory) MUST NOT constraints rule.mustnot (in rule, not memory) Known limitations warning openspec, limitation, [name] Design rationale learning openspec, rationale, [name] Workflow 2: Inform Proposal Creation Triggers: "prepare proposal for [feature]" "check before proposing [feature]" "what do I need to know before proposing [feature]" Steps 1. Recall relevant memories 2. Check applicable rules 3. Recall OpenSpec-specific context 4. If specific files are affected, check them 5. Present findings to user in this format: 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/openspec-daem0n-bridge