DIVx0
Joined 15 years ago
Joined 15 years ago
Now all you really have to do is chat with claude about what you're thinking about building.
In plan mode, claude can't edit anything and has some extra "you're an expert at planning!" prompts prepended to your initial message in plan mode.
And then either when you're ready or Claude thinks the "plan" is gelling, it'll suggest stopping and let it write up a detailed plan. CC will dispatch some "planning agents" with prompts that your 'main' CC has crafted for that agent to plan for within the context of your conversation and what parts of the codebase it should look to integrate/explore.
Once all that is done, it will display it to you and then offer to "clear context and implement" - where it will just get to work. Or it will offer to go back to chatting and resolve whatever was misunderstood, or if you had a new idea you wanted to mix in.
These plans are saved as markdown in your .claude/plans directory.
Plan mode is handy on the on-off. But if you enter another plan mode, thinking claude would learn from, or build off a previous plan spec, it won't unless you explicitly say something like "read previous plan <path to plan file> and re-use the scaffolding directives for this new project"
Like most spec driven development tools, GSD works well for greenfield or first few rounds of “compound engineering.” However, like all others, the project gets too big and GSD can’t manage to deliver working code reliably.
Agents working GSD plans will start leaving orphans all over, it won’t wire them up properly because verification stages use simple lexical tools to search code for implementation facts. I tried giving GSD some ast aware tools but good luck getting Claude to reliably use them.
Ultimately I put GSD back on the shelf and developed my own “property graph” based planner that is closer to Claude “plan mode” but the design SOT is structured properties and not markdown. My system will generate docs from the graph as user docs. Agents only get tasked as my “graph” closes nodes and re-sorts around invariants, then agents are tasked directly.
I've been doing this for decades, and I've never seen that attitude work with any 'leader.' I'd hate to work for you. Ever hear of servant leadership? Or hear the line "My job is to clear the runway for you"
Managers are cost centers, 'your' employees are what keep you employed, give them the respect they deserve.
Tell me more about how humans are criminals for existing? You hate the idea of someone standing on your piece of dirt without your express say-so that your preference is to live under an umbrella of fear and suspicion of your neighbors?
Forgive me, this is not how I want to live. I wonder how many Norwegians who settled in Minnesota were illegal immigrants?
I guess I should thank you for saving my time? Plenty of others in this space.
I have since solved this problem: 1) Tool-Check PLUS from Wera: fantastic and highly condensed set of sockets, bits, ratchet and driver. all high quality. 2) Leatherman ARC: replaced a more basic multi-tool. I like the high quality blade material and the whole thing is very durable, i can squeeze and crank the pliers without worry.
The leatherman is a bit of a splurge but I highly recommend the tool-check for tool-using EDC minded folks. They make good gifts too.
sidebar: I've had a lot of problems with the AppleTV plex app, it does not play some HDR content well, or at all. Plex on my nVidia Shield works well.
Argon in low and medium mode had higher quality results than it did when running in high mode, almost every time. My tasks involved the agent finding some details in a raster image and then mark it up with predictions about what it found.
Argon on high would do the work, and then a whole bunch of other stuff i did not ask for. All that extra broke everything else downstream from the analysis.
However, doing the same work with Argon in low effort was on par with results from Haiku 5.5 (xhigh) and GPT-6.1-Terra (medium). So, Argon low works better than Argon high, but for my tasks -- a very weak model relative to how google positions it.
I'm ready for Geimini Unobtanium!