thoth-agents 0.1.5 → 0.1.7

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "thoth-agents",
3
- "version": "0.1.5",
3
+ "version": "0.1.7",
4
4
  "description": "Delegate-first OpenCode plugin with seven agents, thoth-mem persistence, and bundled SDD skills.",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -61,6 +61,8 @@
61
61
  "@modelcontextprotocol/sdk": "^1.26.0",
62
62
  "@opencode-ai/plugin": "1.4.7",
63
63
  "@opencode-ai/sdk": "1.4.7",
64
+ "ink": "^7.0.3",
65
+ "react": "^19.2.6",
64
66
  "unique-names-generator": "^4.7.1",
65
67
  "vscode-jsonrpc": "^8.2.0",
66
68
  "vscode-languageserver-protocol": "^3.17.5",
@@ -70,7 +72,9 @@
70
72
  "devDependencies": {
71
73
  "@biomejs/biome": "2.4.2",
72
74
  "@types/node": "^22.19.19",
75
+ "@types/react": "^19.2.15",
73
76
  "@types/which": "^3.0.4",
77
+ "ink-testing-library": "^4.0.0",
74
78
  "tsup": "^8.5.1",
75
79
  "tsx": "4.22.2",
76
80
  "typescript": "^5.9.3",
@@ -1,11 +1,13 @@
1
1
  ---
2
2
  name: sdd-design
3
- description: Create `design.md` with architecture decisions and file changes.
3
+ description: Create `design.md` as a technical solution design with architecture decisions and file changes.
4
4
  ---
5
5
 
6
6
  # SDD Design Skill
7
7
 
8
- Create the technical design that explains how the approved spec will be built.
8
+ Create the technical solution design that explains how the approved spec will
9
+ be built. OpenSpec `design.md` is a technical approach artifact covering
10
+ implementation architecture, tradeoffs, and repository patterns.
9
11
 
10
12
  ## Shared Conventions
11
13
 
@@ -28,6 +30,10 @@ The orchestrator passes the artifact store mode (`thoth-mem`, `openspec`, or
28
30
  - Proposal and specs exist and implementation planning needs technical depth
29
31
  - A prior design needs to be revised after spec changes
30
32
 
33
+ This phase is not a UI/UX design task. Do not route this phase to the designer
34
+ agent because it is named `design`; the default implementation owner is a
35
+ technical write-capable role such as `deep`.
36
+
31
37
  ## Prerequisites
32
38
 
33
39
  - `change-name`
@@ -86,6 +92,10 @@ Return:
86
92
  ## Rules
87
93
 
88
94
  - Base the design on the actual codebase, not generic assumptions.
95
+ - Do not route this phase to the designer agent. `sdd-design` itself always
96
+ stays with the technical write-capable agent.
97
+ - Later `sdd-apply` tasks may route to the designer agent when the work is
98
+ specifically user-facing UI, visual work, screenshots, or visual QA.
89
99
  - Every architecture decision must include rationale.
90
100
  - Use concrete file paths and interfaces.
91
101
  - Keep implementation details aligned with the spec and repository patterns.