# Sync OpenSpec Workflows With Daem0n Memory

OpenSpec decisions can drift when prior requirements and outcomes are hard to find. This skill connects specs, proposals, and archived changes to Daem0n-MCP memory.

## Install

```bash
npx skillstore add dasblueyeddevil/openspec-daem0n-bridge
```

## Metadata

- Status: approved
- Slug: dasblueyeddevil-openspec-daem0n-bridge
- Skillstore revision: r1
- Version status: missing
- Tree hash: 4f9c93dfd05d1712f564b0fbaa36bc4f6e8a38b8442a028379365562c4ca958a
- Author: DasBluEyedDevil
- GitHub username: DasBluEyedDevil
- License: MIT
- Repository: https://github.com/DasBluEyedDevil/Daem0n-MCP/tree/main/.claude/skills/openspec-daem0n-bridge
- Ref: 7e9e368dc1a370f2040369ebcd0db06d90cb48e5
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/dasblueyeddevil-openspec-daem0n-bridge
- Manifest: https://skillstore.pages.dev/api/skills/dasblueyeddevil-openspec-daem0n-bridge/manifest

## Capabilities

- Detects an openspec/specs directory in the project workspace.
- Imports OpenSpec spec summaries into Daem0n-MCP memory.
- Extracts MUST, MUST NOT, SHOULD, and SHOULD NOT requirement language.
- Recalls relevant memories before creating a new OpenSpec proposal.
- Records proposal intent with OpenSpec tags and pending status.
- Turns archived changes into learnings and links them to decisions.

## Use Cases

- Import Existing Specs: Sync current OpenSpec requirements into memory before starting implementation work.
- Prepare Safer Proposals: Review relevant specs, warnings, and past decisions before drafting a new proposal.
- Capture Archived Outcomes: Convert completed OpenSpec changes into reusable learnings for future planning.

## Prompt Templates

### Import Specs

```
Sync the OpenSpec specs in this repository to Daem0n memory and summarize what was imported.
```

### Refresh Memory

```
Refresh the OpenSpec memory for this project and tell me which rules, warnings, and patterns changed.
```

### Check Proposal Context

```
Before I propose the [feature] change, recall relevant OpenSpec memories, rules, warnings, and past decisions.
```

### Record Archived Change

```
Record the outcome for archived OpenSpec change [change-id], create learnings, and link them to the original decision memory.
```

## Limitations

- Requires Daem0n-MCP memory tools to be available in the agent session.
- Assumes the project uses the standard openspec directory layout.
- Uses local shell examples for file discovery and file reads.
- Does not validate OpenSpec content for correctness or completeness.

## Best Practices

- Review the import summary before relying on stored memories for planning.
- Use clear OpenSpec change ids so proposal and archive records stay linked.
- Redact confidential details before storing specs or archived outcomes in memory.

## Anti Patterns

- Do not import private specifications into shared memory without approval.
- Do not rely on stale memories after OpenSpec files have changed.
- Do not treat remembered rules as a replacement for reading the current spec.

## Security Audit

- Audited at: 2026-07-05T08:59:38.671\+00:00
- Summary: Most static external command alerts are Markdown backtick false positives or MCP call examples. The real risks are narrow local shell reads of OpenSpec files and automatic persistence of project specification data into Daem0n memory.

## Stats

- Views: 261
- Downloads: 7
- Favorites: 0
- Popularity score: 0