lean-spec 0.2.8 → 0.2.9

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.
@@ -26,8 +26,8 @@ If you have LeanSpec MCP tools available, **ALWAYS use them**:
26
26
  | View a spec | `view` | Full content with formatting |
27
27
  | Create new spec | `create` | Auto-sequences, proper structure |
28
28
  | Update spec | `update` | Validates transitions, timestamps |
29
- | Link specs | `link` | Add relationships (depends_on, related) |
30
- | Unlink specs | `unlink` | Remove relationships |
29
+ | Link specs | `link` | Add dependencies (depends_on) |
30
+ | Unlink specs | `unlink` | Remove dependencies |
31
31
  | Check dependencies | `deps` | Visual dependency graph |
32
32
 
33
33
  **Why MCP over CLI?**
@@ -46,8 +46,8 @@ lean-spec list # See all specs
46
46
  lean-spec search "query" # Find relevant specs
47
47
  lean-spec create <name> # Create new spec
48
48
  lean-spec update <spec> --status <status> # Update status
49
- lean-spec link <spec> --related <other> # Add relationships
50
- lean-spec unlink <spec> --related <other> # Remove relationships
49
+ lean-spec link <spec> --depends-on <other> # Add dependencies
50
+ lean-spec unlink <spec> --depends-on <other> # Remove dependencies
51
51
  lean-spec deps <spec> # Show dependencies
52
52
  ```
53
53
 
@@ -65,7 +65,7 @@ lean-spec deps <spec> # Show dependencies
65
65
 
66
66
  4. 📊 **Update status to `in-progress`** BEFORE coding
67
67
  5. 📝 **Document decisions** in the spec as you work
68
- 6. 🔗 **Link related specs** if you discover connections
68
+ 6. 🔗 **Link dependencies** if you discover blocking relationships
69
69
 
70
70
  ### After Completing Work
71
71
 
@@ -106,17 +106,17 @@ lean-spec deps <spec> # Show dependencies
106
106
  - Trivial changes
107
107
  - Self-explanatory refactors
108
108
 
109
- ## Spec Relationships
109
+ ## Spec Dependencies
110
110
 
111
- ### `related` - Bidirectional Soft Reference
112
- Informational relationship between specs. Shown from both sides.
113
- **Use when:** Related topics, coordinated but not blocking work.
111
+ ### `depends_on` - Blocking Dependency
112
+ Directional dependency - this spec cannot start until dependencies are complete.
113
+ **Use when:** True blocking dependency, work order matters, one spec builds on another.
114
114
 
115
- ### `depends_on` - Directional Blocking Dependency
116
- Hard dependency - spec cannot start until dependencies complete.
117
- **Use when:** True blocking dependency, work order matters.
115
+ ```bash
116
+ lean-spec link <spec> --depends-on <other-spec>
117
+ ```
118
118
 
119
- **Default:** Use `related`. Reserve `depends_on` for true blockers.
119
+ **Note:** Only use `depends_on` for actual blocking dependencies. Don't link specs just because they're "related" - link them when one truly blocks the other.
120
120
 
121
121
  ## Quality Standards
122
122
 
@@ -1,5 +0,0 @@
1
- export { backfillCommand, backfillTimestamps } from './chunk-A6JDTXPV.js';
2
- import './chunk-LXOJW2FE.js';
3
- import './chunk-LVD7ZAVZ.js';
4
- //# sourceMappingURL=backfill-QIQLXSUG.js.map
5
- //# sourceMappingURL=backfill-QIQLXSUG.js.map