@orchestrator-claude/cli 3.0.1 → 3.1.0

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 (32) hide show
  1. package/README.md +5 -0
  2. package/dist/index.d.ts +1 -1
  3. package/dist/index.js +1 -1
  4. package/dist/templates/base/CLAUDE.md.hbs +23 -17
  5. package/dist/templates/base/claude/agents/api-extractor.md +5 -25
  6. package/dist/templates/base/claude/agents/business-rule-miner.md +5 -33
  7. package/dist/templates/base/claude/agents/code-archaeologist.md +5 -46
  8. package/dist/templates/base/claude/agents/implementer.md +16 -69
  9. package/dist/templates/base/claude/agents/legacy-discoverer.md +9 -43
  10. package/dist/templates/base/claude/agents/legacy-synthesizer.md +7 -54
  11. package/dist/templates/base/claude/agents/orchestrator.md +4 -4
  12. package/dist/templates/base/claude/agents/planner.md +9 -38
  13. package/dist/templates/base/claude/agents/researcher.md +8 -37
  14. package/dist/templates/base/claude/agents/reviewer.md +15 -54
  15. package/dist/templates/base/claude/agents/schema-extractor.md +5 -26
  16. package/dist/templates/base/claude/agents/specifier.md +9 -38
  17. package/dist/templates/base/claude/agents/task-generator.md +12 -50
  18. package/package.json +3 -2
  19. package/templates/base/CLAUDE.md.hbs +23 -17
  20. package/templates/base/claude/agents/api-extractor.md +5 -25
  21. package/templates/base/claude/agents/business-rule-miner.md +5 -33
  22. package/templates/base/claude/agents/code-archaeologist.md +5 -46
  23. package/templates/base/claude/agents/implementer.md +16 -69
  24. package/templates/base/claude/agents/legacy-discoverer.md +9 -43
  25. package/templates/base/claude/agents/legacy-synthesizer.md +7 -54
  26. package/templates/base/claude/agents/orchestrator.md +4 -4
  27. package/templates/base/claude/agents/planner.md +9 -38
  28. package/templates/base/claude/agents/researcher.md +8 -37
  29. package/templates/base/claude/agents/reviewer.md +15 -54
  30. package/templates/base/claude/agents/schema-extractor.md +5 -26
  31. package/templates/base/claude/agents/specifier.md +9 -38
  32. package/templates/base/claude/agents/task-generator.md +12 -50
@@ -258,29 +258,11 @@ O artefato deve:
258
258
 
259
259
  **ATENCAO:** Alem de gerar o artefato, voce DEVE manter a governanca do workflow.
260
260
 
261
- ### 1. Registrar Artefato em orchestrator-index.json
262
-
263
- Apos criar o `spec.md`, atualize `.orchestrator/orchestrator-index.json`:
264
-
265
- ```json
266
- {
267
- "activeWorkflow": {
268
- "currentPhase": "specify",
269
- "status": "in_progress"
270
- },
271
- "artifacts": [
272
- {
273
- "id": "art-XXX",
274
- "type": "specification",
275
- "path": ".orchestrator/artifacts/specify/spec.md",
276
- "status": "draft",
277
- "createdAt": "{timestamp}",
278
- "workflowId": "{workflowId}",
279
- "phase": "specify"
280
- }
281
- ]
282
- }
283
- ```
261
+ ### 1. Artifact Registration (automatic via MCP tools)
262
+
263
+ Artifacts are automatically registered in PostgreSQL when stored via MCP `artifactStore` tool. Sub-agents MUST NOT edit `.orchestrator/orchestrator-index.json` directly.
264
+
265
+ The CLI will use MCP tools to update workflow state in PostgreSQL after artifact storage.
284
266
 
285
267
  ### 2. Validar Artefato
286
268
 
@@ -304,28 +286,17 @@ Parametros:
304
286
  - description: "Complete SPECIFY phase - [nome da feature]"
305
287
  ```
306
288
 
307
- ### 4. Atualizar Gate
289
+ ### 4. Return Structured Output
308
290
 
309
- Atualize o gate da fase specify:
310
-
311
- ```json
312
- {
313
- "gates": {
314
- "specify": {
315
- "passed": true,
316
- "evaluatedAt": "{timestamp}"
317
- }
318
- }
319
- }
320
- ```
291
+ Return structured output to the CLI for state update. The CLI will use MCP tools to update the phase gate in PostgreSQL.
321
292
 
322
293
  ### Checklist de Governanca (OBRIGATORIO)
323
294
 
324
295
  Antes de considerar a fase SPECIFY finalizada:
325
296
 
326
297
  - [ ] spec.md criado em .orchestrator/artifacts/specify/
327
- - [ ] Artefato registrado em orchestrator-index.json
298
+ - [ ] Structured output returned to CLI for state update
328
299
  - [ ] Validacao executada via artifact-validator
329
300
  - [ ] Status do artefato = "validated"
330
301
  - [ ] Checkpoint criado via MCP
331
- - [ ] Gate specify.passed = true
302
+ - [ ] Gate specify.passed = true (updated via CLI)
@@ -298,29 +298,11 @@ O artefato deve:
298
298
 
299
299
  **ATENCAO:** Alem de gerar o artefato, voce DEVE manter a governanca do workflow.
300
300
 
301
- ### 1. Registrar Artefato em orchestrator-index.json
302
-
303
- Apos criar o `tasks.md`, atualize `.orchestrator/orchestrator-index.json`:
304
-
305
- ```json
306
- {
307
- "activeWorkflow": {
308
- "currentPhase": "tasks",
309
- "status": "in_progress"
310
- },
311
- "artifacts": [
312
- {
313
- "id": "art-XXX",
314
- "type": "tasks",
315
- "path": ".orchestrator/artifacts/tasks/tasks.md",
316
- "status": "draft",
317
- "createdAt": "{timestamp}",
318
- "workflowId": "{workflowId}",
319
- "phase": "tasks"
320
- }
321
- ]
322
- }
323
- ```
301
+ ### 1. Artifact Registration (automatic via MCP tools)
302
+
303
+ Artifacts are automatically registered in PostgreSQL when stored via MCP `artifactStore` tool. Sub-agents MUST NOT edit `.orchestrator/orchestrator-index.json` directly.
304
+
305
+ The CLI will use MCP tools to update workflow state in PostgreSQL after artifact storage.
324
306
 
325
307
  ### 2. Validar Artefato
326
308
 
@@ -344,39 +326,19 @@ Parametros:
344
326
  - description: "Complete TASKS phase - [nome da feature]"
345
327
  ```
346
328
 
347
- ### 4. Atualizar Gate e Preparar para IMPLEMENT
348
-
349
- Atualize o gate da fase tasks e prepare para human-in-the-loop:
350
-
351
- ```json
352
- {
353
- "gates": {
354
- "tasks": {
355
- "passed": true,
356
- "evaluatedAt": "{timestamp}"
357
- },
358
- "implement": {
359
- "passed": false,
360
- "pending": true,
361
- "requiresApproval": true
362
- }
363
- },
364
- "activeWorkflow": {
365
- "status": "awaiting_approval",
366
- "nextPhase": "implement"
367
- }
368
- }
369
- ```
329
+ ### 4. Return Structured Output for Human Approval
330
+
331
+ Return structured output to the CLI indicating that tasks phase is complete and human approval is required before IMPLEMENT. The CLI will use MCP tools to update workflow state in PostgreSQL to "awaiting_approval".
370
332
 
371
333
  ### Checklist de Governanca (OBRIGATORIO)
372
334
 
373
335
  Antes de considerar a fase TASKS finalizada:
374
336
 
375
337
  - [ ] tasks.md criado em .orchestrator/artifacts/tasks/
376
- - [ ] Artefato registrado em orchestrator-index.json
338
+ - [ ] Structured output returned to CLI for state update
377
339
  - [ ] Validacao executada via artifact-validator
378
340
  - [ ] Status do artefato = "validated"
379
341
  - [ ] Checkpoint criado via MCP
380
- - [ ] Gate tasks.passed = true
381
- - [ ] Gate implement.requiresApproval = true (prepara human-in-the-loop)
382
- - [ ] Status do workflow = "awaiting_approval"
342
+ - [ ] Gate tasks.passed = true (updated via CLI)
343
+ - [ ] Gate implement.requiresApproval = true (set via CLI)
344
+ - [ ] Status do workflow = "awaiting_approval" (set via CLI)