opencode-multiagent 0.6.0 → 0.7.0

package/docs/usage-guide.md

@@ -56,6 +56,41 @@ user -> brainstormer -> (concludes with brief) -> planner -> executor -> ...
 | `brainstormer` | Explores ideas with the user before planning. Produces a planner brief.    |
 | `planner`      | Owns triage, planning, challenge, inspection, and result integration.      |
 | `executor`     | Runs the plan by dispatching bounded coding tasks and validating results.  |
+| `architect`    | Evaluates technical direction and produces implementation briefs.           |
+
+### Workflow gateways
+
+Every work type has a mandatory gate sequence. `planner` selects the gateway and `executor`
+enforces it. No gate can be skipped.
+
+| Work type          | Mandatory gateway                                                                    |
+| ------------------ | ------------------------------------------------------------------------------------ |
+| Standard feature   | `planner -> executor -> coder -> tester -> reviewer -> done`                         |
+| Security work      | `planner -> architect -> executor -> sec-coder -> tester -> reviewer -> done`        |
+| Big refactor       | `planner -> scout -> architect -> auditor -> executor -> [phased coder -> tester -> reviewer] -> done` |
+| Ops / infra        | `planner -> architect -> executor -> ops-coder -> reviewer -> done`                  |
+| Deep bug fix       | `planner -> executor -> scout -> reviewer(evidence) -> coder -> tester -> reviewer -> done` |
+| Docs only          | `planner -> executor -> docmaster -> done`                                           |
+| UI work            | `planner -> executor -> ui-coder -> tester -> reviewer -> done`                      |
+
+### Acceptance output standard
+
+Every agent returns a structured verdict that `executor` can parse:
+
+| Agent       | Verdict values                              | Required sections                                    |
+| ----------- | ------------------------------------------- | ---------------------------------------------------- |
+| `planner`   | TIER 0/1/2/3                                | Triage, Plan, Route, Verification Gates              |
+| `executor`  | PASS / IN_PROGRESS / BLOCKED / ESCALATED    | Execution Status, Task Board, Verification           |
+| `architect` | RECOMMENDED DIRECTION / NEEDS MORE RESEARCH / REJECTED | Verdict, Trade-offs, Implementation Brief, Risks     |
+| `coder`     | DONE / ESCALATE / BLOCKED                   | Verdict, Files, Verification, Review                 |
+| `ui-coder`  | DONE / ESCALATE / BLOCKED                   | Verdict, Files, Visual Behavior, Review              |
+| `sec-coder` | DONE / ESCALATE / BLOCKED                   | Verdict, Security Analysis, Attack Surface, Review   |
+| `tester`    | PASS / FAIL / GAPS                          | Verdict, Test Files, Coverage, Findings              |
+| `ops-coder` | DONE / ESCALATE / BLOCKED                   | Verdict, Files, Validation, Review                   |
+| `reviewer`  | OKAY / REJECT                               | Verdict, Findings, Verification                      |
+| `auditor`   | PASS / FAIL (HIGH/MEDIUM/LOW)               | Verdict, Gaps Found, Missing Gates                   |
+| `docmaster` | DONE / REJECTED                             | Verdict, Changed Paths                               |
+| `scout`     | (research output)                           | Files, Patterns, Open Questions                      |
 
 ## 4. Triage Levels
 
@@ -64,8 +99,8 @@ user -> brainstormer -> (concludes with brief) -> planner -> executor -> ...
 | Tier     | Meaning                                                  | Typical route                                |
 | -------- | -------------------------------------------------------- | -------------------------------------------- |
 | `Tier 0` | Trivial single-file work                                 | `planner -> executor -> coder`               |
-| `Tier 1` | Bounded work                                             | `planner -> executor -> coder/ui-coder/sec-coder` |
-| `Tier 2` | Complex multi-module work                                | `planner -> auditor -> executor -> coders`   |
+| `Tier 1` | Bounded work                                             | `planner -> executor -> coder/ui-coder/sec-coder/tester/ops-coder` |
+| `Tier 2` | Complex multi-module work                                | `planner -> auditor -> executor -> coders/tester/ops-coder` |
 | `Tier 3` | Inspection                                               | `planner` (inspection mode)                  |
 
 As a user, the practical takeaway is simple: ask for the task naturally and let `planner` decide
@@ -85,14 +120,30 @@ understand when reading logs or `.opencode` artifacts.
 
 ### Task lifecycle
 
-Possible task states:
-
-- `pending`
-- `claimed`
-- `in_progress`
-- `completed`
-- `failed`
-- `blocked`
+The task board uses a state machine with the following states:
+
+| State                    | Meaning                                                              |
+| ------------------------ | -------------------------------------------------------------------- |
+| `pending`                | Created but not yet picked up                                        |
+| `triaged`                | `planner` has classified the work                                    |
+| `planned`                | A durable plan exists for this task                                  |
+| `architecture_approved`  | `architect` has approved the technical direction                     |
+| `claimed`                | An agent has claimed the task but not yet started                    |
+| `in_progress`            | Active implementation underway                                       |
+| `in_review`              | Implementation complete, under `reviewer` review                     |
+| `in_test`                | Under `tester` verification                                          |
+| `completed`              | All gates passed, work is done                                       |
+| `failed`                 | Work failed (may trigger retry/escalation)                           |
+| `rejected`               | `reviewer` or `auditor` rejected the work                            |
+| `blocked`                | Cannot proceed due to unmet dependencies or external blockers        |
+
+State transition rules:
+- `pending` -> `triaged` -> `planned` -> `architecture_approved` -> `claimed` -> `in_progress` -> `in_review` -> `in_test` -> `completed` (happy path)
+- Any active state -> `blocked` (when dependencies are unmet)
+- `in_review` -> `rejected` -> `in_progress` (when reviewer rejects)
+- `in_test` -> `rejected` -> `in_progress` (when tests fail and code needs changes)
+- Any active state -> `failed` (on unrecoverable error)
+- Dependency enforcement: `claimed`, `in_progress`, `in_review`, and `in_test` require all dependencies to be `completed`
 
 ### Retry and escalation
 

package/docs/usage-guide.tr.md

@@ -56,6 +56,41 @@ kullanici -> brainstormer -> (brief ile sonuçlanır) -> planner -> executor ->
 | `brainstormer` | Planlama öncesi kullanıcıyla fikirleri keşfeder, planner'a hazır brief üretir.        |
 | `planner`      | Talebi triage eder, route seçer, büyük işler için plan üretir, sonuçları inceler.     |
 | `executor`     | Planı bounded uzman görevlerine bölerek uygular ve sonuçları doğrular.                |
+| `architect`    | Teknik yönü değerlendirir ve implementation brief üretir.                              |
+
+### Workflow kapıları (Gateway'ler)
+
+Her iş tipi zorunlu bir kapı sırasına sahiptir. `planner` kapıyı seçer, `executor` uygular.
+Hiçbir kapı atlanamaz.
+
+| İş tipi              | Zorunlu akış                                                                           |
+| -------------------- | -------------------------------------------------------------------------------------- |
+| Standart feature     | `planner -> executor -> coder -> tester -> reviewer -> done`                           |
+| Güvenlik işi         | `planner -> architect -> executor -> sec-coder -> tester -> reviewer -> done`          |
+| Büyük refactor       | `planner -> scout -> architect -> auditor -> executor -> [fazlı coder -> tester -> reviewer] -> done` |
+| Ops / altyapı        | `planner -> architect -> executor -> ops-coder -> reviewer -> done`                    |
+| Derin bug fix        | `planner -> executor -> scout -> reviewer(kanıt) -> coder -> tester -> reviewer -> done` |
+| Sadece dokümantasyon | `planner -> executor -> docmaster -> done`                                             |
+| UI işi               | `planner -> executor -> ui-coder -> tester -> reviewer -> done`                        |
+
+### Kabul çıktı standardı
+
+Her ajan, `executor`'un ayrıştırabileceği yapılandırılmış bir verdict döndürür:
+
+| Ajan        | Verdict değerleri                           | Zorunlu bölümler                                     |
+| ----------- | ------------------------------------------- | ---------------------------------------------------- |
+| `planner`   | TIER 0/1/2/3                                | Triage, Plan, Route, Verification Gates              |
+| `executor`  | PASS / IN_PROGRESS / BLOCKED / ESCALATED    | Execution Status, Task Board, Verification           |
+| `architect` | RECOMMENDED DIRECTION / NEEDS MORE RESEARCH / REJECTED | Verdict, Trade-offs, Implementation Brief, Risks     |
+| `coder`     | DONE / ESCALATE / BLOCKED                   | Verdict, Files, Verification, Review                 |
+| `ui-coder`  | DONE / ESCALATE / BLOCKED                   | Verdict, Files, Visual Behavior, Review              |
+| `sec-coder` | DONE / ESCALATE / BLOCKED                   | Verdict, Security Analysis, Attack Surface, Review   |
+| `tester`    | PASS / FAIL / GAPS                          | Verdict, Test Files, Coverage, Findings              |
+| `ops-coder` | DONE / ESCALATE / BLOCKED                   | Verdict, Files, Validation, Review                   |
+| `reviewer`  | OKAY / REJECT                               | Verdict, Findings, Verification                      |
+| `auditor`   | PASS / FAIL (HIGH/MEDIUM/LOW)               | Verdict, Gaps Found, Missing Gates                   |
+| `docmaster` | DONE / REJECTED                             | Verdict, Changed Paths                               |
+| `scout`     | (araştırma çıktısı)                         | Files, Patterns, Open Questions                      |
 
 ## 4. Triage Seviyeleri (Tier Modeli)
 
@@ -64,8 +99,8 @@ kullanici -> brainstormer -> (brief ile sonuçlanır) -> planner -> executor ->
 | Tier     | Açıklama                                       | Rota                                          |
 | -------- | ---------------------------------------------- | --------------------------------------------- |
 | `Tier 0` | Küçük, açık işler                              | `planner -> executor -> coder`                |
-| `Tier 1` | Bounded işler                                  | `planner -> executor -> coder/ui-coder/sec-coder` |
-| `Tier 2` | Karmaşık çok modüllü işler                     | `planner -> auditor -> executor -> coders`    |
+| `Tier 1` | Bounded işler                                  | `planner -> executor -> coder/ui-coder/sec-coder/tester/ops-coder` |
+| `Tier 2` | Karmaşık çok modüllü işler                     | `planner -> auditor -> executor -> coders/tester/ops-coder` |
 | `Tier 3` | İnceleme                                       | `planner` (inspeksiyon modu)                  |
 
 Kullanıcı açısından pratik kural basittir: güçlü bir sebep yoksa görevi doğal şekilde tarif edin ve
@@ -85,14 +120,30 @@ nasıl oluştuğunu anlamak için bilinmeleri faydalıdır.
 
 ### Task yaşam döngüsü
 
-Olası task durumları:
-
-- `pending`
-- `claimed`
-- `in_progress`
-- `completed`
-- `failed`
-- `blocked`
+Task board aşağıdaki durumları olan bir state machine kullanır:
+
+| Durum                    | Anlamı                                                                |
+| ------------------------ | --------------------------------------------------------------------- |
+| `pending`                | Oluşturuldu, henüz alınmadı                                          |
+| `triaged`                | `planner` işi sınıflandırdı                                          |
+| `planned`                | Bu görev için kalıcı bir plan mevcut                                  |
+| `architecture_approved`  | `architect` teknik yönü onayladı                                      |
+| `claimed`                | Bir ajan görevi aldı ama henüz başlamadı                              |
+| `in_progress`            | Aktif implementasyon devam ediyor                                     |
+| `in_review`              | İmplementasyon tamam, `reviewer` incelemesinde                        |
+| `in_test`                | `tester` doğrulamasında                                               |
+| `completed`              | Tüm kapılar geçildi, iş tamamlandı                                   |
+| `failed`                 | İş başarısız oldu (retry/escalation tetikleyebilir)                   |
+| `rejected`               | `reviewer` veya `auditor` işi reddetti                                |
+| `blocked`                | Karşılanmamış bağımlılıklar veya dış engeller nedeniyle ilerlenemiyor |
+
+Durum geçiş kuralları:
+- `pending` -> `triaged` -> `planned` -> `architecture_approved` -> `claimed` -> `in_progress` -> `in_review` -> `in_test` -> `completed` (mutlu yol)
+- Herhangi bir aktif durum -> `blocked` (bağımlılıklar karşılanmadığında)
+- `in_review` -> `rejected` -> `in_progress` (reviewer reddettiğinde)
+- `in_test` -> `rejected` -> `in_progress` (testler başarısız olup kod değişikliği gerektiğinde)
+- Herhangi bir aktif durum -> `failed` (kurtarılamaz hata durumunda)
+- Bağımlılık zorunluluğu: `claimed`, `in_progress`, `in_review` ve `in_test` durumları tüm bağımlılıkların `completed` olmasını gerektirir
 
 ### Yeniden deneme ve yükseltme
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-multiagent",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "type": "module",
   "description": "Multi-agent orchestration plugin for OpenCode",
   "license": "MIT",