You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.**Check for ready work**: Run `bd ready` to see what's unblocked
63
+
2.**Claim your task**: `bd update <id> --status in_progress`
64
+
3.**Work on it**: Implement, test, document
65
+
4.**Discover new work**: If you find bugs or TODOs, create issues:
66
+
- Old way (two commands): `bd create "Found bug in auth" -t bug -p 1 --json` then `bd dep add <new-id> <current-id> --type discovered-from`
67
+
- New way (one command): `bd create "Found bug in auth" -t bug -p 1 --deps discovered-from:<current-id> --json`
68
+
5.**Complete**: `bd close <id> --reason "Implemented"`
69
+
6.**Export**: Changes auto-sync to `.beads/issues.jsonl` (5-second debounce)
70
+
71
+
### Issue Types
72
+
73
+
-`bug` - Something broken that needs fixing
74
+
-`feature` - New functionality
75
+
-`task` - Work item (tests, docs, refactoring)
76
+
-`epic` - Large feature composed of multiple issues
77
+
-`chore` - Maintenance work (dependencies, tooling)
78
+
79
+
### Priorities
80
+
81
+
-`0` - Critical (security, data loss, broken builds)
82
+
-`1` - High (major features, important bugs)
83
+
-`2` - Medium (nice-to-have features, minor bugs)
84
+
-`3` - Low (polish, optimization)
85
+
-`4` - Backlog (future ideas)
86
+
87
+
### Dependency Types
88
+
89
+
-`blocks` - Hard dependency (issue X blocks issue Y)
90
+
-`related` - Soft relationship (issues are connected)
91
+
-`parent-child` - Epic/subtask relationship
92
+
-`discovered-from` - Track issues discovered during work
93
+
94
+
Only `blocks` dependencies affect the ready work queue.
95
+
6
96
## **CRITICAL - TEST-DRIVEN DEVELOPMENT**
7
97
8
98
When fixing ANY bug:
@@ -11,11 +101,11 @@ When fixing ANY bug:
11
101
3.**THIRD**: Implement the fix
12
102
4.**FOURTH**: Run the test and verify it passes
13
103
14
-
**This is non-negotiable. Never implement a fix before verifying the test fails.**
104
+
**This is non-negotiable. Never implement a fix before verifying the test fails. Stop and ask the user if you cannot think of a way to mechanically test the bad behavior.**
15
105
16
106
## General Instructions
17
107
18
-
- in this repository, "qmd" means "quarto markdown", the dialect of markdown we are developing. Although we aim to be largely compatible with Pandoc, it is not necessarily the case that a discrepancy in the behavior is a bug.
108
+
- in this repository, "qmd" means "quarto markdown", the dialect of markdown we are developing. Although we aim to be largely compatible with Pandoc, discrepancies in the behavior might not be bugs.
19
109
- the qmd format only supports the inline syntax for a link [link](./target.html), and not the reference-style syntax [link][1].
20
110
- Always strive for test documents as small as possible. Prefer a large number of small test documents instead of small number of large documents.
21
111
- When fixing bugs, always try to isolate and fix one bug at a time.
0 commit comments