spec-driven-with-beads 1.1.0 → 1.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +56 -0
- package/package.json +1 -1
package/README.md
ADDED
|
@@ -0,0 +1,56 @@
|
|
|
1
|
+
# spec-driven-with-beads
|
|
2
|
+
|
|
3
|
+
OpenSpec custom schema that uses [Beads](https://github.com/gastownhall/beads) (`bd`) for task tracking, execution, and **durable knowledge retention** across sessions.
|
|
4
|
+
|
|
5
|
+
```
|
|
6
|
+
proposal → specs → design → tasks+beads → apply (via Beads) → consolidate
|
|
7
|
+
```
|
|
8
|
+
|
|
9
|
+
## What makes this different
|
|
10
|
+
|
|
11
|
+
Other spec-driven schemas end at `archive` — move files, update specs, done. Knowledge dies with the session.
|
|
12
|
+
|
|
13
|
+
This schema adds **`consolidate`** — a fourth action that closes the learning loop:
|
|
14
|
+
|
|
15
|
+
| Phase | What happens |
|
|
16
|
+
|-------|-------------|
|
|
17
|
+
| `tasks` | Writes `tasks.md` AND seeds Beads via `bd create` + `bd dep add` |
|
|
18
|
+
| `apply` | Drives work through `bd ready` → `bd update --claim` → code → `bd close` |
|
|
19
|
+
| **`consolidate`** | `bd close` remaining → **`bd compact`** → **`bd remember`** → `openspec archive` |
|
|
20
|
+
|
|
21
|
+
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.
|
|
22
|
+
|
|
23
|
+
No other OpenSpec schema does this. No task tracker (Linear, GitHub Issues, Jira) has a `bd remember` equivalent.
|
|
24
|
+
|
|
25
|
+
## Requirements
|
|
26
|
+
|
|
27
|
+
- [Beads](https://github.com/gastownhall/beads) installed (`bd` on PATH)
|
|
28
|
+
- `bd init` run in your project
|
|
29
|
+
- OpenSpec installed (`npm install -g @fission-ai/openspec`)
|
|
30
|
+
|
|
31
|
+
## Install
|
|
32
|
+
|
|
33
|
+
```bash
|
|
34
|
+
npm install -g spec-driven-with-beads
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
This copies the schema into OpenSpec's global schemas, making it available in any project.
|
|
38
|
+
|
|
39
|
+
## Usage
|
|
40
|
+
|
|
41
|
+
In your project's `openspec/config.yaml`:
|
|
42
|
+
|
|
43
|
+
```yaml
|
|
44
|
+
schema: spec-driven-with-beads
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
Then use standard OpenSpec commands:
|
|
48
|
+
- `/opsx:propose "my feature"`
|
|
49
|
+
- `/opsx:apply`
|
|
50
|
+
- `/opsx:consolidate` — closes issues, compacts, remembers, archives
|
|
51
|
+
|
|
52
|
+
## Links
|
|
53
|
+
|
|
54
|
+
- [OpenSpec](https://github.com/Fission-AI/OpenSpec)
|
|
55
|
+
- [Beads](https://github.com/gastownhall/beads)
|
|
56
|
+
- [Community schema catalog](https://github.com/intent-driven-dev/openspec-schemas)
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "spec-driven-with-beads",
|
|
3
|
-
"version": "1.1.
|
|
3
|
+
"version": "1.1.1",
|
|
4
4
|
"description": "OpenSpec custom schema using Beads (bd) for task tracking, execution, and knowledge consolidation",
|
|
5
5
|
"keywords": ["openspec", "beads", "spec-driven-development", "schema", "sdd"],
|
|
6
6
|
"license": "MIT",
|