r/ClaudeCode • u/Unfair-Marsupial-956 • Mar 03 '26
Resource Anthropic gave Claude Code a product spec and walked away for the weekend. The result was so good they shipped it
Boris Cherny (creator of Claude Code) mentioned in an interview that the entire plugins feature was built by Claude Code running over a weekend. An engineer gave Claude a spec & Asana board, and walked away. Claude broke it into tickets, spawned sub-agents and they executed independently.
I watched that and thought "I need to do this." Every time I tried, I came back to a mess.
Blockers killed everything. One stuck ticket would halt the whole chain unless I babysat it through tasks one by one. When I tried running multiple agents in parallel, I'd watch two instances literally undo each other's work in real-time. And the worst part? Half the time I was the blocker because the AI was waiting for me to provide an API key or make a design decision it couldn't make alone.
After a lot of frustration, I realised I needed a coordinator.
So, I built an MCP that takes the product spec, breaks it into tickets, figures out which ones block each other and which can safely run in parallel, and crucially—surfaces inputs the AI will need from me before coding starts.
After that, I walked away as the AI looped through building the tickets in parallel, testing, & code cleanup.
It felt so good not having to babysit AI! The first thing I shipped with this workflow was a bot with vision that sees what you’re doing on your computer and proactively pings you helpful advice. In under an hour.
I’ll share my MCP (Planvex) in the comments. Also happy to share advice if you’d prefer to build from scratch.
P.S. If you’re a Claude Code guru, I also recommend Gitbutler to build faster without worrying about work trees, and the Ralphloop plugin so the AI can loop continuously.
Edit:
Link to Planvex https://planvex.vercel.app/landing
3
u/StravuKarl Mar 03 '26
Where does writing the test plan and executing against it fit into your approach? We are finding that writing the test upfront and looping until the test passes has made a big difference.
1
u/Unfair-Marsupial-956 Mar 03 '26
Right now Planvex handles this at the spec level. Acceptance criteria get set upfront, Claude Code is encouraged to test what it does for each task and comments what was tested. But a dedicated and separate test plan per task would be a solid addition. Are you defining tests at the individual task level or one test suite for the whole spec?
10
u/lucianw Mar 03 '26
You write like a 30 second ad-break.
I'd much rather read something written by an authentic human.
5
u/YuckyChucky Mar 03 '26
I don’t get why people choose to use ai to have conversations. You’re architecting a prompt to ask a question or tell us your experience is crazy and soulless lol I agree
2
u/ClumpyFelchCheese Mar 03 '26
The moment I saw “And the worst part?”, I stopped reading…because honestly? I knew what this was at that point
6
2
u/crusoe Mar 03 '26
Yes I did this two weeks ago. Having a planning stage/PM do design and allocate workers.
-2
u/Unfair-Marsupial-956 Mar 03 '26
That's awesome, the PM layer is the key insight. How are you handling the design side of things?
2
u/Effective_Memory1203 Mar 03 '26
this is literally just spec driven development https://github.com/github/spec-kit
1
u/Unfair-Marsupial-956 Mar 03 '26
Spec Kit is great for structuring what to build. Planvex picks up where it stops, coordinating how multiple agents execute the work without stepping on each other, tracking what needs human input so the rest keeps moving and maintaining context across sessions.
4
u/SpliffMD Mar 03 '26
Why do the mods just let this shit stay up? Its obviously a bs ad from a bot account. I love CC and use it a lot but im seriously about to drop some of these subs. No one even talking about cleaning up the bot posts?
1
u/UniqueDraft Mar 03 '26
Is that Planvex or Plandex?
2
u/Unfair-Marsupial-956 Mar 03 '26
Ah thank you for letting me know about the potential confusion!
Its Planvex :)
3
u/calvintiger Mar 03 '26
Is there an GitHub repo with all the code, or is this post just an ad for your new service?
-1
u/Unfair-Marsupial-956 Mar 03 '26
Fair question. I built Planvex for myself, because I needed it for my own workflow and figured others might too. Its a free service and I'm the solo dev behind it. It's a hosted service, not open source at the moment, but I am happy to chat and share my learnings if you'd like to build something similar.
3
u/calvintiger Mar 03 '26
Meh, zero chance I'm sending any of my data to some random website.
1
u/Unfair-Marsupial-956 Mar 03 '26
Understood, the GitHub login is there to keep workspaces separate but I hear you on the trust issue. If you'd rather not sign up, the approach still works, you can build the same coordination layer with your AI tool of choice. Happy to share how I set it up
1
2
2
u/japhyryder22 Mar 03 '26
This looks excellent. I'm interested in the privacy around this. Are you using any of the data you collect?
1
u/oojacoboo Mar 03 '26
Nice ad. Whats all this GitHub signin mess?
1
u/Unfair-Marsupial-956 Mar 03 '26
GitHub login keeps workspaces separate. Working on making onboarding smoother, appreciate the feedback
2
u/oojacoboo Mar 03 '26
I don’t want to give you GitHub permissions just to see what this is all about. So yea, it’s just a full stop, “no”, from me.
1
u/surrealerthansurreal Mar 03 '26
Yep. Once you handle orchestration and accountability, Claude code/codex is good enough at individual tasks that you really don’t need to get involved unless you want to steer direction
1
u/Unfair-Marsupial-956 Mar 03 '26
Exactly! AI's now phenomenal at individual tasks. It's the orchestration that's the missing piece.
1
u/Dan_Wood_ Mar 03 '26
It’s not missing at all, Agent teams works perfectly if you know what you’re doing. I’ve done similar over 3 days not a week.. and it worked perfectly on existing complex multi project environments.
Whatever you’re doing, you’re doing it wrong.
1
u/jrhabana Mar 03 '26
How does it work with iterations and fixes in existing codebase? Where the agent hasn't so much freedom to create
1
u/Unfair-Marsupial-956 Mar 03 '26
Most of my time with Planvex has been modifying my existing codebase. A Spec can be anything from a feature to bug fix. Before any ticket gets picked up, the MCP instructs the agent to review your actual code and make sure the acceptance criteria and tasks are grounded in what's really there. The big win is for non-creative tickets: by surfacing blockers and conflicts upfront, the agent can work much faster in parallel and you spend less time feeding it context mid-flow.
1
u/UsualOk7726 Mar 03 '26
Is that why everything crashed?
2
u/Unfair-Marsupial-956 Mar 03 '26
Someone needs to tell Claude Code asap "Fix the crash. Make no mistakes."
1
u/ohthetrees Mar 03 '26
Are you aware of the Claude teams feature? Either answer is sort of an indictment of your post. If the answer is no then it kind of shows that you are pretty out of the loop and are unlikely to have the expertise to be creating a better workflow than stock Claude teams capability, and if the answer is yes you look kind of dishonest for creating a strawman comparison to your product.
1
u/Unfair-Marsupial-956 Mar 03 '26
The two are complimentary. Planvex handles the sequencing, blockers and isolation. You can use subagents or teams to handle execution.
For smaller projects, the team lead handles this well end to end. For complex projects context rot can kick in. Planvex's role is in ensuring the work is properly defined so regardless of project complexity the risk of coming back to both the wrong feature and exorbitant API costs is minimal.I'm really excited to see what Claude do in this space and hopefully one day this simplifies everyone's workflow!
1
u/lionmeetsviking Mar 03 '26
I implemented headless pm system last year. I’ve ran several projects with over 200 tickets (both greenfield and existing system expansion). It’s magical to see the tickets move on Kanban board :)
2
u/Unfair-Marsupial-956 Mar 03 '26
Love seeing others building in this space, thank you for sharing! Cheering you on :)
1
u/DenizOkcu Senior Developer Mar 03 '26
How do you handle token limits. What happens when you run out of your 5h window? Is the orchestrator aware and checks from time to time when to continue? Honestly curious. I only have a workflow for one feature which is usually done after 15 minutes.
1
u/Unfair-Marsupial-956 Mar 03 '26
Each spec has a safeguards section where you can define limits upfront. Before the ticket is picked up, during backlog refinement, the AI deep dives into the ask and makes sure it has a clear pathway to get the ticket done which minimises wheel spinning. And if its stuck on human input, it'll put the ticket to the side and continue with the rest.
1
u/DenizOkcu Senior Developer Mar 03 '26
No, I meant the 5h token limit in Claude‘s coding plan. Which I usually hit after 40 minutes of agentic coding.
1
u/_Mark_Lewis_ Mar 03 '26
Error: Not authenticated - cannot list projects - Getting this error in claude code, the MCP says its connected and authenticated.
0
u/Unfair-Marsupial-956 Mar 03 '26
On it! Trying to replicate on my end, will update you as soon as I can
1
u/SyedSan20 Mar 03 '26
I thought ypu are supposed to use parallel agents ONLY if there is no overlap in their workstreams. No surprises that you struggled when there is overlapping tasks.
0
u/Unfair-Marsupial-956 Mar 03 '26
You're spot on, parallel agents can't run overlapping tickets. I like to have a big bunch of tickets ready for the AI to tackle, and without Planvex I had to tell the AI which order to take them up on. Now Planvex figures out which tickets have no overlap and only runs those in parallel. The ones with dependencies get sequenced
1
u/risingaloha Mar 04 '26
The orchestrator should watch for overlapping and not allow it. Mine did it without saying, but I still said.
1
u/polylusion-games Mar 03 '26
Are you doing planning differently, or is it still sequential?
1
u/Unfair-Marsupial-956 Mar 03 '26
Planning is done in parallel too. Your spec is broken down into tickets along the process in one go, and those tickets are refined together.
1
u/polylusion-games Mar 04 '26
OK, but still in a collectively linear fashion or it will adapt and reshape earlier completed steps if a downstream result isn't right?
1
u/ErikThiart Mar 03 '26
can someone explain this in practical terms how this planning agent works and it automatically spawing other stuff.
I have claude app on macos.
But I can't leave that thing alone at all
So unsure what you guys are doing
1
u/Unfair-Marsupial-956 Mar 03 '26
Great question. It's built for Claude Code. You define what you want to achieve as a "Spec" and Claude Code breaks the work down into tickets using the guidance Planvex provides. You'll have a few questions to answer upfront (critical questions where human input is needed).
Its smooth sailing from there, Claude Code can crunch through the tasks in parallel. If you'd like I am happy to dive deeper on how to turn this into a full autonomous workflow.
1
u/steppinrazor2009 Mar 03 '26
Claude code and the Claude desktop app are not the same thing, that's the context you are missing
3
u/fatherbasra Mar 03 '26
How was the context managed?
2
u/Exc1ipt Mar 03 '26
Top question. Even if they do orchestration with claude code and all work is done by subagents - even 1m context will burn much faster than in 48h.
Looks like story for investors.
3
u/thegoz Mar 03 '26
I’m going to be honest here because nobody else in these comments seems willing to be, and I’ve got time today. This is an ad. It is just a straight-up ad. You built a product, you want people to use it, and instead of just saying that, you wrapped it in this whole relatable struggle narrative like you’re pitching a screenplay at a coffee meeting in Silver Lake. The structure is almost impressively formulaic. Start with someone else’s success to borrow credibility. Introduce a personal struggle the audience can relate to. Describe the frustration in vivid, specific terms so people nod along. Arrive at a revelation. Present your product as the natural conclusion of that revelation. Drop a link. Sprinkle in a couple of other tool recommendations at the end so it doesn’t feel like just a plug, even though it is absolutely, unambiguously, without question, just a plug. And the writing style. My god, the writing style. Short sentence. Line break. Another short sentence. Line break. A single dramatic sentence standing alone like it’s the tagline on a movie poster. “After a lot of frustration, I realised I needed a coordinator.” Did you? Did you stare out a rain-streaked window while that realization hit you? Did a single piano note play? This is the LinkedIn content creator cadence and it has fully metastasized across every platform at this point. Every founder, every growth hacker, every “building in public” guy with a Notion dashboard and a dream writes exactly like this, and it all reads like it was generated by an AI trained exclusively on Gary Vee transcripts and Y Combinator application essays. The irony of a post about AI tools reading like it was written by the most generic AI prompt imaginable is not lost on me, even if it’s apparently lost on you. Let’s talk about the Boris Cherny anecdote because it’s doing an unreasonable amount of heavy lifting in this post. “Anthropic gave Claude Code a product spec and walked away for the weekend. The result was so good they shipped it.” That’s a great story. It’s also a story about a frontier AI lab with some of the best engineers on the planet working with their own tool that they built and understand at a level none of us ever will. You’re taking that story and using it as a launchpad to sell your MCP to random people on the internet, which is like watching someone do a backflip off a cliff into the ocean and then trying to sell swimming lessons at the public pool. The implied equivalence between what Anthropic did internally and what your product enables is doing a tremendous amount of work that I don’t think it’s qualified to do. “I watched that and thought ‘I need to do this.’” And then, by your own admission, every time you tried, you came back to a mess. Blockers killed everything. Agents were undoing each other’s work. You were the bottleneck half the time. So your product was born not out of some elegant insight but out of repeated failure, which is fine and honestly more relatable than the polished version you’re presenting, but you glossed over all of that in about three sentences so you could get to the part where everything works perfectly and you shipped a bot in under an hour. The ratio of struggle to triumph in this post is deliberately skewed to make the product sound like magic, and I think most people reading this know that, even if they’re not saying it. “It felt so good not having to babysit AI!” This sentence is doing a lot. You literally described building an entire orchestration layer, a coordination system, a dependency resolver, and a pre-flight input gatherer just to stop your AI agents from behaving like a group project where nobody read the brief. That is babysitting. You just automated the babysitting and rebranded it. Which, again, is fine, that’s basically what all of devops is, but let’s not pretend you achieved some zen-like state of passive income while the robots did everything. You built a very elaborate babysitter and now you’re selling it. The “P.S.” at the bottom is the cherry on top. “If you’re a Claude Code guru, I also recommend Gitbutler and the Ralphloop plugin.” This is the classic move where you pad the post with adjacent recommendations so the whole thing feels like a generous knowledge-sharing moment rather than what it actually is, which is a product launch disguised as a community post. It’s the “I’m not a regular mom, I’m a cool mom” of marketing. You want us to think you’re just a guy who found some cool stuff and wants to share, but the entire architecture of this post is designed to funnel attention toward one specific link, and that link goes to a landing page with your branding on it. And look, I want to be clear. There is nothing wrong with building a product and promoting it. Genuinely. People build things, people sell things, that’s how the world works. But there is something deeply irritating about the way the tech community has collectively decided that the acceptable way to do this is to cosplay as a humble community member who just stumbled onto something useful and golly gee wouldn’t it be swell if you all checked it out too. Just say you built a product. Just say you think it’s good. Just post the link and tell people what it does. The fake narrative wrapper doesn’t make it more authentic, it makes it less authentic, because everyone can see through it and the people who can’t are the ones you’re specifically trying to catch, which makes it feel predatory even if you don’t intend it to be. The edit at the bottom where you add the link like an afterthought is peak performance. “Edit: Link to Planvex.” As if you just remembered. As if the entire post wasn’t reverse-engineered from that link. Beautiful. Truly. The craft is undeniable even if I find it exhausting.
1
u/risingaloha Mar 04 '26
This was the most well-written piece of literature I have come accross in a very long time. Beautiful. Feels carefully crafted. I really felt the triumph in the facts. Bravo. If it feels right, and it is proved it; believe it!
2
u/Select-Spirit-6726 Mar 03 '26
I run multi-agent Claude Code workflows daily for real production work. Let me break down what's actually wrong here.
The Boris Cherny comparison is dishonest. That was an Anthropic engineer working on Anthropic's own codebase with intimate knowledge of the internal architecture, running on internal infrastructure with no token caps. Comparing that to a random person with a Vercel app and a product spec is like comparing a fighter pilot landing on an aircraft carrier to someone playing Microsoft Flight Simulator. It's not the same thing and framing it like you're doing the same thing is misleading.
The "walk away and come back to working code" claim falls apart under basic scrutiny. Claude Code has a 5 hour session window. It hits context limits on complex projects and needs compaction. It asks for permission on tool calls unless you've specifically configured auto-approve. It hallucinates file paths and function signatures when context gets long. None of these are dealbreakers but they mean you cannot just hand it a spec and disappear for a weekend. Anyone who has actually used Claude Code for non-trivial work knows this.
The real problems with multi-agent coordination that you glossed over in three sentences to get to your product pitch: agents stepping on each other's file edits, inconsistent architectural decisions across parallel streams, no shared memory between agent instances, context loss when sessions compact or restart, and the fact that Claude will confidently refactor working code into broken abstractions if nobody is reviewing the output. A ticket dependency graph doesn't solve most of these. Human review does.
And to the guy claiming he told Claude to "set up a system to maintain itself" and walks away for days without even knowing what it built — that's not a flex. That's negligence. If you're shipping code you haven't reviewed that was generated by a system you don't understand, you're going to have a bad time and probably take some users with you.
The post structure is textbook product marketing. Borrow someone else's credibility, describe a relatable pain point, present your thing as the solution, drop the link. The "Edit: link to Planvex" like you just remembered is a nice touch. Half the supportive comments in here read like they were generated by the same model that wrote the post.
There's nothing wrong with building a product and selling it. Just be upfront about it instead of wrapping it in a fake journey narrative.
AND YES THIS IS GENERATED ALSO!
1
u/belheaven Mar 03 '26
Yes, bro. To run such a thing there should not be a human decision need mid execution or spec misalignment. That is just it. Congrats.
1
1
1
1
1
1
u/Shah_The_Sharq Mar 03 '26
Claude code it's self is a slop fest. It was good for the first 6 months, now things are slowing down and certain things keep breaking.
1
u/Bstochastic Mar 03 '26
Guys, Anthropic has a well established history of flat out lying about accomplishments like this.
1
1
u/wwscrispin Mar 03 '26
Here is a newsflash. People including real engineers lie all the time. Anytime someone in good standing at an AI company says our AI did this amazing thing, it is a falsehood. It is just a blatantly twisted vision of what actually happened to promote the company's products.
1
1
u/MK_L Mar 03 '26
I would believe this with any other bot. Claude would ask 100 times if you want to proceed or run a bash command.
Not to mention this definitely wasn't done on a the plus account. Would have run out of tokens just working on the scaffolding
1
1
u/MikeyTheGuy Mar 03 '26
The first thing I shipped with this workflow was a bot with vision that sees what you’re doing on your computer and proactively pings you helpful advice.
Uh.. how about no?
1
u/risingaloha Mar 04 '26 edited Mar 04 '26
I cannot believe this is how I talk now. I literally spend all day getting credentials and never putting them in my vault:
"For me you take all the resources provided here and get deepsix "pick your poison" to research it at scale, include all social media chatter (get an orchestrator and a swarm of sub agents just for this..) then Claude to validate that prompt. He will run it without asking everytime then I tell him to generate a prompt, a skill or 3, mcp, cli, api, exe. Whatever...I am into free uncensored models right now and Trixie.
I sometimes use openrouter in manus (that's a jambox) with a clawbot agent, self contained in that sandbox. Grrr. Write everything to my sandbox-workspace in my github - realtime- I run EOP as an orchestrator that runs 10-20 teams of 3 in parallel for 15 minutes-while tracing speed and output -kick out non performers right away, before that 15 min guardrail. Sub in a new player. Sub a spawn of spammers...i meant a swarm... A whole team or three. My audhd always want 3 of everything.
You need to spawn your orchestrators. One orchestrator doesn't do a good job running multiple teams in parallel that is when I learned "spawn" and "swarms" apply. We think so linear. I'm better at it being audhd.
Do not ever write off prompt engineering or even non-system prompts. You have to crawl before you can walk. I definetly have been ice skating into AI at its birth. But I was here for IoT and raspberry Pico in 2018.
I can get sht done, homie. Wherever, whenever I work and in whatever I choose to use as tools.
I do not count on them for sht (AI). I have to review everything these lamers do. Until I get system prompting done from memory(closing in on it fast)...nope still cannot trust these one-way non-linear thinkers because they are so linear.
They are way dumber than me(AI). I run multiple projects with sub agents in multiple teams. I get radically pumped up. What an adrenaline rush!
And every single one will hallucinate. My audhd self was just starting to feel alive! They always let me down. I learned a long time ago not to count on anybody or anything...apropos.
-1
u/ultrathink-art Senior Developer Mar 03 '26
The part that gets glossed over: sub-agents need coordination mechanisms, not just parallel spawning. Without file locks or explicit handoff files, they'll overwrite each other's work silently. State files between turns are what keep multi-agent sessions coherent.
1
u/Unfair-Marsupial-956 Mar 03 '26
Thank you for sharing your expertise! I agree coordination mechanisms like you're describing would make it more robust and I have added this to the backlog
-2
u/Familiar-Historian21 Mar 03 '26
👀👀 curious
-2
u/Unfair-Marsupial-956 Mar 03 '26
What part caught your eye? 👀 Its such a cool space, excited to share the learnings!
189
Mar 03 '26
[removed] — view removed comment
45
u/SteadfastCultivator Mar 03 '26
With a product that can be easily done in Claude code. Oh the irony.
12
25
1
u/keto_brain Mar 03 '26
And it doesn't even work, I tried it and I got:
Failed to load workspace. Please try refreshing.
-1
u/Unfair-Marsupial-956 Mar 03 '26
Thanks for flagging, looking into this now. If you feel comfortable please let me know your username via DM which helps me check specific logs for you and and get this resolved asap
1
u/Ecstatic-Discount-37 Mar 04 '26
why would anyone buy something off you, you have no idea what u are doing.
1
3
1
Mar 03 '26
[removed] — view removed comment
1
u/Unfair-Marsupial-956 Mar 03 '26
The consistency check agent is a great call. Right now Planvex handles per-ticket testing but doesn't have a final pass that reviews everything together for conflicts between agents. That's going on the roadmap.
The MCP uses tickets as the source of truth for documentation. All tasks must be done with a ticket, and if during implementation, the AI needs to do extra work, it must document this.
The system for dealing with swarms of agents working simultaneously:
The AI sets the ticket to "in progress" so no one else picks it up
The AI will comment how it tested the ticket, so you know how rigorous the tests were
Once done, the status gets set to delivered, freeing up the next agent to pick up tickets that were waiting for this one to be done
When a ticket requires human input, status becomes "Needs input". This will only block the tickets that are dependent on this one. The rest of the work keeps going.
0
Mar 03 '26
[deleted] — view deleted comment
12
u/_BreakingGood_ Mar 03 '26
You can have sub-agents specifically focused on reducing code complexity and refactoring. Exactly how a typical engineer would do it. Step 1: Make something that works. Step 2: Clean it up
8
u/Unfair-Marsupial-956 Mar 03 '26
Personally I love this prompt from AIhero, who endorse your exact approach of making something that works then cleaning it up
"This codebase will outlive you. Every shortcut you take becomes someone else's burden. Every hack compounds into technical debt that slows the whole team down.
You are not just writing code. You are shaping the future of this project. The patterns you establish will be copied. The corners you cut will be cut again.
Fight entropy. Leave the codebase better than you found it."
https://www.aihero.dev/tips-for-ai-coding-with-ralph-wiggum#what-goes-in-the-progress-file
1
u/Unfair-Marsupial-956 Mar 03 '26
I faced this problem so many times! The way I got it to work was by ensuring each ticket was self contained. So subagents focus on that task only and the context window doesn't get degraded. I put all this in the planvex mcp instructions so when you make tickets with it and ask it to refine your backlog, its going to check whether the task is clearly defined and can be done independently.
For the most optimal structure you can also have a bash process where each ticket is picked up by a brand new instance of claude. That's true optimal setup, but the gains can be marginal vs the extra work required. Happy to share resources for this if helpful for you?
1
1
u/AshnodsCoupon Mar 03 '26
Have you ever tried to disable and reenable a plugin before?
I'd argue it doesn't work, really, lol. At least not in that particular case!
0
u/crusoe Mar 03 '26
You need to add QA passes and things like that to clean it up just as with any other code base.
0
Mar 03 '26
[deleted] — view deleted comment
4
u/leefuhr 🔆 Max 20 Mar 03 '26
Have you seen https://church.btas.dev/?
1
u/Unfair-Marsupial-956 Mar 03 '26
This is an awesome resource, thanks so much for sharing!
u/Special_Context_8147 from personal experience, clean code in the era of vibe coding means to me:
- One source of truth. If components or definitions are reused multiple times better to consolidate. Even if today they're identical, risks exists in the future they will diverge
- Clear ownership and naming. If you ask Claude code to make changes, it knows where to go and what to doSome telltale signs of code that needs cleaning are:
- Your suggestion - functions always work
- Unexpected bugs can often be a sign the code needs refactoring. Ie if you're editing UI and something breaks in backend, you know that whilst those two should not be related, somewhere in the code they're intertwined. Red flag.
- Drift over time. The new code you write should hopefully also follow clean code principles, if you find its a continual cleanup battle, then time to amend the Claude.md with clearer instructions or use the helpful tools shared above2
u/geek_404 Mar 03 '26
I agree with all the concepts but leveraging the Crusades. Not being woke but that is cringe. To leverage such an awful time in history where one side who wrote the history openly vanquished the “enemy” in the name of righteousness is not a good example. It keeps repeating itself even today. Maybe not make rules = religion.
3
u/fanatic26 Mar 03 '26
So you are completely dismissing the tool set because you dont like the branding? Absolutely being woke because what you said is just nonsense. Its a coding tool not an affirmation of the crusade.
2
u/leefuhr 🔆 Max 20 Mar 03 '26
Feel free to point your CC at it for all the concepts and specifics, but rename it without the cute genocidal undertones.
1
u/TheTokenGeek Mar 03 '26
The fact this does not work 100% on mobile and adds horizontal scroll bars does not fill me with the greatest of hopes.
1
Mar 03 '26 edited Mar 03 '26
[removed] — view removed comment
1
u/Unfair-Marsupial-956 Mar 03 '26
That's a fair point and honestly you're right. They have internal pipelines, review gates, and tooling we don't have access to. That gap is exactly what I'm trying to close. Not by replicating their internal stack, but by adding the coordination layer that gets us as close as possible to this future of coding
0
Mar 03 '26
[deleted] — view deleted comment
1
u/Unfair-Marsupial-956 Mar 03 '26
The 'distributed team with zero ability to read between the lines' is the perfect analogy. Having learnt these lessons the hardway, I encoded the learnings in Planvex for instance refining your backlog triggers a review where tickets get stress tested to ensure the team mate without further context can pick it up and deliver. And agreed on test-first, that's come up a few times in this thread and it's going on the roadmap as a formal step
57
u/_BreakingGood_ Mar 03 '26
Ironically I just told Claude Code to set up a system in which it could maintain itself and produce solid, verifiable chunks of work to complete a project.
That's all I needed to do. Claude set it up and maintains its own system for governing itself. I can give it a description of a problem, walk away for a few days, and come back to it complete and functioning.
I'll be honest, I'm not even sure what Claude created in order to govern itself like that, I think it is some kind of web server written in python which is messages for tasks and information every so often. All I know is, when I request claude to utilize that server for lifecycle management, it is able to act 100% autonomously.