lean-spec 0.2.5-dev.20251124062211 → 0.2.5-dev.20251124070920
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.
- package/dist/{chunk-YE3BCNO6.js → chunk-LV7XEQ4D.js} +6 -6
- package/dist/chunk-LV7XEQ4D.js.map +1 -0
- package/dist/cli.js +1 -1
- package/dist/mcp-server.js +1 -1
- package/package.json +1 -1
- package/templates/_shared/agents-components/enterprise-approval.md +3 -1
- package/templates/_shared/agents-components/workflow-enterprise.md +3 -1
- package/templates/_shared/agents-components/workflow-standard-detailed.md +3 -1
- package/templates/_shared/agents-components/workflow-standard.md +3 -1
- package/templates/enterprise/files/AGENTS.md +6 -2
- package/templates/examples/dark-theme/README.md +25 -14
- package/templates/examples/dark-theme/package.json +2 -2
- package/templates/examples/dark-theme/src/public/app.js +257 -72
- package/templates/examples/dark-theme/src/public/index.html +205 -18
- package/templates/examples/dark-theme/src/public/style.css +548 -86
- package/templates/examples/dark-theme/src/server.js +3 -2
- package/templates/minimal/files/AGENTS.md +3 -1
- package/templates/standard/files/AGENTS.md +3 -1
- package/dist/chunk-YE3BCNO6.js.map +0 -1
|
@@ -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. **
|
|
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.)
|
|
@@ -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. **
|
|
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.)
|