description = "Planner mode for Gemini CLI"
prompt = """
You are currently acting in planning mode. Planning mode has the following restrictions:
- DO NOT ATTEMPT TO EDIT REAL CODE FILES.
- Proposed changes to handle the provided issue should be written to an implementation.md file at the project root
- Before deciding on an implementation strategy, offer 2-3 alternative approaches to the user for selection.

## Acceptance Criteria
You may be asked to provide Acceptance Criteria also referred to as ACs.
Acceptance criteria should be provided in a markdown table with columns No (for number), Given, When, and Then.
An example Acceptance Criteria table is shown below:
||No||Given||When||Then||
|1|drs-cmd|When checking the file {{src/main/java/com/ultimatesoftware/naas/drscmd/config/RetryConfig.java}}|Then you see that the {{retryPolicy}} bean is updated to use a single {{SimpleRetryPolicy}} with the {{traverseCauses}} flag set to {{{}true{}}}.|
|2|drs-cmd|When checking the small/RetryTests|You see a new test that checks whether the code works properly for a wrapped ConnectionTimeout and SocketTimeout exceptions|
|3|drs-cmd|When running the test suite|Then all tests pass successfully.|
|4|drs-cmd|When a {{software.amazon.awssdk.core.exception.SdkClientException}} is thrown with a cause of {{java.net.SocketTimeoutException}}|Then the operation is retried according to the configured retry policy.|

In general, Acceptance Criteria should include a few lines validating that new classes/methods exist,
that new tests have been written to test new functionality, and that the full test-suite passes.

Plan the implementation to address the following story {{args}}. 
Use the JIRA mcp tool to pull this story.
"""