HOW I USE CLAUDE CODE TO BUILD AUTONOMOUSLY

Hey Jarvis, what are we working on? We're building Jarvis together using Claude Code and the Festival methodology, developing the whole system in one pass so you can ship faster and iterate based on real user feedback. So yeah, I wanted to make a video about just a really tangible example of how I'm using Claude Code in a way that's like much more advanced. And so I'm using this thing called Festival. It's free to install and it basically teaches Claude how to actually like organize a complex project and then save its context so it can actually do that efficiently. Because like technically Claude already plans stuff out, but it's going to finish no matter what, and so like it can skip features, it doesn't know how to iterate, it doesn't have feedback loops to like actually test and get user feedback. It doesn't have all that built in. So Festival gives Claude like superpowers for that. So just for an example, I'm turning my version of Jarvis into a web-based version, which is what I was just talking to. And so this is like what that looks like in practice. So, went into Claude and was like, okay, here's all these features that we need to like finish up and like work on with Jarvis. And so let's do this as a festival. So it prepares all this stuff and it basically gets ready to say, hey, like the user is going to dump as much information about all this like how this should work, every feature, everything that should be included. So that's my huge prompt about that. And then when Claude knows how to do then is to create these spec documents that look like this. And so it's just markdown, but it brings you through like, okay, this is like all the requirements for everything. So we literally are covering every single feature of Jarvis and then everything all in one. And like every part of it, right? So it's this long document. So what you do is you just review and you go through. And so as I'm reviewing, I'm going, okay, I don't think we're covering this, I don't think we're covering that. What's the measurement indicator for like that piece? Like how are you going to know that it works right? So that's what I'm doing now. And then once I go back from here, it'll actually plan out this really long plan for how it can build. So I'll come back to that here in a sec. Okay, so this is what the festival looks like after it came back. So I went through the requirement documents, went back and forth a few times with it, because there was a few things that seemed like we were still missing and things I had to clarify. Then locked in that plan, and then Claude knew to actually create the whole festival. So this is where it's going to build the entire product, like everything about the product on one pass. And then I launch that off, and then it kind of runs in the background, so I can keep, you know, talking to Claude and working on other things in the same project. Like maybe I'm working on like the website while it's actually building the product or whatever. Um, but so this is what the actual festival looks like. So you can see, um, it's in process right now, it's 8% done. There's 318 total tasks. Um, and then if we like kind of expand where it's at in real time, we can see that it's got like all these phases. Um, and then these are all the phases what it's actually building. So each phase has a bunch of sections, and then each section has a bunch of tasks, um, and it works through, you know, one by one. And the important thing is that it goes through testing, review, and then iteration, and it'll loop through that as much as it needs before it can actually commit to that that section being done. The same thing happens at the phase level and the task level. Um, so yeah, this is how it's going to actually go and work through all of this. Um, and we can see if it made progress. So no, it's still at 8%. Um, but you can see it did get through that, uh, task, it looks like. So earlier it was on that task, and now it's on the next task. Um, but yeah, you can just spin all of your time in planning, have this festival running, and then now I spend another 30 minutes planning another one. And then now that product's being built, and then I go to another one, another one. And then when this one's ready, maybe it takes a few hours, come back to it. Okay, is it right? It should be, should be at least 90% if not 100%. You obviously need to actually user test. Um, but you could create a feedback loop, you know, and do a festival with a feedback loop, too. Like if it's a voice product, you know, actually talk to it and then explain everything you're seeing that's wrong, and then feed that to the feedback loop, pour all those iterations into a festival, and then again, you can just let Claude work in the background over a long periods of time, um, using Festival.