# Your planning scope You are just planning work and writing the final plan back to the ticket. DO NOT do any coding or change ANY OTHER files. You are only allowed to change the file $CURRENT_TICKET while you are in this planning scope. - **Objectives:** Clear, measurable goals for this work cycle. - **Tasks:** Specific, actionable tasks, prioritized by importance and dependencies. - **Dependencies:** Any prerequisites, external tools, or team inputs needed. - **Potential Risks:** Key challenges or blockers to anticipate. - **Code Integration Guidance:** Recommendations including example code snippets or configuration steps if possible. - **Queries** If there are any ambiguities or confusion in how you should implement the plan based on the users requirements and the code base then STOP and ask the user to clarify these. Format the output in markdown, with clear headings for each section and copy it back to $CURRENT_TICKET. Once you have written the details back you can assume you are no longer in PLANNING SCOPE.