spec-driven-with-beads 3.0.0 → 3.0.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.
Files changed (2) hide show
  1. package/README.md +124 -29
  2. package/package.json +8 -2
package/README.md CHANGED
@@ -1,55 +1,150 @@
1
1
  # spec-driven-with-beads
2
2
 
3
- OpenSpec custom schema that uses [Beads](https://github.com/gastownhall/beads) molecules for task tracking, execution, and durable knowledge retention across sessions.
3
+ **Spec-driven development with git-synced task tracking.**
4
+ Bridge OpenSpec's spec planning with Beads' persistent, dependency-aware issue graph.
4
5
 
5
6
  ```
6
- proposal → specs → design → tasks+beads → apply (via molecule) → consolidate
7
+ proposal → specs → design → tasks+beads → apply → consolidate
7
8
  ```
8
9
 
9
- ## What makes this different
10
+ ---
10
11
 
11
- Other spec-driven schemas end at `archive` move files, done. Knowledge dies with the session.
12
+ ## The problem every AI coding agent hits
12
13
 
13
- This schema uses Beads' **formula + molecule** system. One `bd pour` creates the entire dependency graph with mandatory `needs:` dependencies, then **consolidate** closes the learning loop — `bd remember` persists lessons as durable memories, `bd mol distill` extracts reusable formulas from completed work.
14
+ You plan a change with OpenSpec: proposal specs design. Great. Then you implement. The agent creates a flat `tasks.md`, ticks boxes, done.
14
15
 
15
- ### Key features
16
+ Next session? The agent has amnesia. It doesn't know what was done, what was learned, or what's blocked. Multi-day features fragment across disconnected sessions. Multi-developer workflows don't exist — everyone works in isolation.
16
17
 
17
- - **Mandatory dependency graph** — the formula defines `needs:` between every step. `bd ready` only shows unblocked work. No manual `bd dep add`.
18
- - **Spec-compliance aspect** — auto-injects a "Verify specs pass" step before consolidate. No config needed.
19
- - **Bond points for optional behavior** — parallel multi-agent execution, async gates (human approval/CI/timers). Bond a formula to unlock; bond nothing = sequential.
20
- - **`bd mol squash`** — compresses completed molecules into lightweight digests. Clean issue graph.
21
- - **`bd mol distill`** — extracts reusable formulas from completed changes. The schema teaches itself.
22
- - **`bd remember`** — persists learnings that `bd prime` injects into every future session.
18
+ **This schema fixes that.**
23
19
 
24
- ## Requirements
20
+ ---
25
21
 
26
- - [Beads](https://github.com/gastownhall/beads) installed (`bd` on PATH)
27
- - `bd init` run in your project
28
- - OpenSpec installed (`npm install -g @fission-ai/openspec`)
22
+ ## The solution: Beads + OpenSpec
29
23
 
30
- ## Install
24
+ [Beads](https://github.com/gastownhall/beads) is a **Dolt-powered issue tracker that syncs to git**. Unlike flat markdown task lists or cloud issue trackers, Beads stores your task graph in a version-controlled SQL database that lives in your repo. Push, pull, branch, merge — just like code.
25
+
26
+ | Capability | Flat `tasks.md` | GitHub Issues | **Beads (this schema)** |
27
+ |---|---|---|---|
28
+ | Dependency graph | ❌ Manual | ❌ Shallow | ✅ `needs:` in formula, `bd ready` enforces |
29
+ | Git-synced | ✅ (file) | ❌ (cloud) | **✅ Dolt DB in `.beads/`, push/pull with code** |
30
+ | Multi-session persistence | ❌ Lost | ✅ (cloud) | **✅ `bd dolt push/pull` — pick up where you left off** |
31
+ | Multi-developer sync | ❌ Merge hell | ✅ (cloud) | **✅ Dolt-native replication, cell-level merge** |
32
+ | Cross-session knowledge | ❌ None | ❌ None | **✅ `bd remember` → `bd prime` injects into every session** |
33
+ | Reusable workflows | ❌ Copy-paste | ❌ None | **✅ `bd mol distill` extracts formulas from completed work** |
34
+ | Parallel agents | ❌ Impossible | ❌ Clunky | **✅ `bd pin` + bond points with `waits_for` fan-in** |
35
+ | Dependency-aware ready queue | ❌ None | ❌ None | **✅ `bd ready` only shows unblocked work** |
36
+ | Async coordination | ❌ None | ❌ Partial | **✅ Gates (human approval, timers, CI checks)** |
37
+ | One-command setup | ❌ Manual | ❌ N/A | **✅ `bd pour spec-driven-change --var name=my-feature`** |
38
+
39
+ ---
40
+
41
+ ## How it works
42
+
43
+ ### One command creates the entire task graph
44
+
45
+ ```
46
+ bd pour spec-driven-change --var name=add-user-auth
47
+ ```
48
+
49
+ Produces a molecule with mandatory dependency chain:
50
+
51
+ ```
52
+ bd-a3f8 (epic: Spec-driven Change: add-user-auth)
53
+ ├── bd-a3f8.1 proposal (human review)
54
+ ├── bd-a3f8.2 specs (needs: proposal)
55
+ ├── bd-a3f8.3 design (needs: specs)
56
+ ├── bd-a3f8.4 implement (needs: design)
57
+ ├── bd-a3f8.5 verify-specs-consolidate (auto-injected spec compliance check)
58
+ └── bd-a3f8.6 consolidate (human, needs: implement, verify-specs)
59
+ ```
60
+
61
+ No manual `bd create` × N. No `bd dep add` × N. The formula defines the graph.
62
+
63
+ ### Dependencies are enforced, not documented
31
64
 
32
- ```bash
33
- npm install -g spec-driven-with-beads
65
+ ```
66
+ $ bd ready
67
+ 1. [P1] bd-a3f8.1: Review proposal for add-user-auth
68
+
69
+ $ bd ready --explain
70
+ ● Ready:
71
+ bd-a3f8.1 — no blocking dependencies
72
+
73
+ ● Blocked:
74
+ bd-a3f8.2 — blocked by bd-a3f8.1 (proposal)
75
+ bd-a3f8.4 — blocked by bd-a3f8.3 (design)
34
76
  ```
35
77
 
36
- ## Usage
78
+ The agent never picks work it can't start. No wasted cycles.
37
79
 
38
- In `openspec/config.yaml`:
80
+ ### Work flows across sessions
39
81
 
40
- ```yaml
41
- schema: spec-driven-with-beads
82
+ ```
83
+ # Session 1 — morning
84
+ bd pour spec-driven-change --var name=add-user-auth
85
+ bd update bd-a3f8.1 --claim # Review proposal
86
+ bd close bd-a3f8.1
87
+ bd dolt push # Save state to repo
88
+
89
+ # Session 2 — afternoon (new session, zero context)
90
+ bd dolt pull # Pull task graph
91
+ bd ready # → bd-a3f8.2: Write specs
92
+ ```
93
+
94
+ Pick up exactly where you left off. The agent doesn't need to re-read `tasks.md` — it queries `bd ready`.
95
+
96
+ ### Knowledge compounds across changes
97
+
98
+ After each change, `consolidate` runs:
99
+
100
+ ```
101
+ bd lint # Validate all issues have proper structure
102
+ bd compact # Compress old Dolt history
103
+ bd remember --key ... # Store lessons learned
104
+ bd mol squash # Compress molecule to lightweight digest
105
+ bd mol distill # (optional) Extract reusable formula
106
+ ```
107
+
108
+ Every future `bd prime` call injects those memories. The agent knows what the last change taught it — no rediscovery.
109
+
110
+ ### Optional: parallel multi-agent or async gates
111
+
112
+ Bond nothing → sequential, zero config. Bond a formula at a bond point → unlock:
113
+
114
+ | Bond point | What it enables |
115
+ |---|---|
116
+ | `parallel-execution` | Split implement into parallel sub-steps, one per capability, each pinned to a different agent. Fan-in before consolidate. |
117
+ | `async-gates` | Add human approval gates, timer delays, or GitHub CI checks before implementation. |
118
+
119
+ ---
120
+
121
+ ## Quick start
122
+
123
+ ```bash
124
+ # Prerequisites
125
+ brew install beads # or: npm install -g @beads/bd
126
+ npm install -g @fission-ai/openspec # OpenSpec CLI
127
+ npm install -g spec-driven-with-beads # This schema
128
+
129
+ # In your project
130
+ cd your-project
131
+ bd init
132
+ openspec init
133
+ echo "schema: spec-driven-with-beads" >> openspec/config.yaml
134
+
135
+ # Start your first spec-driven change
136
+ # → /opsx:propose "my feature"
137
+ # → /opsx:apply
138
+ # → /opsx:consolidate
42
139
  ```
43
140
 
44
- Then:
45
- - `/opsx:propose "my feature"`
46
- - `/opsx:apply` — driven by molecule step order
47
- - `/opsx:consolidate` — lint, squash, remember, distill, archive
141
+ ---
48
142
 
49
143
  ## Links
50
144
 
51
- - [OpenSpec](https://github.com/Fission-AI/OpenSpec)
52
- - [Beads](https://github.com/gastownhall/beads)
145
+ - [npm package](https://www.npmjs.com/package/spec-driven-with-beads)
146
+ - [OpenSpec](https://github.com/Fission-AI/OpenSpec) (55k ★)
147
+ - [Beads](https://github.com/gastownhall/beads) (24k ★)
53
148
  - [Beads Formula docs](https://gastownhall.github.io/beads/workflows/formulas)
54
149
  - [Beads Molecule docs](https://gastownhall.github.io/beads/workflows/molecules)
55
150
  - [Community schema catalog](https://github.com/intent-driven-dev/openspec-schemas)
package/package.json CHANGED
@@ -1,8 +1,14 @@
1
1
  {
2
2
  "name": "spec-driven-with-beads",
3
- "version": "3.0.0",
3
+ "version": "3.0.1",
4
4
  "description": "OpenSpec custom schema using Beads molecules with bond points, aspects, and distill for spec-driven development",
5
- "keywords": ["openspec", "beads", "spec-driven-development", "schema", "sdd"],
5
+ "keywords": [
6
+ "openspec",
7
+ "beads",
8
+ "spec-driven-development",
9
+ "schema",
10
+ "sdd"
11
+ ],
6
12
  "license": "MIT",
7
13
  "author": "yoinks-yoinks",
8
14
  "homepage": "https://www.npmjs.com/package/spec-driven-with-beads",