spets 0.1.57 → 0.1.58
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/index.js +55 -38
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -264,51 +264,57 @@ async function listPlugins() {
|
|
|
264
264
|
function getClaudeSkillContent() {
|
|
265
265
|
return `# Spets Workflow Executor
|
|
266
266
|
|
|
267
|
-
Orchestrator-controlled workflow. Execute
|
|
267
|
+
Orchestrator-controlled workflow. Execute immediately.
|
|
268
268
|
|
|
269
|
-
##
|
|
270
|
-
|
|
271
|
-
- NO EnterPlanMode, TaskCreate/TaskUpdate, subprocess spawning
|
|
272
|
-
- Execute immediately - no planning
|
|
273
|
-
|
|
274
|
-
## Execution Loop
|
|
269
|
+
## Start
|
|
275
270
|
|
|
271
|
+
Run this command with the user's task description:
|
|
276
272
|
\`\`\`bash
|
|
277
273
|
npx spets orchestrate init "$ARGUMENTS"
|
|
278
274
|
\`\`\`
|
|
279
275
|
|
|
280
|
-
|
|
276
|
+
## Main Loop
|
|
277
|
+
|
|
278
|
+
Repeat until \`type\` is \`"complete"\` or \`"error"\`:
|
|
279
|
+
|
|
280
|
+
1. Parse the JSON response
|
|
281
|
+
2. Execute the action for this \`type\`
|
|
282
|
+
3. Run the shell command in \`response.onComplete\`, piping JSON via stdin
|
|
283
|
+
4. Use the new JSON response, go to step 1
|
|
281
284
|
|
|
282
|
-
|
|
283
|
-
|
|
284
|
-
|
|
285
|
-
|
|
285
|
+
## How to Run onComplete
|
|
286
|
+
|
|
287
|
+
The \`onComplete\` field contains a complete shell command. Pipe your JSON result via stdin:
|
|
288
|
+
|
|
289
|
+
\`\`\`bash
|
|
290
|
+
echo '<your_json>' | npx spets orchestrate explore-done task-id-123
|
|
291
|
+
\`\`\`
|
|
286
292
|
|
|
287
|
-
## Actions
|
|
293
|
+
## Actions by Type
|
|
288
294
|
|
|
289
295
|
### type: "phase"
|
|
290
296
|
|
|
291
297
|
| phase | Action |
|
|
292
298
|
|-------|--------|
|
|
293
|
-
| explore | Follow \`
|
|
294
|
-
| clarify | Follow \`
|
|
295
|
-
| execute | Follow \`
|
|
296
|
-
| verify | Follow \`
|
|
299
|
+
| explore | Follow \`prompt\`, pipe explore JSON to \`onComplete\` |
|
|
300
|
+
| clarify | Follow \`prompt\`, pipe questions JSON to \`onComplete\` |
|
|
301
|
+
| execute | Follow \`prompt\`, write to \`context.output\`, run \`onComplete\` |
|
|
302
|
+
| verify | Follow \`prompt\`, pipe verify JSON to \`onComplete\` |
|
|
297
303
|
|
|
298
304
|
### type: "checkpoint"
|
|
299
305
|
|
|
300
306
|
| checkpoint | Action |
|
|
301
307
|
|------------|--------|
|
|
302
|
-
| clarify | AskUserQuestion for each \`
|
|
303
|
-
| approve | Read \`specPath\`, summarize, AskUserQuestion (Approve/Revise/Reject/Stop)
|
|
308
|
+
| clarify | Use AskUserQuestion for each item in \`questions\`, pipe answers JSON to \`onComplete\` |
|
|
309
|
+
| approve | Read \`specPath\`, summarize, use AskUserQuestion (Approve/Revise/Reject/Stop), run \`onComplete[choice]\` |
|
|
304
310
|
|
|
305
311
|
### type: "complete"
|
|
306
312
|
|
|
307
|
-
Print message and stop.
|
|
313
|
+
Print \`message\` and stop.
|
|
308
314
|
|
|
309
315
|
### type: "error"
|
|
310
316
|
|
|
311
|
-
Print error and stop.
|
|
317
|
+
Print \`error\` and stop.
|
|
312
318
|
|
|
313
319
|
---
|
|
314
320
|
|
|
@@ -324,46 +330,57 @@ description: SDD workflow executor - orchestrator-controlled spec-driven develop
|
|
|
324
330
|
|
|
325
331
|
# Spets Workflow Executor
|
|
326
332
|
|
|
327
|
-
Orchestrator-controlled workflow.
|
|
333
|
+
Orchestrator-controlled workflow.
|
|
328
334
|
|
|
329
|
-
##
|
|
335
|
+
## Start
|
|
330
336
|
|
|
337
|
+
Run this command with the user's task description:
|
|
331
338
|
\`\`\`bash
|
|
332
|
-
npx spets orchestrate init "
|
|
339
|
+
npx spets orchestrate init "user's task description here"
|
|
333
340
|
\`\`\`
|
|
334
341
|
|
|
335
|
-
|
|
342
|
+
## Main Loop
|
|
343
|
+
|
|
344
|
+
Repeat until \`type\` is \`"complete"\` or \`"error"\`:
|
|
345
|
+
|
|
346
|
+
1. Parse the JSON response
|
|
347
|
+
2. Execute the action for this \`type\`
|
|
348
|
+
3. Run the shell command in \`response.onComplete\`, piping JSON via stdin
|
|
349
|
+
4. Use the new JSON response, go to step 1
|
|
350
|
+
|
|
351
|
+
## How to Run onComplete
|
|
336
352
|
|
|
337
|
-
|
|
338
|
-
|
|
339
|
-
|
|
340
|
-
|
|
353
|
+
The \`onComplete\` field contains a complete shell command. Pipe your JSON result via stdin:
|
|
354
|
+
|
|
355
|
+
\`\`\`bash
|
|
356
|
+
echo '<your_json>' | npx spets orchestrate explore-done task-id-123
|
|
357
|
+
\`\`\`
|
|
341
358
|
|
|
342
|
-
## Actions
|
|
359
|
+
## Actions by Type
|
|
343
360
|
|
|
344
361
|
### type: "phase"
|
|
345
362
|
|
|
346
363
|
| phase | Action |
|
|
347
364
|
|-------|--------|
|
|
348
|
-
| explore | Follow \`
|
|
349
|
-
| clarify | Follow \`
|
|
350
|
-
| execute | Follow \`
|
|
351
|
-
| verify | Follow \`
|
|
365
|
+
| explore | Follow \`prompt\`, pipe explore JSON to \`onComplete\` |
|
|
366
|
+
| clarify | Follow \`prompt\`, pipe questions JSON to \`onComplete\` |
|
|
367
|
+
| execute | Follow \`prompt\`, write to \`context.output\`, run \`onComplete\` |
|
|
368
|
+
| verify | Follow \`prompt\`, pipe verify JSON to \`onComplete\` |
|
|
352
369
|
|
|
353
370
|
### type: "checkpoint"
|
|
354
371
|
|
|
355
372
|
| checkpoint | Action |
|
|
356
373
|
|------------|--------|
|
|
357
|
-
| clarify | Ask user each \`
|
|
358
|
-
| approve | Read \`specPath\`, summarize, ask user (Approve/Revise/Reject/Stop)
|
|
374
|
+
| clarify | Ask user each question in \`questions\`, pipe answers JSON to \`onComplete\` |
|
|
375
|
+
| approve | Read \`specPath\`, summarize, ask user (Approve/Revise/Reject/Stop), run \`onComplete[choice]\` |
|
|
359
376
|
|
|
360
377
|
### type: "complete"
|
|
361
378
|
|
|
362
|
-
Print message and stop.
|
|
379
|
+
Print \`message\` and stop.
|
|
363
380
|
|
|
364
381
|
### type: "error"
|
|
365
382
|
|
|
366
|
-
Print error and stop.
|
|
383
|
+
Print \`error\` and stop.
|
|
367
384
|
|
|
368
385
|
---
|
|
369
386
|
|