lean-spec 0.2.5-dev.20251124062211 → 0.2.5-dev.20251124064307

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 (12) hide show
  1. package/dist/{chunk-YE3BCNO6.js → chunk-FYYLWDI6.js} +3 -3
  2. package/dist/{chunk-YE3BCNO6.js.map → chunk-FYYLWDI6.js.map} +1 -1
  3. package/dist/cli.js +1 -1
  4. package/dist/mcp-server.js +1 -1
  5. package/package.json +1 -1
  6. package/templates/_shared/agents-components/enterprise-approval.md +3 -1
  7. package/templates/_shared/agents-components/workflow-enterprise.md +3 -1
  8. package/templates/_shared/agents-components/workflow-standard-detailed.md +3 -1
  9. package/templates/_shared/agents-components/workflow-standard.md +3 -1
  10. package/templates/enterprise/files/AGENTS.md +6 -2
  11. package/templates/minimal/files/AGENTS.md +3 -1
  12. package/templates/standard/files/AGENTS.md +3 -1
package/dist/cli.js CHANGED
@@ -1,4 +1,4 @@
1
- import { analyzeCommand, archiveCommand, backfillCommand, boardCommand, checkCommand, compactCommand, createCommand, depsCommand, examplesCommand, filesCommand, ganttCommand, initCommand, linkCommand, listCommand, mcpCommand, migrateCommand, openCommand, searchCommand, splitCommand, statsCommand, templatesCommand, timelineCommand, tokensCommand, uiCommand, unlinkCommand, updateCommand, validateCommand, viewCommand } from './chunk-YE3BCNO6.js';
1
+ import { analyzeCommand, archiveCommand, backfillCommand, boardCommand, checkCommand, compactCommand, createCommand, depsCommand, examplesCommand, filesCommand, ganttCommand, initCommand, linkCommand, listCommand, mcpCommand, migrateCommand, openCommand, searchCommand, splitCommand, statsCommand, templatesCommand, timelineCommand, tokensCommand, uiCommand, unlinkCommand, updateCommand, validateCommand, viewCommand } from './chunk-FYYLWDI6.js';
2
2
  import './chunk-LVD7ZAVZ.js';
3
3
  import { Command } from 'commander';
4
4
  import { readFileSync } from 'fs';
package/dist/mcp-server.js CHANGED
@@ -1,5 +1,5 @@
1
1
  #!/usr/bin/env node
2
- export { createMcpServer } from './chunk-YE3BCNO6.js';
2
+ export { createMcpServer } from './chunk-FYYLWDI6.js';
3
3
  import './chunk-LVD7ZAVZ.js';
4
4
  //# sourceMappingURL=mcp-server.js.map
5
5
  //# sourceMappingURL=mcp-server.js.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lean-spec",
3
- "version": "0.2.5-dev.20251124062211",
3
+ "version": "0.2.5-dev.20251124064307",
4
4
  "description": "Specification-driven development made simple",
5
5
  "type": "module",
6
6
  "bin": {
package/templates/_shared/agents-components/enterprise-approval.md CHANGED
@@ -7,4 +7,6 @@
7
7
  5. **Stakeholder sign-off** - Update status to `planned`
8
8
  6. **Implementation** - Update status to `in-progress`, keep spec in sync
9
9
  7. **Final review** - Before deployment
10
- 8. **Complete & archive** - Mark `complete`, then archive
10
+ 8. **Complete** - Mark `complete` after successful deployment
11
+
12
+ **Note**: Archive specs only when they're no longer actively referenced (weeks/months later), not immediately after completion.
package/templates/_shared/agents-components/workflow-enterprise.md CHANGED
@@ -6,6 +6,8 @@
6
6
  6. **Start implementation** - Mark `in-progress` BEFORE implementing what the spec describes
7
7
  7. **Implement changes** - Keep spec in sync, update status appropriately
8
8
  8. **Complete implementation** - Mark `complete` AFTER implementing what the spec describes
9
- 9. **Archive when done** - `lean-spec archive <spec>` after completion
9
+ 9. **Document** - Report progress and document changes into the spec
10
10
 
11
11
  **Remember**: Status tracks implementation work, not spec document creation. Creating a spec = planning (stays `planned` until implementation starts).
12
+
13
+ **Note on Archiving**: Archive specs when they're no longer actively referenced (weeks/months after completion), not immediately. Used for historical specs, not recent work. Use `lean-spec archive <spec>` to move old specs to `archived/` directory.
package/templates/_shared/agents-components/workflow-standard-detailed.md CHANGED
@@ -5,6 +5,8 @@
5
5
  5. **Start implementation** - Mark `in-progress` BEFORE implementing what the spec describes
6
6
  6. **Implement changes** - Keep spec in sync as you learn
7
7
  7. **Complete implementation** - Mark `complete` AFTER implementing what the spec describes
8
- 8. **Archive when done** - `lean-spec archive <spec>` moves to archive
8
+ 8. **Document** - Report progress and document changes into the spec
9
9
 
10
10
  **Remember**: Status tracks implementation work, not spec document creation. Creating a spec = planning (stays `planned` until implementation starts).
11
+
12
+ **Note on Archiving**: Archive specs when they're no longer actively referenced (weeks/months after completion), not immediately. Use `lean-spec archive <spec>` to move old specs to `archived/` directory.
package/templates/_shared/agents-components/workflow-standard.md CHANGED
@@ -3,6 +3,8 @@
3
3
  3. **Start implementation** - Mark `in-progress` BEFORE implementing what the spec describes
4
4
  4. **Implement changes** - Keep spec in sync as you learn
5
5
  5. **Complete implementation** - Mark `complete` AFTER implementing what the spec describes
6
- 6. **Archive when done** - `lean-spec archive <spec>` moves to archive
6
+ 6. **Document** - Report progress and document changes into the spec
7
7
 
8
8
  **Remember**: Status tracks implementation work, not spec document creation. Creating a spec = planning (stays `planned` until implementation starts).
9
+
10
+ **Note on Archiving**: Archive specs when they're no longer actively referenced (weeks/months after completion), not immediately. Use `lean-spec archive <spec>` to move old specs to `archived/` directory.
package/templates/enterprise/files/AGENTS.md CHANGED
@@ -146,7 +146,9 @@ Optional for:
146
146
  5. **Stakeholder sign-off** - Update status to `planned`
147
147
  6. **Implementation** - Update status to `in-progress`, keep spec in sync
148
148
  7. **Final review** - Before deployment
149
- 8. **Complete & archive** - Mark `complete`, then archive
149
+ 8. **Complete** - Mark `complete` after successful deployment
150
+
151
+ **Note**: Archive specs only when they're no longer actively referenced (weeks/months later), not immediately after completion.
150
152
 
151
153
  ## Workflow
152
154
 
@@ -158,9 +160,11 @@ Optional for:
158
160
  6. **Start implementation** - Mark `in-progress` BEFORE implementing what the spec describes
159
161
  7. **Implement changes** - Keep spec in sync, update status appropriately
160
162
  8. **Complete implementation** - Mark `complete` AFTER implementing what the spec describes
161
- 9. **Archive when done** - `lean-spec archive <spec>` after completion
163
+ 9. **Document** - Report progress and document changes into the spec
162
164
 
163
165
  **Remember**: Status tracks implementation work, not spec document creation. Creating a spec = planning (stays `planned` until implementation starts).
166
+
167
+ **Note on Archiving**: Archive specs when they're no longer actively referenced (weeks/months after completion), not immediately. Used for historical specs, not recent work. Use `lean-spec archive <spec>` to move old specs to `archived/` directory.
164
168
  **CRITICAL - What "Work" Means:**
165
169
  - ❌ **NOT**: Creating/writing the spec document itself
166
170
  - ✅ **YES**: Implementing what the spec describes (code, docs, features, etc.)
package/templates/minimal/files/AGENTS.md CHANGED
@@ -81,9 +81,11 @@ lean-spec update <spec> --status in-progress
81
81
  3. **Start implementation** - Mark `in-progress` BEFORE implementing what the spec describes
82
82
  4. **Implement changes** - Keep spec in sync as you learn
83
83
  5. **Complete implementation** - Mark `complete` AFTER implementing what the spec describes
84
- 6. **Archive when done** - `lean-spec archive <spec>` moves to archive
84
+ 6. **Document** - Report progress and document changes into the spec
85
85
 
86
86
  **Remember**: Status tracks implementation work, not spec document creation. Creating a spec = planning (stays `planned` until implementation starts).
87
+
88
+ **Note on Archiving**: Archive specs when they're no longer actively referenced (weeks/months after completion), not immediately. Use `lean-spec archive <spec>` to move old specs to `archived/` directory.
87
89
  **CRITICAL - What "Work" Means:**
88
90
  - ❌ **NOT**: Creating/writing the spec document itself
89
91
  - ✅ **YES**: Implementing what the spec describes (code, docs, features, etc.)
package/templates/standard/files/AGENTS.md CHANGED
@@ -107,9 +107,11 @@ lean-spec update <spec> --status in-progress --assignee yourname
107
107
  5. **Start implementation** - Mark `in-progress` BEFORE implementing what the spec describes
108
108
  6. **Implement changes** - Keep spec in sync as you learn
109
109
  7. **Complete implementation** - Mark `complete` AFTER implementing what the spec describes
110
- 8. **Archive when done** - `lean-spec archive <spec>` moves to archive
110
+ 8. **Document** - Report progress and document changes into the spec
111
111
 
112
112
  **Remember**: Status tracks implementation work, not spec document creation. Creating a spec = planning (stays `planned` until implementation starts).
113
+
114
+ **Note on Archiving**: Archive specs when they're no longer actively referenced (weeks/months after completion), not immediately. Use `lean-spec archive <spec>` to move old specs to `archived/` directory.
113
115
  **CRITICAL - What "Work" Means:**
114
116
  - ❌ **NOT**: Creating/writing the spec document itself
115
117
  - ✅ **YES**: Implementing what the spec describes (code, docs, features, etc.)