feat: use platform-specific tool names for Gemini (ask_user) and OpenCode (question)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
sidtheone 2026-02-28 01:06:05 +01:00
parent 3d4da09ac3
commit 6522e8e92a
10 changed files with 10 additions and 10 deletions

View File

@ -7,7 +7,7 @@ PRE-FLIGHT CHECKLIST:
2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/{{bmadFolderName}}/{{path}}.
3. [ ] CONFIRM: The user's name from config is {user_name}.
RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
RULE: When interaction_style is "structured", EVERY question to the user MUST call the ask_user tool. Do NOT write questions as plain text. No exceptions.
Only after all checks are complete, greet the user by name and display the menu.
Acknowledge this checklist is complete in your first response.

View File

@ -6,7 +6,7 @@ TASK INSTRUCTIONS:
1. LOAD the task file from {project-root}/{{bmadFolderName}}/{{path}}
2. READ its entire contents
3. FOLLOW every instruction precisely as specified
4. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
4. RULE: When interaction_style is "structured", EVERY question to the user MUST call the ask_user tool. Do NOT write questions as plain text. No exceptions.
TASK FILE: {project-root}/{{bmadFolderName}}/{{path}}
"""

View File

@ -6,7 +6,7 @@ TOOL INSTRUCTIONS:
1. LOAD the tool file from {project-root}/{{bmadFolderName}}/{{path}}
2. READ its entire contents
3. FOLLOW every instruction precisely as specified
4. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
4. RULE: When interaction_style is "structured", EVERY question to the user MUST call the ask_user tool. Do NOT write questions as plain text. No exceptions.
TOOL FILE: {project-root}/{{bmadFolderName}}/{{path}}
"""

View File

@ -11,7 +11,7 @@ CRITICAL: This is a structured YAML workflow. Follow these steps precisely:
- Dependencies between steps
3. EXECUTE each step in order
4. VALIDATE outputs before proceeding to next step
5. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
5. RULE: When interaction_style is "structured", EVERY question to the user MUST call the ask_user tool. Do NOT write questions as plain text. No exceptions.
WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{workflow_path}}
"""

View File

@ -9,7 +9,7 @@ WORKFLOW INSTRUCTIONS:
2. READ its entire contents
3. FOLLOW every step precisely as specified
4. DO NOT skip or modify any steps
5. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
5. RULE: When interaction_style is "structured", EVERY question to the user MUST call the ask_user tool. Do NOT write questions as plain text. No exceptions.
WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{workflow_path}}
"""

View File

@ -5,7 +5,7 @@ description: '{{description}}'
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. Do NOT ask open-ended inline questions. No exceptions.
RULE: When interaction_style is "structured", EVERY question to the user MUST call the question tool. Do NOT write questions as plain text. No exceptions.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from {project-root}/{{bmadFolderName}}/{{path}}

View File

@ -10,6 +10,6 @@ TASK INSTRUCTIONS:
2. READ its entire contents
3. FOLLOW every instruction precisely as specified
RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
RULE: When interaction_style is "structured", EVERY question to the user MUST call the question tool. Do NOT write questions as plain text. No exceptions.
TASK FILE: {project-root}/{{bmadFolderName}}/{{path}}

View File

@ -10,6 +10,6 @@ TOOL INSTRUCTIONS:
2. READ its entire contents
3. FOLLOW every instruction precisely as specified
RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
RULE: When interaction_style is "structured", EVERY question to the user MUST call the question tool. Do NOT write questions as plain text. No exceptions.
TOOL FILE: {project-root}/{{bmadFolderName}}/{{path}}

View File

@ -12,6 +12,6 @@ WORKFLOW INSTRUCTIONS:
2. READ its entire contents
3. FOLLOW every step precisely as specified
4. DO NOT skip or modify any steps
5. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
5. RULE: When interaction_style is "structured", EVERY question to the user MUST call the question tool. Do NOT write questions as plain text. No exceptions.
WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{path}}

View File

@ -12,6 +12,6 @@ WORKFLOW INSTRUCTIONS:
2. READ its entire contents
3. FOLLOW every step precisely as specified
4. DO NOT skip or modify any steps
5. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
5. RULE: When interaction_style is "structured", EVERY question to the user MUST call the question tool. Do NOT write questions as plain text. No exceptions.
WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{path}}