spec-driven-with-beads 1.0.0 → 1.1.0
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.
|
@@ -5,7 +5,7 @@ OpenSpec workflow that uses Beads (`bd`) for task tracking and execution instead
|
|
|
5
5
|
## Workflow
|
|
6
6
|
|
|
7
7
|
```
|
|
8
|
-
proposal → specs → design → tasks+beads → apply (via Beads) →
|
|
8
|
+
proposal → specs → design → tasks+beads → apply (via Beads) → consolidate
|
|
9
9
|
```
|
|
10
10
|
|
|
11
11
|
| Phase | Artifact | Beads interaction |
|
|
@@ -15,7 +15,7 @@ proposal → specs → design → tasks+beads → apply (via Beads) → archive
|
|
|
15
15
|
| `design` | `design.md` | None |
|
|
16
16
|
| `tasks` | `tasks.md` + seeds Beads | `bd create` for each task, `bd dep add` for dependencies |
|
|
17
17
|
| `apply` | (tracks via Beads) | `bd ready` → `bd update --claim` → code → `bd close` |
|
|
18
|
-
| `
|
|
18
|
+
| `consolidate` | (wraps up) | `bd close` remaining → `bd compact` → `bd remember` learnings → `openspec archive` |
|
|
19
19
|
|
|
20
20
|
## Why Beads?
|
|
21
21
|
|
|
@@ -2,7 +2,7 @@ name: spec-driven-with-beads
|
|
|
2
2
|
version: 1
|
|
3
3
|
description: >
|
|
4
4
|
OpenSpec workflow powered by Beads issue tracking.
|
|
5
|
-
proposal -> specs -> design -> tasks+beads -> apply (via Beads) ->
|
|
5
|
+
proposal -> specs -> design -> tasks+beads -> apply (via Beads) -> consolidate.
|
|
6
6
|
|
|
7
7
|
artifacts:
|
|
8
8
|
- id: proposal
|
|
@@ -215,3 +215,23 @@ apply:
|
|
|
215
215
|
|
|
216
216
|
Pause if you hit blockers or need clarification. Use `bd show <id>` to
|
|
217
217
|
inspect task details, and `bd update <id>` to add notes.
|
|
218
|
+
|
|
219
|
+
consolidate:
|
|
220
|
+
requires:
|
|
221
|
+
- apply
|
|
222
|
+
instruction: |
|
|
223
|
+
All tasks are complete. Run consolidate to close the loop:
|
|
224
|
+
|
|
225
|
+
1. Close any remaining open Beads issues: `bd close <id1> <id2> ...`
|
|
226
|
+
2. Compact old closed issues: `bd compact`
|
|
227
|
+
3. Distill learnings from this change and persist them:
|
|
228
|
+
```
|
|
229
|
+
bd remember --key spec-driven-beads-<change-name> "Lessons from this change:
|
|
230
|
+
- What unexpected problems did you encounter?
|
|
231
|
+
- What decisions turned out well or poorly?
|
|
232
|
+
- Any surprising edge cases or constraints?
|
|
233
|
+
- What should the next similar change do differently?"
|
|
234
|
+
```
|
|
235
|
+
4. Run the OpenSpec archive command: `openspec archive` (moves change folder, updates source specs)
|
|
236
|
+
|
|
237
|
+
This ensures knowledge persists across sessions — future `bd prime` calls will inject these learnings.
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "spec-driven-with-beads",
|
|
3
|
-
"version": "1.
|
|
4
|
-
"description": "OpenSpec custom schema using Beads (bd) for task tracking and
|
|
3
|
+
"version": "1.1.0",
|
|
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",
|
|
7
7
|
"author": "yoinks-yoinks",
|