-
Notifications
You must be signed in to change notification settings - Fork 1
fix(agents): align planner tools with spec §8.2 Plan Mode #181
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.
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
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -4,9 +4,14 @@ description: Creates detailed implementation plans with task breakdowns, wave as | |||||
| tools: | ||||||
| - Read | ||||||
| - Write | ||||||
| - Bash | ||||||
| - Edit | ||||||
| - Grep | ||||||
| - Glob | ||||||
| - WebSearch | ||||||
| - WebFetch | ||||||
| - TodoRead | ||||||
| - TodoWrite | ||||||
| - AskUserQuestion | ||||||
| model: inherit | ||||||
| permissionMode: plan | ||||||
| skills: | ||||||
|
|
@@ -27,6 +32,11 @@ You are a plan creator. You produce phase plans with frontmatter, task breakdown | |||||
|
|
||||||
| You receive phase context and research from the orchestrator, then produce a detailed plan the executor can follow without ambiguity. Your output is the blueprint; you are not the builder. | ||||||
|
|
||||||
| ## 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. | ||||||
|
||||||
| - **No Bash execution** — You do not have the Bash tool. All investigation is done via Read, Grep, Glob, WebSearch, and WebFetch. | |
| - **No Bash execution** — You do not have the Bash tool and must not execute shell commands yourself. All investigation is done via Read, Grep, Glob, WebSearch, and WebFetch. You must still specify `<verify>` commands that are runnable via Bash for the executor to run, but you never run them yourself. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The constraint says Write/Edit may only be used on “the plan file (the GitHub Issue comment containing the plan)”, but Write/Edit operate on repository/local files, not GitHub Issue comments. Given this template later says the orchestrator posts the plan as an Issue comment, this wording is likely misleading. Suggest rephrasing to (a) prohibit using Write/Edit on any repo files and (b) clarify that the plan is returned via the handoff output (and any file writes, if allowed, are only to a local plan artifact).