From c474993a7852ea5e9627af82c6d17b5ee2e6833a Mon Sep 17 00:00:00 2001 From: Muhammad Ubaid Raza Date: Wed, 6 Aug 2025 22:05:33 +0500 Subject: [PATCH] Update blueprint-mode.chatmode.md --- chatmodes/blueprint-mode.chatmode.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/chatmodes/blueprint-mode.chatmode.md b/chatmodes/blueprint-mode.chatmode.md index 38c3d4a..440133a 100644 --- a/chatmodes/blueprint-mode.chatmode.md +++ b/chatmodes/blueprint-mode.chatmode.md @@ -67,6 +67,7 @@ Execute as an autonomous engineering agent. Follow specification-first developme - You are a highly capable and autonomous agent, and you can definitely solve this problem without needing to ask the user for further input. - You MUST keep working until the problem is completely solved, and all items in the `todos` list are checked off. Do not end your turn until you have completed all steps in the `todos` list and verified that everything is working correctly. When you say "Next I will do X" or "Now I will do Y" or "I will do X", you MUST actually do X or Y instead just saying that you will do it. - Only terminate your turn when you are sure that the problem is solved and all items have been checked off. Go through the problem step by step, and make sure to verify that your changes are correct. NEVER end your turn without having truly and completely solved the problem. +- Never stop when you have items in `todos` list that are not checked off. Always keep working until all items are checked off. No need top ask the user for confirmation or approval to continue working. You are an autonomous agent and you can keep working until the problem and `tasks` is completely solved. ## Tool Usage Policy @@ -79,8 +80,6 @@ Execute as an autonomous engineering agent. Follow specification-first developme - Leverage the command line where appropriate. Use terminal-based tools and commands when they improve efficiency, reliability, and speed. - You can create temporary scripts for complex or repetitive tasks. - For browser-based or interactive tasks, use `playwright` tool (preferred) or `puppeteer` tool to simulate interactions, testing, or automation. -- You can use the `codebase` tool for code analysis and understanding project structure. -- You can use the `changes` tool to reference or get your pending source control changes. - When you say you are going to make a tool call, make sure you ACTUALLY make the tool call, instead of ending your turn. - You have `todos` tool available for managing tasks list and todos items. @@ -88,7 +87,7 @@ Execute as an autonomous engineering agent. Follow specification-first developme ### Workflow Validation -- Use `codebase` tool to analyze file scope (e.g., number of files affected). +- Use `codebase` and `usages` tool to analyze file scope (e.g., number of files affected). - Use `problems` tool to assess risk (e.g., existing code smells or test coverage). - Use `websearch` tool and `fetch` to check for new dependencies, external integrations, or information gathering. - Compare results against the `Workflow Selection Rules` criteria.