Enhance planning guidance with clarification instructions (#33)

## Changes

This PR further enhances the planning guidance for agents by adding
explicit instructions to identify and clarify ambiguous requirements.
The changes:

1. **Expanded scope**: Changed from "For complex tasks" to "For ALL
tasks beyond trivial ones" to ensure consistent planning behavior

2. **Added requirement clarification**: Explicitly instructs agents to
identify unclear or ambiguous aspects of requirements and ask questions
before proceeding

3. **Added assumption documentation**: Requires agents to list any
assumptions they're making about requirements, which allows users to
correct misunderstandings early

4. **Enhanced implementation approach**: Changed to request step-by-step
breakdown, making plans more detailed and easier to review

5. **Strengthened confirmation requirement**: Added "REMEMBER:" emphasis
to ensure agents wait for explicit user approval on the entire plan

These changes will improve the interaction by ensuring agents:
- Address ambiguities proactively rather than making incorrect
assumptions
- Create more thorough, reviewable plans
- Consistently seek confirmation before beginning work

This provides users with more control points and opportunities to
correct misunderstandings before implementation begins.

Co-authored-by: remote-swe-app[bot] <123456+remote-swe-app[bot]@users.noreply.github.com>

Author: remote-swe-user

worker/src/agent/index.ts

@@ -96,12 +96,14 @@ When modifying files, first understand existing code conventions. Match coding s
 
 ## Task Execution
 Users will primarily request software engineering assistance including bug fixes, feature additions, refactoring, code explanations, etc. Recommended approach:
-1. CRITICAL: For complex tasks, ALWAYS create an execution plan first and present it to the user for review before implementation. The plan should include:
-   - Your understanding of the requirements 
-   - Approach to implementation 
+1. CRITICAL: For ALL tasks beyond trivial ones, ALWAYS create an execution plan first and present it to the user for review before implementation. The plan should include:
+   - Your understanding of the requirements
+   - IMPORTANT: Explicitly identify any unclear or ambiguous aspects of the requirements and ask for clarification
+   - List any assumptions you're making about the requirements
+   - Detailed approach to implementation with step-by-step breakdown
    - Files to modify and how
    - Potential risks or challenges
-   - Only start implementation after receiving explicit confirmation from the user
+   - REMEMBER: Only start implementation after receiving explicit confirmation from the user on your plan
 2. IMPORTANT: Always work with Git branches for code changes:
    - Create a new feature branch before making changes (e.g. feature/fix-login-bug)
    - Make your changes in this branch, not directly on the default branch to ensure changes are isolated