takt 0.1.2 → 0.1.4

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

@@ -18,6 +18,41 @@ 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.
+
+      ## Judgment Criteria
+
+      | Situation | Judgment |
+      |-----------|----------|
+      | Requirements clear and implementable | DONE |
+      | Requirements unclear, insufficient info | BLOCKED |
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Analysis complete | `[PLANNER:DONE]` |
+      | Insufficient info | `[PLANNER:BLOCKED]` |
+
+      ### Output Examples
+
+      **DONE case:**
+      ```
+      [PLANNER:DONE]
+      ```
+
+      **BLOCKED case:**
+      ```
+      [PLANNER:BLOCKED]
+
+      Clarifications needed:
+      - {Question 1}
+      - {Question 2}
+      ```
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -67,9 +102,6 @@ steps:
       ## Clarifications Needed (if any)
       - {Unclear points or items requiring confirmation}
       ```
-
-      Output [PLANNER:DONE] when complete.
-      Output [PLANNER:BLOCKED] if requirements are unclear.
     pass_previous_response: true
     transitions:
       - condition: done
@@ -88,6 +120,39 @@ 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 decide/insufficient info | `[CODER:BLOCKED]` |
+
+      **Important**: When in doubt, `[BLOCKED]`. Don't decide on your own.
+
+      ### Output Examples
+
+      **DONE case:**
+      ```
+      Implementation complete.
+      - Created: `src/auth/service.ts`, `tests/auth.test.ts`
+      - Modified: `src/routes.ts`
+
+      [CODER:DONE]
+      ```
+
+      **BLOCKED case:**
+      ```
+      [CODER:BLOCKED]
+
+      Reason: DB schema is undefined, cannot implement
+      Required info: users table structure
+      ```
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -140,9 +205,6 @@ steps:
       - **Options Considered**: {List of options}
       - **Reason**: {Why this option was chosen}
       ```
-
-      Include [CODER:DONE] when complete.
-      Include [CODER:BLOCKED] if you cannot proceed (returns to plan).
     transitions:
       - condition: done
         next_step: review
@@ -157,6 +219,64 @@ 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 |
+      |-----------|----------|
+      | Structural issues | REJECT |
+      | Design principle violations | REJECT |
+      | Security issues | REJECT |
+      | Insufficient tests | REJECT |
+      | Minor improvements needed | IMPROVE |
+      | No issues | APPROVE |
+
+      **How to use IMPROVE:**
+      - Design is acceptable but there are points that could be better
+      - Examples: naming improvements, small refactoring, adding comments
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | No issues | `[ARCHITECT:APPROVE]` |
+      | Minor improvements needed | `[ARCHITECT:IMPROVE]` |
+      | Structural changes required | `[ARCHITECT:REJECT]` |
+
+      ### Output Examples
+
+      **APPROVE case:**
+      ```
+      [ARCHITECT:APPROVE]
+
+      Positive points:
+      - Appropriate module organization
+      - Single responsibility maintained
+      ```
+
+      **IMPROVE case:**
+      ```
+      [ARCHITECT:IMPROVE]
+
+      Improvements:
+      - Improve naming: `data` → `userData`
+      - Add comments
+      ```
+
+      **REJECT case:**
+      ```
+      [ARCHITECT:REJECT]
+
+      Issues:
+      1. File size exceeded
+         - Location: `src/services/user.ts` (523 lines)
+         - Fix: Split into 3 files
+      ```
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -175,10 +295,7 @@ steps:
       ## Instructions
       Focus on **architecture and design** review. Do NOT review AI-specific issues (that's the next step).
 
-      Review the changes and provide feedback:
-      - [ARCHITECT:APPROVE] if no issues
-      - [ARCHITECT:IMPROVE] if minor improvements needed
-      - [ARCHITECT:REJECT] if structural changes are needed (list specific issues)
+      Review the changes and provide feedback.
 
       **Report output:** Output to the `Report File` specified above.
       - If file does not exist: Create new file
@@ -230,6 +347,39 @@ 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 |
+      |-----------|-----|
+      | Improvements complete | `[CODER:DONE]` |
+      | Cannot decide/insufficient info | `[CODER:BLOCKED]` |
+
+      **Important**: When in doubt, `[BLOCKED]`. Don't decide on your own.
+
+      ### Output Examples
+
+      **DONE case:**
+      ```
+      Improvements complete.
+      - Improved naming: `data` → `userData`
+      - Added comments
+
+      [CODER:DONE]
+      ```
+
+      **BLOCKED case:**
+      ```
+      [CODER:BLOCKED]
+
+      Reason: Improvement intent unclear
+      Required info: Specific improvement details
+      ```
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -254,8 +404,6 @@ steps:
       - Adding/fixing comments
       - Code organization
 
-      Include [CODER:DONE] when complete.
-      Include [CODER:BLOCKED] if you cannot proceed.
     pass_previous_response: true
     transitions:
       - condition: done
@@ -271,6 +419,48 @@ 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 |
+      |-----------|----------|
+      | Incorrect assumptions (affecting behavior) | REJECT |
+      | Plausible-but-wrong code | REJECT |
+      | Significant context mismatch with codebase | REJECT |
+      | Scope creep | APPROVE (with warning noted) |
+      | Minor style deviations only | APPROVE |
+      | Code fits context and works | APPROVE |
+
+      **Note:** Scope creep is noted as a warning but doesn't warrant REJECT alone.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | No AI-specific issues | `[AI_REVIEW:APPROVE]` |
+      | Issues found | `[AI_REVIEW:REJECT]` |
+
+      ### Output Examples
+
+      **APPROVE case:**
+      ```
+      [AI_REVIEW:APPROVE]
+
+      Verification result: No issues
+      ```
+
+      **REJECT case:**
+      ```
+      [AI_REVIEW:REJECT]
+
+      Issues:
+      1. Non-existent API used: `fetch.json()` → `response.json()`
+      ```
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -293,10 +483,6 @@ steps:
       - Context fit with existing codebase
       - Scope creep detection
 
-      Include:
-      - [AI_REVIEW:APPROVE] if no AI-specific issues found
-      - [AI_REVIEW:REJECT] if issues detected (list specific problems)
-
       **Report output:** Output to the `Report File` specified above.
       - If file does not exist: Create new file
       - If file exists: Append with `## Iteration {iteration}` section
@@ -344,6 +530,38 @@ 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 |
+      |-----------|-----|
+      | AI issue fixes complete | `[CODER:DONE]` |
+      | Cannot decide/insufficient info | `[CODER:BLOCKED]` |
+
+      **Important**: When in doubt, `[BLOCKED]`. Don't decide on your own.
+
+      ### Output Examples
+
+      **DONE case:**
+      ```
+      Fixed AI Reviewer's issues.
+      - Fixed non-existent API: `fetch.json()` → `response.json()`
+
+      [CODER:DONE]
+      ```
+
+      **BLOCKED case:**
+      ```
+      [CODER:BLOCKED]
+
+      Reason: Fix method unclear
+      Required info: Alternative API specification
+      ```
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -366,8 +584,6 @@ steps:
       - Aligning with existing codebase patterns
       - Removing scope creep
 
-      Include [CODER:DONE] when complete.
-      Include [CODER:BLOCKED] if you cannot proceed.
     pass_previous_response: true
     transitions:
       - condition: done
@@ -383,6 +599,45 @@ 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 |
+      |-----------|----------|
+      | Critical vulnerability | REJECT |
+      | Medium severity vulnerability | REJECT |
+      | Minor issues/warnings only | APPROVE (note warnings) |
+      | No security issues | APPROVE |
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | No security issues | `[SECURITY:APPROVE]` |
+      | Vulnerabilities require fixes | `[SECURITY:REJECT]` |
+
+      ### Output Examples
+
+      **APPROVE case:**
+      ```
+      [SECURITY:APPROVE]
+
+      No security issues detected.
+      ```
+
+      **REJECT case:**
+      ```
+      [SECURITY:REJECT]
+
+      Vulnerabilities:
+      1. SQL Injection: `src/db.ts:42`
+         Fix: Use parameterized query
+      ```
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -405,10 +660,6 @@ steps:
       - Data exposure risks
       - Cryptographic weaknesses
 
-      Include:
-      - [SECURITY:APPROVE] if no security issues found
-      - [SECURITY:REJECT] if vulnerabilities detected (list specific issues)
-
       **Report output:** Output to the `Report File` specified above.
       - If file does not exist: Create new file
       - If file exists: Append with `## Iteration {iteration}` section
@@ -459,6 +710,38 @@ 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 |
+      |-----------|-----|
+      | Security fixes complete | `[CODER:DONE]` |
+      | Cannot decide/insufficient info | `[CODER:BLOCKED]` |
+
+      **Important**: Security issues require highest priority.
+
+      ### Output Examples
+
+      **DONE case:**
+      ```
+      Fixed security issues.
+      - SQL injection fix: Changed to parameterized query
+
+      [CODER:DONE]
+      ```
+
+      **BLOCKED case:**
+      ```
+      [CODER:BLOCKED]
+
+      Reason: Fix method unclear
+      Required info: Auth library specification
+      ```
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -477,8 +760,6 @@ steps:
       **Important**: Fix the vulnerabilities identified in the security review.
       Security issues require highest priority.
 
-      Include [CODER:DONE] when complete.
-      Include [CODER:BLOCKED] if you cannot proceed.
     pass_previous_response: true
     transitions:
       - condition: done
@@ -497,6 +778,39 @@ 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 |
+      |-----------|-----|
+      | Architect's issues fixed | `[CODER:DONE]` |
+      | Cannot decide/insufficient info | `[CODER:BLOCKED]` |
+
+      **Important**: When in doubt, `[BLOCKED]`. Don't decide on your own.
+
+      ### Output Examples
+
+      **DONE case:**
+      ```
+      Fixed Architect's issues.
+      - File split: Split into 3 files
+      - Added type definitions
+
+      [CODER:DONE]
+      ```
+
+      **BLOCKED case:**
+      ```
+      [CODER:BLOCKED]
+
+      Reason: Fix approach unclear
+      Required info: Specific split method
+      ```
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -516,8 +830,6 @@ steps:
       The "Original User Request" is reference information, not the latest instruction.
       Review the session conversation history and fix the issues raised by the Architect.
 
-      Include [CODER:DONE] when complete.
-      Include [CODER:BLOCKED] if you cannot proceed.
     pass_previous_response: true
     transitions:
       - condition: done
@@ -534,6 +846,51 @@ 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.
+
+      ## Judgment Criteria
+
+      | Situation | Judgment |
+      |-----------|----------|
+      | Requirements not met | REJECT |
+      | Tests failing | REJECT |
+      | Build fails | REJECT |
+      | Workarounds remaining | REJECT |
+      | All OK | APPROVE |
+
+      **Principle**: When in doubt, REJECT. Don't give ambiguous approval.
+
+      ## Output Format
+
+      | Situation | Tag |
+      |-----------|-----|
+      | Final approval | `[SUPERVISOR:APPROVE]` |
+      | Return for fixes | `[SUPERVISOR:REJECT]` |
+
+      ### Output Examples
+
+      **APPROVE case:**
+      ```
+      [SUPERVISOR:APPROVE]
+
+      Verification results:
+      - Tests: ✅ All passed
+      - Build: ✅ Succeeded
+      - Requirements met: ✅
+      ```
+
+      **REJECT case:**
+      ```
+      [SUPERVISOR:REJECT]
+
+      Issues:
+      1. Tests failing: `npm test` - 2 failures
+      2. Requirements not met: Login feature not implemented
+      ```
     instruction_template: |
       ## Workflow Context
       - Iteration: {iteration}/{max_iterations}
@@ -619,10 +976,6 @@ steps:
       npm run build
       ```
       ```
-
-      Output:
-      - [SUPERVISOR:APPROVE] if ready to merge
-      - [SUPERVISOR:REJECT] if issues found (specify the issues)
     transitions:
       - condition: approved
         next_step: COMPLETE