-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Add blog post: Does Your AI Agent Need a Plan? #6209
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
Conversation
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.
Pull request overview
This PR adds a new blog post titled "Does Your AI Agent Need a Plan?" that explores three distinct planning philosophies for working with goose: The Architect (using /plan mode), The Director (using instruction files), and The Explorer (using conversational context building with todo extension and goosehints).
Key Points
- Presents planning as a spectrum rather than a binary choice
- Provides practical examples from real migration projects
- Links to relevant documentation for each approach
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| documentation/blog/2025-12-19-does-your-ai-agent-need-a-plan/index.md | New blog post content with frontmatter, three planning strategy sections, and meta tags for social sharing |
| documentation/blog/2025-12-19-does-your-ai-agent-need-a-plan/blog-banner.png | Blog post banner image (binary PNG file) |
documentation/blog/2025-12-19-does-your-ai-agent-need-a-plan/index.md
Outdated
Show resolved
Hide resolved
documentation/blog/2025-12-19-does-your-ai-agent-need-a-plan/index.md
Outdated
Show resolved
Hide resolved
|
* main: (155 commits) remove Tool Selection Strategy preview (#6250) fix(cli): correct bash syntax in terminal integration functions (#6181) fix : opening a session to view it modifies session history order in desktop (#6156) test: fix recipe and audio tests to avoid side effects (#6231) chore: Update gemini versions in test_providers.sh (#6246) feat: option to stream json - jsonl really (#6228) feat: add mcp app renderer (#6095) docs: update skills extension to support .agents/skills directories (#6199) Add YouTube short to Chrome DevTools MCP tutorial (#6244) docs: Caveats for privacy information in logs documentation (#6218) move goose issue solver to opus (#6233) feat: improved UX for tool calls via execute_code (#6205) Blog: Code Mode Doesn't Replace MCP (#6227) fix: prevent keychain requests during cargo test (#6219) test: fix test_max_turns_limit slow execution and wrong message type (#6221) Skills vs MCP blog (#6220) Add blog post: Does Your AI Agent Need a Plan? (#6209) fix(ui): enable MCP UI to send a prompt message when an element is clicked (#6207) docs: param option for recipe deeplink/open (#6206) docs: edit in place or fork session (#6203) ...
Summary
Adds a new blog post exploring different planning approaches with goose.
Content
This post discusses three planning philosophies for AI agents:
/planmode for interactive dialogue and comprehensive planningFiles Added
documentation/blog/2025-12-19-does-your-ai-agent-need-a-plan/index.mddocumentation/blog/2025-12-19-does-your-ai-agent-need-a-plan/blog-banner.png