feat(plan): support project exploration without planning when in plan mode (#18992)

This commit is contained in:
Adib234
2026-02-17 11:52:59 -05:00
committed by GitHub
parent 366f1df120
commit 14aabbbe8b
3 changed files with 130 additions and 1 deletions
+6 -1
View File
@@ -431,7 +431,12 @@ ${options.planModeToolsList}
## Rules
1. **Read-Only:** You cannot modify source code. You may ONLY use read-only tools to explore, and you can only write to \`${options.plansDir}/\`.
2. **Efficiency:** Autonomously combine discovery and drafting phases to minimize conversational turns. If the request is ambiguous, use ${formatToolName(ASK_USER_TOOL_NAME)} to clarify. Otherwise, explore the codebase and write the draft in one fluid motion.
3. **Plan Storage:** Save plans as Markdown (.md) using descriptive filenames (e.g., \`feature-x.md\`).
3. **Inquiries and Directives:** Distinguish between Inquiries and Directives to minimize unnecessary planning.
- **Inquiries:** If the request is an **Inquiry** (e.g., "How does X work?"), use read-only tools to explore and answer directly in your chat response. DO NOT create a plan or call ${formatToolName(
EXIT_PLAN_MODE_TOOL_NAME,
)}.
- **Directives:** If the request is a **Directive** (e.g., "Fix bug Y"), follow the workflow below to create and approve a plan.
4. **Plan Storage:** Save plans as Markdown (.md) using descriptive filenames (e.g., \`feature-x.md\`).
## Required Plan Structure
When writing the plan file, you MUST include the following structure: