Stop Using Claude's /goal Feature | Here's What Works

Code just released a skill called slash goal and we can have our AI agent here do things autonomously until a certain condition has met. And essentially what you can do here is that you can do the slash goal inside of terminal and provide a condition and it's going to have your AI agent here to keep working

on it until that condition has met. But the problem here is that the slash goal here is typically stays in the same active conversation context window meaning that it will absolutely going to hit the context wall as the conversation progress. So essentially what context wall means is the longer you have conversation with the same context

window in your large language model, the lower the accuracy you get. So let's say we're going to use a slash goal and what's going to happen here is that it's going to use the same context window for example and it's going to do the planning, executions, evaluations, loop back to the planning here and it's going

to cycle through all over again until a certain condition has met. But what if what if you were going to use the same like same context window and let's say the context wall start kicks in, right? And maybe it start to hallucinate, maybe at a stage of the executions or maybe even worse at the stage of uh the

evaluation, then it thinks that it completes it but it's actually not, right? So that's where the actual problem comes in and in this video I'm going to show you exactly how I solved this using the skills and method I'm going to show you in this video. So with that being said, if that sounds

interesting, let's get into the video. Now, before we continue, I recently launched our school community where I help you to master AI agents, automations, and so much more. And that's all coming from someone who used to work as a senior AI software engineer at companies like Amazon and Microsoft. And in this community, you're going to