@bugzy-ai/bugzy 1.2.1 → 1.3.0

package/dist/tasks/index.cjs

@@ -520,7 +520,9 @@ Document all findings including:
 \`\`\`
 
 #### 3.2 Launch Test Runner Agent
-Invoke the test-runner agent with special exploration instructions:
+{{INVOKE_TEST_RUNNER}}
+
+Execute the exploration test case with special exploration instructions:
 
 \`\`\`
 Execute the exploration test case at ./test-cases/EXPLORATION-TEMP.md with focus on discovery and documentation.
@@ -973,10 +975,10 @@ Before invoking the agent, identify the test cases for the current area:
 
 #### Step 2.2: Invoke test-code-generator Agent
 
-Use the test-code-generator agent for the current area with the following context:
+{{INVOKE_TEST_CODE_GENERATOR}} for the current area with the following context:
 
 **Agent Invocation:**
-"Use the test-code-generator agent to automate test cases for the [AREA_NAME] area.
+"Automate test cases for the [AREA_NAME] area.
 
 **Context:**
 - Area: [AREA_NAME]
@@ -1116,10 +1118,10 @@ Provide a comprehensive summary showing:
       role: "documentation-researcher",
       contentBlock: `#### 1.4 Gather Product Documentation
 
-Use the documentation-researcher agent to gather comprehensive product documentation:
+{{INVOKE_DOCUMENTATION_RESEARCHER}} to gather comprehensive product documentation:
 
 \`\`\`
-Use the documentation-researcher agent to explore all available product documentation, specifically focusing on:
+Explore all available product documentation, specifically focusing on:
 - UI elements and workflows
 - User interactions and navigation paths
 - Form fields and validation rules
@@ -1133,10 +1135,9 @@ Use the documentation-researcher agent to explore all available product document
       role: "team-communicator",
       contentBlock: `### Step 4.5: Team Communication
 
-Use the team-communicator agent to notify the product team about the new test cases and automated tests:
+{{INVOKE_TEAM_COMMUNICATOR}} to notify the product team about the new test cases and automated tests:
 
 \`\`\`
-Use the team-communicator agent to:
 1. Post an update about test case and automation creation
 2. Provide summary of coverage:
    - Number of manual test cases created
@@ -1394,10 +1395,10 @@ Provide a summary of:
       role: "documentation-researcher",
       contentBlock: `### Step 2: Gather comprehensive project documentation
 
-Use the documentation-researcher agent to explore and gather all available project information and other documentation sources. This ensures the test plan is based on complete and current information.
+{{INVOKE_DOCUMENTATION_RESEARCHER}} to explore and gather all available project information and other documentation sources. This ensures the test plan is based on complete and current information.
 
 \`\`\`
-Use the documentation-researcher agent to explore all available project documentation related to: $ARGUMENTS
+Explore all available project documentation related to: $ARGUMENTS
 
 Specifically gather:
 - Product specifications and requirements
@@ -1422,10 +1423,9 @@ The agent will:
       role: "team-communicator",
       contentBlock: `### Step 7.5: Team Communication
 
-Use the team-communicator agent to notify the product team about the new test plan:
+{{INVOKE_TEAM_COMMUNICATOR}} to notify the product team about the new test plan:
 
 \`\`\`
-Use the team-communicator agent to:
 1. Post an update about the test plan creation
 2. Provide a brief summary of coverage areas and key features
 3. Mention any areas that need exploration or clarification
@@ -1660,7 +1660,7 @@ Classify the ambiguity level to determine appropriate response:
 #### Clarification Approach by Severity
 
 **For CRITICAL/HIGH ambiguity:**
-1. **Use team-communicator to ask specific questions**
+1. **{{INVOKE_TEAM_COMMUNICATOR}} to ask specific questions**
 2. **WAIT for response before proceeding**
 3. **Document the clarification request in event history**
 
@@ -1933,7 +1933,7 @@ ${KNOWLEDGE_BASE_UPDATE_INSTRUCTIONS}`,
       contentBlock: `#### 3.3 Use Documentation Researcher if Needed
 For events mentioning unknown features or components:
 \`\`\`
-Use documentation-researcher agent to find information about: [component/feature]
+{{INVOKE_DOCUMENTATION_RESEARCHER}} to find information about: [component/feature]
 \`\`\``
     },
     {
@@ -1942,7 +1942,7 @@ Use documentation-researcher agent to find information about: [component/feature
 
 When an issue needs to be tracked (task type: report_bug or update_story):
 \`\`\`
-Use issue-tracker agent to:
+{{INVOKE_ISSUE_TRACKER}}
 1. Check for duplicate issues in the tracking system
 2. For bugs: Create detailed bug report with:
    - Clear, descriptive title
@@ -2211,7 +2211,7 @@ For each failed test:
 For each test classified as **[TEST ISSUE]**, use the test-debugger-fixer agent to automatically fix the test:
 
 \`\`\`
-Use the test-debugger-fixer agent to fix test issues:
+{{INVOKE_TEST_DEBUGGER_FIXER}}
 
 For each failed test classified as a test issue (not a product bug), provide:
 - Test run timestamp: [from manifest.timestamp]
@@ -2306,7 +2306,7 @@ After triage in Step 5.1, for tests classified as **[PRODUCT BUG]**, use the iss
 For each bug to report, use the issue-tracker agent:
 
 \`\`\`
-Use issue-tracker agent to:
+{{INVOKE_ISSUE_TRACKER}}
 1. Check for duplicate bugs in the tracking system
    - The agent will automatically search for similar existing issues
    - It maintains memory of recently reported issues
@@ -2377,10 +2377,11 @@ After issue tracker agent completes, create a summary:
       role: "team-communicator",
       contentBlock: `### Step 6: Team Communication
 
-Use the team-communicator agent to notify the product team about test execution:
+{{INVOKE_TEAM_COMMUNICATOR}}
+
+Notify the product team about test execution:
 
 \`\`\`
-Use the team-communicator agent to:
 1. Post test execution summary with key statistics
 2. Highlight critical failures that need immediate attention
 3. Share important learnings about product behavior
@@ -2715,7 +2716,7 @@ Read and analyze the JSON report:
 For each test classified as **[TEST ISSUE]**, use the test-debugger-fixer agent to automatically fix the test:
 
 \`\`\`
-Use the test-debugger-fixer agent to fix test issues:
+{{INVOKE_TEST_DEBUGGER_FIXER}}
 
 For each failed test classified as a test issue (not a product bug), provide:
 - Test file path: [from JSON report]
@@ -2756,7 +2757,7 @@ Classification guidelines:
 #### 4A.4 Fix Test Issues Automatically
 
 For tests classified as [TEST ISSUE]:
-- Use test-debugger-fixer agent to analyze and fix
+- {{INVOKE_TEST_DEBUGGER_FIXER}} to analyze and fix
 - Agent debugs with browser if needed
 - Applies fix (selector update, wait condition, assertion correction)
 - Reruns test to verify fix (10x for flaky tests)
@@ -2772,7 +2773,7 @@ Track fixed tests with:
 {{ISSUE_TRACKER_INSTRUCTIONS}}
 
 For tests classified as [PRODUCT BUG]:
-- Use issue-tracker agent to create bug reports
+- {{INVOKE_ISSUE_TRACKER}} to create bug reports
 - Agent checks for duplicates automatically
 - Creates detailed report with:
   - Title, description, reproduction steps
@@ -3088,10 +3089,10 @@ Format as comprehensive markdown report for terminal display:
 
 {{TEAM_COMMUNICATOR_INSTRUCTIONS}}
 
-Use team-communicator agent to post concise results to Slack thread:
+{{INVOKE_TEAM_COMMUNICATOR}} to post concise results to Slack thread:
 
 \`\`\`
-Use the team-communicator agent to post verification results.
+Post verification results.
 
 **Channel**: [from CHANGE_CONTEXT.slackChannel]
 **Thread**: [from CHANGE_CONTEXT.slackThread]
@@ -3272,10 +3273,10 @@ A successful verification includes:
       role: "documentation-researcher",
       contentBlock: `#### Research Project Documentation
 
-Use the documentation-researcher agent to gather comprehensive context about the changed features:
+{{INVOKE_DOCUMENTATION_RESEARCHER}} to gather comprehensive context about the changed features:
 
 \`\`\`
-Use the documentation-researcher agent to explore project documentation related to the changes.
+Explore project documentation related to the changes.
 
 Specifically gather:
 - Product specifications for affected features
@@ -3307,10 +3308,9 @@ Use this information to:
       role: "issue-tracker",
       contentBlock: `#### Log Product Bugs
 
-For tests classified as **[PRODUCT BUG]**, use the issue-tracker agent to log bugs:
+For tests classified as **[PRODUCT BUG]**, {{INVOKE_ISSUE_TRACKER}} to log bugs:
 
 \`\`\`
-Use issue-tracker agent to:
 1. Check for duplicate bugs in the tracking system
    - The agent will automatically search for similar existing issues
    - It maintains memory of recently reported issues
@@ -3359,10 +3359,9 @@ Use issue-tracker agent to:
       role: "team-communicator",
       contentBlock: `#### Team Communication
 
-Use the team-communicator agent to share verification results (primarily for Slack trigger, but can be used for other triggers):
+{{INVOKE_TEAM_COMMUNICATOR}} to share verification results (primarily for Slack trigger, but can be used for other triggers):
 
 \`\`\`
-Use the team-communicator agent to:
 1. Post verification results summary
 2. Highlight critical failures that need immediate attention
 3. Share bugs logged with issue tracker links