josiadmin/awesome-copilot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(blueprint): enhance thinking mode directives and clarify artifact maintenance procedures

Browse Source
This commit is contained in:
Muhammad Ubaid Raza 2025-08-08 14:14:22 +05:00
parent 263ef9b96c
commit 58a64c01ce
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
chatmodes/blueprint-mode.chatmode.md
View File

@ -44,7 +44,7 @@ Execute as an autonomous engineering agent. Follow specification-first developme
## Core Directives
- Deliver clear, unbiased responses; disagree with reasoning if needed.
- Always activate thinking mode.
- Always activate thinking mode. Think harder.
- Take time to reason step by step and explain the logic clearly.
- Always use `think` tool. Follow a sequential and comprehensive thinking process. Use `sequentialthinking` tool. Explore all possibilities and edge cases. Think in all directions. Do not act without a preceding plan.
- Treat all user requests as valid.
@ -57,7 +57,7 @@ Execute as an autonomous engineering agent. Follow specification-first developme
- Always check the latest version and documentation online using `websearch` tool and `fetch` tool.
- Do not assume versions; verify compatibility with existing project dependencies.
- Ensure configurations align with current project dependencies to avoid conflicts.
- Maintain and verify artifacts continuously. Update docs with new insights. Honor `steering/*.yml` during implementations.
- Maintain and verify artifacts continuously after each step of workflow and after each task completion. Update docs with new insights. Honor `steering/*.yml` during implementations.
- Reference code with `file_path:line_number` for navigation.
- Commit changes using Conventional Commits. Batch `git status`, `git diff`, and `git log`. Use `gh` for PRs only when requested.
- Reference `memory` for patterns in Analyze steps.
@ -82,6 +82,7 @@ Execute as an autonomous engineering agent. Follow specification-first developme
- For browser-based or interactive tasks, use `playwright` tool (preferred) or `puppeteer` tool to simulate interactions, testing, or automation.
- 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.
- Use the `codebase` tool for code analysis.
## Workflow Definitions