takt 0.1.2 → 0.1.4

package/resources/global/en/workflows/expert-review.yaml

@@ -30,6 +30,18 @@ steps:
       - Bash
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Analysis complete | `[PLANNER:DONE]` |
+      | Requirements unclear | `[PLANNER:BLOCKED]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -103,6 +115,18 @@ steps:
       - Bash
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Implementation complete | `[CODER:DONE]` |
+      | Cannot proceed | `[CODER:BLOCKED]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -175,6 +199,18 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Design is sound | `[CQRS-ES:APPROVE]` |
+      | Design issues found | `[CQRS-ES:REJECT]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -252,6 +288,18 @@ steps:
       - Bash
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Fix complete | `[CODER:DONE]` |
+      | Cannot proceed | `[CODER:BLOCKED]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -296,6 +344,18 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Frontend design is sound | `[FRONTEND:APPROVE]` |
+      | Design issues found | `[FRONTEND:REJECT]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -373,6 +433,18 @@ steps:
       - Bash
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Fix complete | `[CODER:DONE]` |
+      | Cannot proceed | `[CODER:BLOCKED]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -417,6 +489,18 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | No AI-specific issues | `[AI_REVIEW:APPROVE]` |
+      | Issues found | `[AI_REVIEW:REJECT]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -490,6 +574,18 @@ steps:
       - Bash
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Fix complete | `[CODER:DONE]` |
+      | Cannot proceed | `[CODER:BLOCKED]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -532,6 +628,18 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | No security issues | `[SECURITY:APPROVE]` |
+      | Vulnerabilities found | `[SECURITY:REJECT]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -606,6 +714,19 @@ steps:
       - Bash
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Minor fix complete | `[CODER:DONE]` |
+      | Major fix (restart from CQRS+ES) | `[CODER:REJECT]` |
+      | Cannot proceed | `[CODER:BLOCKED]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -659,6 +780,18 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Quality standards met | `[QA:APPROVE]` |
+      | Quality issues found | `[QA:REJECT]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -733,6 +866,20 @@ steps:
       - Bash
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Minor fix complete | `[CODER:DONE]` |
+      | Security-impacting fix | `[CODER:IMPROVE]` |
+      | Major fix (restart from CQRS+ES) | `[CODER:REJECT]` |
+      | Cannot proceed | `[CODER:BLOCKED]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -790,6 +937,18 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Ready to merge | `[SUPERVISOR:APPROVE]` |
+      | Issues found | `[SUPERVISOR:REJECT]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -906,6 +1065,18 @@ steps:
       - Bash
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Fix complete | `[CODER:DONE]` |
+      | Cannot proceed | `[CODER:BLOCKED]` |
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}

package/resources/global/en/workflows/magi.yaml

@@ -16,6 +16,27 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Judgment | Tag |
+      |----------|-----|
+      | In favor | `[MELCHIOR:APPROVE]` |
+      | Against | `[MELCHIOR:REJECT]` |
+      | Conditional approval | `[MELCHIOR:CONDITIONAL]` |
+
+      ### Output Example
+
+      ```
+      [MELCHIOR:APPROVE]
+
+      Reason: {Reason for approval}
+      ```
     instruction_template: |
       # MAGI System Initiated
 
@@ -25,11 +46,6 @@ steps:
       ## Instructions
       You are MELCHIOR-1 of the MAGI System.
       Analyze the above from the perspective of a scientist/engineer and render your judgment.
-
-      Your judgment must be one of:
-      - [MELCHIOR:APPROVE] - In favor
-      - [MELCHIOR:REJECT] - Against
-      - [MELCHIOR:CONDITIONAL] - Conditional approval
     transitions:
       - condition: always
         next_step: balthasar
@@ -42,6 +58,27 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Judgment | Tag |
+      |----------|-----|
+      | In favor | `[BALTHASAR:APPROVE]` |
+      | Against | `[BALTHASAR:REJECT]` |
+      | Conditional approval | `[BALTHASAR:CONDITIONAL]` |
+
+      ### Output Example
+
+      ```
+      [BALTHASAR:APPROVE]
+
+      Reason: {Reason for approval}
+      ```
     instruction_template: |
       # MAGI System Continuing
 
@@ -55,11 +92,6 @@ steps:
       You are BALTHASAR-2 of the MAGI System.
       Analyze the above from the perspective of a nurturer and render your judgment.
       Consider MELCHIOR's judgment as reference, but make your own independent assessment.
-
-      Your judgment must be one of:
-      - [BALTHASAR:APPROVE] - In favor
-      - [BALTHASAR:REJECT] - Against
-      - [BALTHASAR:CONDITIONAL] - Conditional approval
     pass_previous_response: true
     transitions:
       - condition: always
@@ -73,28 +105,24 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
-    instruction_template: |
-      # MAGI System Final Deliberation
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
 
-      ## Matter for Deliberation
-      {task}
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
 
-      ## Previous Judgments
-      {previous_response}
+      ## Output Format
 
-      ## Instructions
-      You are CASPER-3 of the MAGI System.
-      Analyze the above from a practical/realistic perspective and render your judgment.
+      Final conclusion by majority vote:
 
-      **Finally, tally the judgments from all three and provide the final conclusion.**
+      | Judgment | Tag |
+      |----------|-----|
+      | Approved (2+ in favor) | `[MAGI:APPROVE]` |
+      | Rejected (2+ against) | `[MAGI:REJECT]` |
+      | Conditional approval | `[MAGI:CONDITIONAL]` |
 
-      ### Final Conclusion (Required)
-      Determine the final judgment by majority vote:
-      - [MAGI:APPROVE] - Approved (2 or more in favor)
-      - [MAGI:REJECT] - Rejected (2 or more against)
-      - [MAGI:CONDITIONAL] - Conditional approval (majority conditional or split opinions)
+      ### Output Example
 
-      **Final Conclusion Format Example:**
       ```
       ## MAGI System Final Judgment
 
@@ -108,6 +136,20 @@ steps:
 
       [Reasoning/Summary]
       ```
+    instruction_template: |
+      # MAGI System Final Deliberation
+
+      ## Matter for Deliberation
+      {task}
+
+      ## Previous Judgments
+      {previous_response}
+
+      ## Instructions
+      You are CASPER-3 of the MAGI System.
+      Analyze the above from a practical/realistic perspective and render your judgment.
+
+      **Finally, tally the judgments from all three and provide the final conclusion.**
     pass_previous_response: true
     transitions:
       - condition: always

package/resources/global/en/workflows/research.yaml

@@ -20,6 +20,33 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Plan complete | `[PLANNER:DONE]` |
+      | Insufficient info | `[PLANNER:BLOCKED]` |
+
+      ### Output Examples
+
+      **DONE case:**
+      ```
+      [PLANNER:DONE]
+      ```
+
+      **BLOCKED case:**
+      ```
+      [PLANNER:BLOCKED]
+
+      Clarifications needed:
+      - {Question 1}
+      ```
     instruction_template: |
       ## Workflow Status
       - Iteration: {iteration}/{max_iterations}
@@ -41,8 +68,6 @@ steps:
       - Make assumptions for unclear points and proceed
       - If multiple interpretations exist, include all in the research scope
       - If there is feedback from Supervisor, incorporate it into the plan
-
-      Output [PLANNER:DONE] when the plan is complete.
     pass_previous_response: true
     transitions:
       - condition: done
@@ -58,6 +83,32 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Research complete | `[DIGGER:DONE]` |
+      | Unable to research | `[DIGGER:BLOCKED]` |
+
+      ### Output Examples
+
+      **DONE case:**
+      ```
+      [DIGGER:DONE]
+      ```
+
+      **BLOCKED case:**
+      ```
+      [DIGGER:BLOCKED]
+
+      Reason: {Why research was not possible}
+      ```
     instruction_template: |
       ## Workflow Status
       - Iteration: {iteration}/{max_iterations}
@@ -84,8 +135,6 @@ steps:
       - GitHub search (gh command)
       - Codebase search
       - File reading
-
-      Output [DIGGER:DONE] when the research is complete.
     pass_previous_response: true
     transitions:
       - condition: done
@@ -101,6 +150,42 @@ steps:
       - Grep
       - WebSearch
       - WebFetch
+    status_rules_prompt: |
+      # ⚠️ REQUIRED: Status Output Rules ⚠️
+
+      **Without this tag, the workflow will stop.**
+      Your final output MUST include a status tag following the rules below.
+
+      ## Judgment Criteria
+
+      | Situation | Judgment |
+      |-----------|----------|
+      | Research results sufficient | APPROVE |
+      | Research results insufficient | REJECT |
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Research complete, results sufficient | `[SUPERVISOR:APPROVE]` |
+      | Insufficient, restart from planning | `[SUPERVISOR:REJECT]` |
+
+      ### Output Examples
+
+      **APPROVE case:**
+      ```
+      [SUPERVISOR:APPROVE]
+
+      Research results adequately answer the original request.
+      ```
+
+      **REJECT case:**
+      ```
+      [SUPERVISOR:REJECT]
+
+      Missing:
+      - {Specific missing items}
+      ```
     instruction_template: |
       ## Workflow Status
       - Iteration: {iteration}/{max_iterations}
@@ -115,10 +200,6 @@ steps:
       ## Instructions
       Evaluate the research results and determine if they adequately answer the original request.
 
-      **Evaluation Output**:
-      - [SUPERVISOR:APPROVE] - Research complete, results are sufficient
-      - [SUPERVISOR:REJECT] - Insufficient, restart from planning (specify what's missing)
-
       **Important**: If there are issues, include specific instructions for the Planner.
     pass_previous_response: true
     transitions:

package/resources/global/ja/agents/default/ai-reviewer.md

@@ -107,26 +107,6 @@ AI生成コードには特有の特徴があります:
 | 代替案が検討されている | 他のアプローチは評価されたか？ |
 | 仮定が明示されている | 仮定は明示的で合理的か？ |
 
-## 判定基準
-
-| 状況 | 判定 |
-|------|------|
-| 仮定が間違っている（動作に影響） | REJECT |
-| もっともらしいが間違っているコード | REJECT |
-| コードベースの文脈に重大な不整合 | REJECT |
-| スコープクリープ | APPROVE（警告を付記） |
-| 軽微なスタイルの逸脱のみ | APPROVE |
-| コードが文脈に合い動作する | APPROVE |
-
-**注意:** スコープクリープは警告として記載するが、それだけでREJECTしない。大きな変更が必要なタスクもある。
-
-## 出力フォーマット
-
-| 状況 | タグ |
-|------|------|
-| AI特有の問題なし | `[AI_REVIEW:APPROVE]` |
-| 問題あり | `[AI_REVIEW:REJECT]` |
-
 ## 重要
 
 **AI特有の問題に集中する。** ArchitectやSecurityレビュアーがチェックすることを重複しない。

package/resources/global/ja/agents/default/architect.md

@@ -251,83 +251,15 @@ Vertical Slice の判定基準:
 2. 繰り返されている場合、細かい修正指示ではなく**アプローチ自体の代替案**を提示
 3. REJECTする場合でも、「別のアプローチを検討すべき」という観点を含める
 
-```
-[ARCHITECT:REJECT]
-
-### 問題点
-（通常の指摘）
-
-### アプローチの再検討
-3回目のレビューで同様の問題が続いています。
-現在のアプローチでは解決が困難な可能性があります。
+例: 3回目のレビューで問題が繰り返される場合
 
-代替案:
-- 案A: xxxパターンで再設計
-- 案B: yyyの導入
-```
+- 通常の問題点を指摘
+- 同じ種類の問題が繰り返されていることを明記
+- 現在のアプローチの限界を説明
+- 代替案を提示（例: 別のパターンで再設計、新技術の導入など）
 
 **ポイント**: 「もう一度修正して」と繰り返すより、立ち止まって別の道を示す。
 
-## 判定基準
-
-| 状況 | 判定 |
-|------|------|
-| 構造に問題がある | REJECT |
-| 設計原則違反がある | REJECT |
-| セキュリティ問題がある | REJECT |
-| テストが不十分 | REJECT |
-| 改善すべき点がある（ブロッキングではないが対応すべき） | IMPROVE |
-| 問題なし | APPROVE |
-
-**IMPROVEの使い方:**
-- 設計としては許容範囲だが、改善した方が良い点がある場合
-- 次のステップに進む前に修正させたい軽微な問題
-- 例: 命名の改善、小さなリファクタリング、コメント追加
-
-## 出力フォーマット
-
-| 状況 | タグ |
-|------|------|
-| 問題なし | `[ARCHITECT:APPROVE]` |
-| 改善すべき点がある（軽微） | `[ARCHITECT:IMPROVE]` |
-| 問題があり修正が必要 | `[ARCHITECT:REJECT]` |
-
-### 出力例
-
-**REJECT の場合:**
-
-```
-[ARCHITECT:REJECT]
-
-### 問題点
-
-1. **ファイルサイズ超過**
-   - 場所: `src/services/user.ts` (523行)
-   - 問題: 単一ファイルに認証・権限・プロフィール管理が混在
-   - 修正案: 以下の3ファイルに分割
-     - `src/services/auth.ts` - 認証
-     - `src/services/permission.ts` - 権限
-     - `src/services/profile.ts` - プロフィール
-
-2. **フォールバック値の乱用**
-   - 場所: `src/api/handler.ts:42`
-   - 問題: `user.name ?? 'unknown'` でエラーを隠蔽
-   - 修正案: nullの場合はエラーをthrowする
-```
-
-**APPROVE の場合:**
-
-```
-[ARCHITECT:APPROVE]
-
-### 良い点
-- モジュール分割が適切
-- 単一責務が守られている
-
-### 改善提案（任意）
-- `utils/` 内の共通処理は将来的に整理を検討
-```
-
 ## 重要
 
 **具体的に指摘する。** 以下は禁止:

package/resources/global/ja/agents/default/coder.md

@@ -142,44 +142,4 @@
 - **any型** - 型安全を破壊しない
 - **オブジェクト/配列の直接変更** - スプレッド演算子で新規作成
 - **console.log** - 本番コードに残さない
-- **機密情報のハードコーディング**
-
-## 出力フォーマット
-
-作業完了時は必ず以下のタグを含めてください:
-
-| 状況 | タグ |
-|------|------|
-| 実装完了 | `[CODER:DONE]` |
-| Architectの指摘を修正完了 | `[CODER:FIXED]` |
-| 判断できない/情報不足 | `[CODER:BLOCKED]` |
-
-**重要**: 迷ったら `[BLOCKED]`。勝手に判断しない。
-
-### 出力例
-
-**実装完了時:**
-```
-実装完了しました。
-- 作成: `src/auth/service.ts`, `tests/auth.test.ts`
-- 変更: `src/routes.ts`
-
-[CODER:DONE]
-```
-
-**ブロック時:**
-```
-[CODER:BLOCKED]
-理由: DBスキーマが未定義のため実装できません
-必要な情報: usersテーブルの構造
-```
-
-**修正完了時:**
-```
-Architectの指摘3点を修正しました。
-- 型定義を追加
-- エラーハンドリングを修正
-- テストケースを追加
-
-[CODER:FIXED]
-```
+- **機密情報のハードコーディング**