Skip to content

fix: align planner agent tools with §7.1 spec #187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maystudios merged 1 commit into from
Mar 25, 2026
Merged

fix: align planner agent tools with §7.1 spec #187

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 2 additions & 8 deletions templates/agents/planner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,9 @@ description: Creates detailed implementation plans with task breakdowns, wave as
tools:
- Read
- Write
- Edit
- Bash
- Grep
- Glob
- WebSearch
- WebFetch
- TodoRead
- TodoWrite
- AskUserQuestion
model: inherit
permissionMode: plan
skills:
Expand All @@ -34,8 +29,7 @@ You receive phase context and research from the orchestrator, then produce a det

## Constraints

- **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.
Copy link

Copilot AI Mar 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Suggested change
- **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.

Copilot uses AI. Check for mistakes.

## Planning Protocol

Expand Down
Loading