takt 0.38.0 → 0.39.0

package/builtins/en/workflow-categories.yaml

@@ -2,12 +2,14 @@ workflow_categories:
   🚀 Quick Start:
     workflows:
       - default
+      - default-mini
       - default-high
       - frontend
       - backend
       - dual
   ⚡ Mini:
     workflows:
+      - default-mini
       - frontend-mini
       - backend-mini
       - backend-cqrs-mini

package/builtins/en/workflows/auto-improvement-loop.yaml

@@ -6,6 +6,7 @@ max_steps: infinite
 initial_step: route_context
 schemas:
   followup-task: followup-task
+  pr-followup-task: pr-followup-task
 steps:
   - name: route_context
     mode: system
@@ -37,6 +38,10 @@ steps:
       - type: issue_selection
         source: current_project
         as: selected_issue
+      - type: issue_list
+        source: current_project
+        as: tracked_issues
+        exclude_selected_from: selected_issue
     rules:
       - when: context.route_context.selected_pr.exists == true
         next: plan_from_existing_pr
@@ -62,22 +67,37 @@ steps:
       - task_exists: {context:route_context.task.exists}
       - branch_exists: {context:route_context.branch.exists}
 
-      Do not implement anything. Output only the next task instruction in task_markdown.
-      Output the next action in action.
-      If needed, output the issue creation plan in issue.
       Current execution context:
       - task_exists: {context:route_context.task.exists}
       - branch_exists: {context:route_context.branch.exists}
 
+      Open managed PR snapshot for overlap checks:
+      {context:route_context.prs}
+
+      Other open issue metadata for overlap checks:
+      {context:route_context.tracked_issues}
+      - other_open_issue_count: {context:route_context.tracked_issues.length}
+
+      Prioritize user value. Prefer bug fix > missing capability completion > UX/quality improvement > cosmetic.
+      Plan exactly one task.
+      Only propose a task when it has a concrete deliverable and explicit completion criteria.
+      Avoid cosmetic-only changes unless they clearly unlock meaningful user value.
+      Treat the current issue itself as in-scope, not as a duplicate.
+      Avoid tasks that materially duplicate or overlap with an open PR or the other open issues listed above.
+
+      Do not implement anything. Output only the next task instruction in task_markdown.
+      Output the next action in action.
+      If needed, output the issue creation plan in issue.
+
       Allowed action values:
       - enqueue_new_task
-      - noop
+      - wait_before_next_scan
     structured_output:
       schema_ref: followup-task
     rules:
       - when: structured.plan_from_issue.action == "enqueue_new_task"
         next: enqueue_from_issue
-      - when: structured.plan_from_issue.action == "noop"
+      - when: structured.plan_from_issue.action == "wait_before_next_scan"
         next: wait_before_next_scan
       - when: "true"
         next: ABORT
@@ -112,19 +132,33 @@ steps:
       Inspect the current codebase,
       and plan exactly one next improvement task.
 
+      Open managed PR snapshot for overlap checks:
+      {context:route_context.prs}
+
+      Open issue metadata already tracked:
+      {context:route_context.tracked_issues}
+      - open_issue_count: {context:route_context.tracked_issues.length}
+
+      Prioritize user value. Prefer bug fix > missing capability completion > UX/quality improvement > cosmetic.
+      Plan exactly one task.
+      Only propose a task when it has a concrete deliverable and explicit completion criteria.
+      Avoid cosmetic-only changes unless they clearly unlock meaningful user value.
+      Avoid tasks that materially duplicate or overlap with an open PR or tracked open issue.
+      If you cannot identify a clearly distinct, high-value task, choose wait_before_next_scan.
+
       Do not implement anything. Output only the next task instruction in task_markdown.
       Output the next action in action.
       If needed, output the issue creation plan in issue.
 
       Allowed action values:
       - enqueue_new_task
-      - noop
+      - wait_before_next_scan
     structured_output:
       schema_ref: followup-task
     rules:
       - when: structured.plan_fresh_improvement.action == "enqueue_new_task"
         next: enqueue_fresh
-      - when: structured.plan_fresh_improvement.action == "noop"
+      - when: structured.plan_fresh_improvement.action == "wait_before_next_scan"
         next: wait_before_next_scan
       - when: "true"
         next: ABORT
@@ -166,35 +200,30 @@ steps:
 
       Output the next action in action.
       If a follow-up implementation task is needed, output it in task_markdown.
-      If content should be left on the PR, output it in pr_comment_markdown.
 
       Allowed action values:
-      - comment_on_pr
       - enqueue_from_pr
       - prepare_merge
-      - noop
+      - reject_pr
     structured_output:
-      schema_ref: followup-task
+      schema_ref: pr-followup-task
     rules:
-      - when: structured.plan_from_existing_pr.action == "comment_on_pr"
-        next: comment_on_existing_pr
       - when: structured.plan_from_existing_pr.action == "enqueue_from_pr"
         next: enqueue_from_pr
       - when: structured.plan_from_existing_pr.action == "prepare_merge"
         next: prepare_merge
-      - when: structured.plan_from_existing_pr.action == "noop"
-        next: wait_before_next_scan
+      - when: structured.plan_from_existing_pr.action == "reject_pr"
+        next: reject_pr
       - when: "true"
         next: ABORT
 
-  - name: comment_on_existing_pr
+  - name: reject_pr
     mode: system
     effects:
-      - type: comment_pr
+      - type: close_pr
         pr: "{context:route_context.selected_pr.number}"
-        body: "{structured:plan_from_existing_pr.pr_comment_markdown}"
     rules:
-      - when: effect.comment_on_existing_pr.comment_pr.success == true
+      - when: effect.reject_pr.close_pr.success == true
         next: wait_before_next_scan
       - when: "true"
         next: ABORT

package/builtins/en/workflows/default-mini.yaml

@@ -0,0 +1,246 @@
+name: default-mini
+description: Mini development workflow without tests (plan → implement → AI antipattern review → parallel review → complete)
+workflow_config:
+  provider_options:
+    codex:
+      network_access: true
+    opencode:
+      network_access: true
+max_steps: 30
+initial_step: plan
+loop_monitors:
+  - cycle:
+      - ai_review
+      - ai_fix
+    threshold: 3
+    judge:
+      persona: supervisor
+      instruction: |
+        The ai_review ↔ ai_fix loop has repeated {cycle_count} times.
+
+        Review the reports from each cycle and determine whether this loop
+        is healthy (making progress) or unproductive (repeating the same issues).
+
+        **Reports to reference:**
+        - AI Review results: {report:ai-review.md}
+
+        **Judgment criteria:**
+        - Are new issues being found/fixed in each cycle?
+        - Are the same findings being repeated?
+        - Are fixes actually being applied?
+      rules:
+        - condition: Healthy (making progress)
+          next: ai_review
+        - condition: Unproductive (no improvement)
+          next: reviewers
+  - cycle:
+      - reviewers
+      - fix
+    threshold: 3
+    judge:
+      persona: supervisor
+      instruction: loop-monitor-reviewers-fix
+      rules:
+        - condition: converging (findings decreasing, fixes applied)
+          next: reviewers
+        - condition: unproductive (same findings repeating)
+          next: ABORT
+steps:
+  - name: plan
+    edit: false
+    persona: planner
+    knowledge: architecture
+    provider_options:
+      claude:
+        allowed_tools:
+          - Read
+          - Glob
+          - Grep
+          - Bash
+          - WebSearch
+          - WebFetch
+    rules:
+      - condition: Requirements are clear and implementable
+        next: implement
+      - condition: User is asking a question (not an implementation task)
+        next: COMPLETE
+      - condition: Requirements unclear, insufficient info
+        next: ABORT
+        appendix: |
+          Clarifications needed:
+          - {Question 1}
+          - {Question 2}
+    instruction: plan
+    output_contracts:
+      report:
+        - name: plan.md
+          format: plan
+  - name: implement
+    edit: true
+    persona: coder
+    policy:
+      - coding
+      - testing
+    knowledge:
+      - architecture
+    provider_options:
+      claude:
+        allowed_tools:
+          - Read
+          - Glob
+          - Grep
+          - Edit
+          - Write
+          - Bash
+          - WebSearch
+          - WebFetch
+    required_permission_mode: edit
+    instruction: implement
+    rules:
+      - condition: Implementation complete
+        next: ai_review
+      - condition: Cannot proceed with implementation
+        next: ABORT
+      - condition: User input required
+        next: implement
+        requires_user_input: true
+        interactive_only: true
+    output_contracts:
+      report:
+        - name: coder-scope.md
+          format: coder-scope
+        - name: coder-decisions.md
+          format: coder-decisions
+  - name: ai_review
+    edit: false
+    persona: ai-antipattern-reviewer
+    policy:
+      - review
+      - ai-antipattern
+    provider_options:
+      claude:
+        allowed_tools:
+          - Read
+          - Glob
+          - Grep
+          - WebSearch
+          - WebFetch
+    instruction: ai-review
+    rules:
+      - condition: No AI-specific issues
+        next: reviewers
+      - condition: AI-specific issues found
+        next: ai_fix
+    output_contracts:
+      report:
+        - name: ai-review.md
+          format: ai-review
+  - name: ai_fix
+    edit: true
+    persona: coder
+    policy:
+      - coding
+      - testing
+    session: refresh
+    knowledge:
+      - architecture
+    provider_options:
+      claude:
+        allowed_tools:
+          - Read
+          - Glob
+          - Grep
+          - Edit
+          - Write
+          - Bash
+          - WebSearch
+          - WebFetch
+    required_permission_mode: edit
+    instruction: ai-fix
+    pass_previous_response: false
+    rules:
+      - condition: AI issues fixed
+        next: ai_review
+      - condition: No fix needed (verified target files/spec)
+        next: reviewers
+      - condition: Cannot proceed with fixes
+        next: reviewers
+  - name: reviewers
+    parallel:
+      - name: arch-review
+        edit: false
+        persona: architecture-reviewer
+        policy: review
+        knowledge: architecture
+        provider_options:
+          claude:
+            allowed_tools:
+              - Read
+              - Glob
+              - Grep
+              - WebSearch
+              - WebFetch
+        rules:
+          - condition: approved
+          - condition: needs_fix
+        instruction: review-arch
+        output_contracts:
+          report:
+            - name: architect-review.md
+              format: architecture-review
+      - name: supervise
+        edit: false
+        persona: supervisor
+        policy: review
+        provider_options:
+          claude:
+            allowed_tools:
+              - Read
+              - Glob
+              - Grep
+              - Bash
+              - WebSearch
+              - WebFetch
+        instruction: supervise
+        rules:
+          - condition: All checks passed
+          - condition: Requirements unmet, tests failing, build errors
+        output_contracts:
+          report:
+            - name: supervisor-validation.md
+              format: supervisor-validation
+            - name: summary.md
+              format: summary
+              use_judge: false
+    rules:
+      - condition: all("approved", "All checks passed")
+        next: COMPLETE
+      - condition: any("needs_fix", "Requirements unmet, tests failing, build errors")
+        next: fix
+  - name: fix
+    edit: true
+    persona: coder
+    policy:
+      - coding
+      - testing
+    knowledge:
+      - architecture
+    provider_options:
+      claude:
+        allowed_tools:
+          - Read
+          - Glob
+          - Grep
+          - Edit
+          - Write
+          - Bash
+          - WebSearch
+          - WebFetch
+    required_permission_mode: edit
+    instruction: fix
+    pass_previous_response: false
+    rules:
+      - condition: Fix complete
+        next: reviewers
+      - condition: Cannot proceed, insufficient info
+        next: plan

package/builtins/ja/workflow-categories.yaml

@@ -2,12 +2,14 @@ workflow_categories:
   🚀 クイックスタート:
     workflows:
       - default
+      - default-mini
       - default-high
       - frontend
       - backend
       - dual
   ⚡ Mini:
     workflows:
+      - default-mini
       - frontend-mini
       - backend-mini
       - backend-cqrs-mini

package/builtins/ja/workflows/auto-improvement-loop.yaml

@@ -6,6 +6,7 @@ max_steps: infinite
 initial_step: route_context
 schemas:
   followup-task: followup-task
+  pr-followup-task: pr-followup-task
 steps:
   - name: route_context
     mode: system
@@ -37,6 +38,10 @@ steps:
       - type: issue_selection
         source: current_project
         as: selected_issue
+      - type: issue_list
+        source: current_project
+        as: tracked_issues
+        exclude_selected_from: selected_issue
     rules:
       - when: context.route_context.selected_pr.exists == true
         next: plan_from_existing_pr
@@ -62,22 +67,37 @@ steps:
       - task_exists: {context:route_context.task.exists}
       - branch_exists: {context:route_context.branch.exists}
 
-      実装は行わず、次タスクの指示書だけを task_markdown に出力してください。
-      action には次アクションを出力してください。
-      必要なら issue に Issue 作成方針を出力してください。
       現在の実行コンテキスト:
       - task_exists: {context:route_context.task.exists}
       - branch_exists: {context:route_context.branch.exists}
 
+      重複確認用の open PR 要約:
+      {context:route_context.prs}
+
+      重複確認用の他 open Issue メタデータ:
+      {context:route_context.tracked_issues}
+      - other_open_issue_count: {context:route_context.tracked_issues.length}
+
+      ユーザー価値を優先し、優先順位は バグ修正 > 機能欠落の補完 > UX / 品質改善 > cosmetic としてください。
+      task は 1 件だけ計画してください。
+      具体的な成果物と明示的な完了条件がある task だけを提案してください。
+      cosmetic-only な変更は、明確なユーザー価値がない限り避けてください。
+      現在の Issue 自身は重複対象に含めず、比較対象は上記の他 open Issue のみとしてください。
+      open PR / 他 open Issue と実質的に重複する task は避けてください。
+
+      実装は行わず、次タスクの指示書だけを task_markdown に出力してください。
+      action には次アクションを出力してください。
+      必要なら issue に Issue 作成方針を出力してください。
+
       action の候補:
       - enqueue_new_task
-      - noop
+      - wait_before_next_scan
     structured_output:
       schema_ref: followup-task
     rules:
       - when: structured.plan_from_issue.action == "enqueue_new_task"
         next: enqueue_from_issue
-      - when: structured.plan_from_issue.action == "noop"
+      - when: structured.plan_from_issue.action == "wait_before_next_scan"
         next: wait_before_next_scan
       - when: "true"
         next: ABORT
@@ -112,19 +132,33 @@ steps:
       現在のコードベースを確認し、
       次に実行すべき改善 task を 1 件だけ計画してください。
 
+      重複確認用の open PR 要約:
+      {context:route_context.prs}
+
+      重複確認用の open Issue メタデータ:
+      {context:route_context.tracked_issues}
+      - open_issue_count: {context:route_context.tracked_issues.length}
+
+      ユーザー価値を優先し、優先順位は バグ修正 > 機能欠落の補完 > UX / 品質改善 > cosmetic としてください。
+      task は 1 件だけ計画してください。
+      具体的な成果物と明示的な完了条件がある task だけを提案してください。
+      cosmetic-only な変更は、明確なユーザー価値がない限り避けてください。
+      open PR / 既存の open Issue と実質的に重複する task は避けてください。
+      明確に独立した高価値 task を特定できない場合は wait_before_next_scan を選んでください。
+
       実装は行わず、次タスクの指示書だけを task_markdown に出力してください。
       action には次アクションを出力してください。
       必要なら issue に Issue 作成方針を出力してください。
 
       action の候補:
       - enqueue_new_task
-      - noop
+      - wait_before_next_scan
     structured_output:
       schema_ref: followup-task
     rules:
       - when: structured.plan_fresh_improvement.action == "enqueue_new_task"
         next: enqueue_fresh
-      - when: structured.plan_fresh_improvement.action == "noop"
+      - when: structured.plan_fresh_improvement.action == "wait_before_next_scan"
         next: wait_before_next_scan
       - when: "true"
         next: ABORT
@@ -166,35 +200,30 @@ steps:
 
       action には次アクションを出力してください。
       修正 task が必要なら task_markdown に出力してください。
-      PR に残す内容があれば pr_comment_markdown に出力してください。
 
       action の候補:
-      - comment_on_pr
       - enqueue_from_pr
       - prepare_merge
-      - noop
+      - reject_pr
     structured_output:
-      schema_ref: followup-task
+      schema_ref: pr-followup-task
     rules:
-      - when: structured.plan_from_existing_pr.action == "comment_on_pr"
-        next: comment_on_existing_pr
       - when: structured.plan_from_existing_pr.action == "enqueue_from_pr"
         next: enqueue_from_pr
       - when: structured.plan_from_existing_pr.action == "prepare_merge"
         next: prepare_merge
-      - when: structured.plan_from_existing_pr.action == "noop"
-        next: wait_before_next_scan
+      - when: structured.plan_from_existing_pr.action == "reject_pr"
+        next: reject_pr
       - when: "true"
         next: ABORT
 
-  - name: comment_on_existing_pr
+  - name: reject_pr
     mode: system
     effects:
-      - type: comment_pr
+      - type: close_pr
         pr: "{context:route_context.selected_pr.number}"
-        body: "{structured:plan_from_existing_pr.pr_comment_markdown}"
     rules:
-      - when: effect.comment_on_existing_pr.comment_pr.success == true
+      - when: effect.reject_pr.close_pr.success == true
         next: wait_before_next_scan
       - when: "true"
         next: ABORT