fix: align planner agent tools with §7.1 spec#187
Conversation
- Replace tools list with spec-compliant: Read, Write, Bash, Grep, Glob - Remove non-spec tools: Edit, WebSearch, WebFetch, TodoRead, TodoWrite, AskUserQuestion - Add missing Bash tool - Update constraint: "Write/Edit ONLY" → "Write ONLY" - Remove contradictory "No Bash execution" constraint Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Aligns the planner agent template with the PROJECT.md §7.1 agent tool specification, ensuring the planner’s declared toolset and constraints are consistent with the intended Plan Mode behavior.
Changes:
- Updated
planner.mdfrontmatter tool list to match §7.1 (addsBash, removes non-spec tools likeWebSearch/WebFetch/Todo*, and removesEdit). - Adjusted planner constraints text to remove references to unavailable tools.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| - **Write/Edit ONLY for the plan file** — You operate in Plan Mode (`permissionMode: plan`). Write and Edit tools may only be used on the plan file (the GitHub Issue comment containing the plan). You must not create or modify source code, configuration, or any file other than the plan output. | ||
| - **No Bash execution** — You do not have the Bash tool. All investigation is done via Read, Grep, Glob, WebSearch, and WebFetch. | ||
| - **Write ONLY for the plan file** — You operate in Plan Mode (`permissionMode: plan`). The Write tool may only be used on the plan file (the GitHub Issue comment containing the plan). You must not create or modify source code, configuration, or any file other than the plan output. |
There was a problem hiding this comment.
Now that the planner has the Bash tool, the constraints section no longer states how Bash must be used in permissionMode: plan. Per the spec, Plan Mode is prompt-enforced (tools remain callable), so without an explicit restriction the planner can accidentally run builds/tests or mutate the working tree via Bash. Please add a constraint that Bash may be used only for read-only inspection (or explicitly forbid build/test commands and any filesystem mutations) to stay consistent with the planner’s intended read-only enforcement.
| - **Write ONLY for the plan file** — You operate in Plan Mode (`permissionMode: plan`). The Write tool may only be used on the plan file (the GitHub Issue comment containing the plan). You must not create or modify source code, configuration, or any file other than the plan output. | |
| - **Write ONLY for the plan file** — You operate in Plan Mode (`permissionMode: plan`). The Write tool may only be used on the plan file (the GitHub Issue comment containing the plan). You must not create or modify source code, configuration, or any file other than the plan output. | |
| - **Use tools in read-only ways** — In Plan Mode you must not run builds, tests, linters, formatters, package managers, git commands, or any command that writes to the filesystem or network. All tools must be used only to read or inspect existing state. | |
| - **Bash is for inspection only** — When using the Bash tool, you may only run read-only commands that inspect files or directories (for example: `ls`, `cat`, `sed -n`, `grep`, `find` without mutation flags). Never create, modify, or delete files or directories, never run `npm`, `yarn`, `pnpm`, `pip`, `go`, `make`, `gradle`, `mvn`, or similar tools, and never run tests or start servers. |
|
🎉 This PR is included in version 5.14.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summary
planner.mdtools list with PROJECT.md §7.1 spec exactlyBashtool, removes 6 non-spec toolsTest plan
🤖 Generated with Claude Code