spec-driven-with-beads 1.0.0 → 1.1.1

package/README.md

@@ -0,0 +1,56 @@
+# spec-driven-with-beads
+
+OpenSpec custom schema that uses [Beads](https://github.com/gastownhall/beads) (`bd`) for task tracking, execution, and **durable knowledge retention** across sessions.
+
+```
+proposal → specs → design → tasks+beads → apply (via Beads) → consolidate
+```
+
+## What makes this different
+
+Other spec-driven schemas end at `archive` — move files, update specs, done. Knowledge dies with the session.
+
+This schema adds **`consolidate`** — a fourth action that closes the learning loop:
+
+| Phase | What happens |
+|-------|-------------|
+| `tasks` | Writes `tasks.md` AND seeds Beads via `bd create` + `bd dep add` |
+| `apply` | Drives work through `bd ready` → `bd update --claim` → code → `bd close` |
+| **`consolidate`** | `bd close` remaining → **`bd compact`** → **`bd remember`** → `openspec archive` |
+
+The key: **`bd remember`** persists lessons, decisions, and edge cases as durable memories. Every future `bd prime` call injects them into the agent's context. Next session, the agent knows what the last change taught you — no context loss, no rediscovery.
+
+No other OpenSpec schema does this. No task tracker (Linear, GitHub Issues, Jira) has a `bd remember` equivalent.
+
+## Requirements
+
+- [Beads](https://github.com/gastownhall/beads) installed (`bd` on PATH)
+- `bd init` run in your project
+- OpenSpec installed (`npm install -g @fission-ai/openspec`)
+
+## Install
+
+```bash
+npm install -g spec-driven-with-beads
+```
+
+This copies the schema into OpenSpec's global schemas, making it available in any project.
+
+## Usage
+
+In your project's `openspec/config.yaml`:
+
+```yaml
+schema: spec-driven-with-beads
+```
+
+Then use standard OpenSpec commands:
+- `/opsx:propose "my feature"`
+- `/opsx:apply`
+- `/opsx:consolidate` — closes issues, compacts, remembers, archives
+
+## Links
+
+- [OpenSpec](https://github.com/Fission-AI/OpenSpec)
+- [Beads](https://github.com/gastownhall/beads)
+- [Community schema catalog](https://github.com/intent-driven-dev/openspec-schemas)

package/openspec/schemas/spec-driven-with-beads/README.md

@@ -5,7 +5,7 @@ OpenSpec workflow that uses Beads (`bd`) for task tracking and execution instead
 ## Workflow
 
 ```
-proposal → specs → design → tasks+beads → apply (via Beads) → archive
+proposal → specs → design → tasks+beads → apply (via Beads) → consolidate
 ```
 
 | Phase | Artifact | Beads interaction |
@@ -15,7 +15,7 @@ proposal → specs → design → tasks+beads → apply (via Beads) → archive
 | `design` | `design.md` | None |
 | `tasks` | `tasks.md` + seeds Beads | `bd create` for each task, `bd dep add` for dependencies |
 | `apply` | (tracks via Beads) | `bd ready` → `bd update --claim` → code → `bd close` |
-| `archive` | moves to archive | `bd compact` on closed issues |
+| `consolidate` | (wraps up) | `bd close` remaining → `bd compact` → `bd remember` learnings → `openspec archive` |
 
 ## Why Beads?
 

package/openspec/schemas/spec-driven-with-beads/schema.yaml

@@ -2,7 +2,7 @@ name: spec-driven-with-beads
 version: 1
 description: >
   OpenSpec workflow powered by Beads issue tracking.
-  proposal -> specs -> design -> tasks+beads -> apply (via Beads) -> archive (compact).
+  proposal -> specs -> design -> tasks+beads -> apply (via Beads) -> consolidate.
 
 artifacts:
   - id: proposal
@@ -215,3 +215,23 @@ apply:
 
     Pause if you hit blockers or need clarification. Use `bd show <id>` to
     inspect task details, and `bd update <id>` to add notes.
+
+consolidate:
+  requires:
+    - apply
+  instruction: |
+    All tasks are complete. Run consolidate to close the loop:
+
+    1. Close any remaining open Beads issues: `bd close <id1> <id2> ...`
+    2. Compact old closed issues: `bd compact`
+    3. Distill learnings from this change and persist them:
+       ```
+       bd remember --key spec-driven-beads-<change-name> "Lessons from this change:
+       - What unexpected problems did you encounter?
+       - What decisions turned out well or poorly?
+       - Any surprising edge cases or constraints?
+       - What should the next similar change do differently?"
+       ```
+    4. Run the OpenSpec archive command: `openspec archive` (moves change folder, updates source specs)
+
+    This ensures knowledge persists across sessions — future `bd prime` calls will inject these learnings.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "spec-driven-with-beads",
-  "version": "1.0.0",
-  "description": "OpenSpec custom schema using Beads (bd) for task tracking and execution",
+  "version": "1.1.1",
+  "description": "OpenSpec custom schema using Beads (bd) for task tracking, execution, and knowledge consolidation",
   "keywords": ["openspec", "beads", "spec-driven-development", "schema", "sdd"],
   "license": "MIT",
   "author": "yoinks-yoinks",