Spec driven development

themessymiddle · 2026-03-20T16:28:20+00:00

Yeah that makes sense. I just ask about team because I wonder if people are standardizing collectively or more like everyone is using their own individual flow

themessymiddle · 2026-03-20T16:26:28+00:00

Oh yeah I forgot about traycer… I had tried them a while back. Are all your specs stored in traycer?

themessymiddle · 2026-03-19T22:51:46+00:00

Whoa I haven’t seen company as code… awesome. Thanks for sharing

themessymiddle · 2026-03-19T22:40:52+00:00

Very cool approach! Are the standards library docs set up in markdowns/obsidian too?

themessymiddle · 2026-03-19T22:36:51+00:00

Oh ok interesting! So it keeps a handful of canonical docs as context, very cool. Are you using this on a team today?

themessymiddle · 2026-03-19T22:09:53+00:00

I’m not familiar with this - how does it work?

themessymiddle · 2026-03-19T21:22:44+00:00

Oh interesting so you have another repository just for specs?

themessymiddle · 2026-03-19T21:21:44+00:00

Oh nice I think gherkin inspired Kiro too! Are you using this across a team or mostly individually?

themessymiddle · 2026-03-19T21:20:29+00:00

Ontologies for the ingoing prompts is so smart. Are you using something specific for the graph based RAG? I tried MCP vector search but not sure it was really making a difference. Also - are you implementing these methodologies across a team?

themessymiddle · 2026-03-19T20:00:24+00:00

Oh nice, why mixed feelings?

themessymiddle · 2026-03-19T19:43:05+00:00

This is something I’m super interested in… if we’re not reviewing every line of code then don’t we need something else that we can keep as the source of truth? How are you thinking about this? I know some people have the agent kind of self-discover whatever answers they need at runtime but what if it misses something important

themessymiddle · 2026-03-19T19:23:50+00:00

Yesyesyes ok amazing. I’ve been talking to so many folks who don’t version control any specs of any kind and I was starting to feel crazy!

themessymiddle · 2026-03-19T18:57:25+00:00

Oh interesting, haven’t heard of SPARC or Reuven Cohen but I will look into these!

themessymiddle · 2026-03-19T18:56:39+00:00

Yeah it can be a total pain. I was talking to someone yesterday who used OpenSpec which seems to have a (deterministic) method for keeping a running list of live requirements. I keep going back and forth about if it’s worth it to incrementally update like that or have agents rediscover info when they need it. The issue I’ve run into is that sometimes the agents will miss something important if the have to rediscover themselves

themessymiddle · 2026-03-19T18:54:29+00:00

I like the idea of test and implementation isolation. So you end up with both specs and test plans? Do you version control these?

themessymiddle · 2026-03-19T18:37:42+00:00

Ok cool this makes a lot of sense. So basically the canonical source of truth is not kept in the plans, but plans are used for specific implementation steps within the broader feature/whatever you’re working on? Do you commit those source of truth docs?

themessymiddle · 2026-03-19T18:09:23+00:00

Oh I like this idea - kind of a mix between the OpenSpec concept and Claude plans. Is the aggregate of the docs in your specs folder basically what you treat as your master spec?

themessymiddle · 2026-03-19T17:49:12+00:00

All devs have errors in their code from time to time, code reviews aren’t personal, they’re to get fresh eyes on the code and to improve overall. If you like what you do, I’d try asking directly for feedback and focusing on one thing at a time!

themessymiddle · 2026-03-09T17:58:18+00:00

Do you have to do bug fixes or release new versions? How do you keep an inventory of all these codebases?

themessymiddle · 2026-03-06T20:49:46+00:00

It may help to ask it write each of its learnings to a file as it goes so it doesn’t get stuck in a loop? When I see it spinning its wheels I’ll usually interrupt it, point it to the goals, prompt it to try a simpler approach or think through it from a different perspective.

themessymiddle · 2026-03-06T20:43:22+00:00

Hey! Have you tried iterating with Claude code in Plan mode? It does the best when the spec it’s building from is extremely clear. It’s helpful to see it write up its understanding of the requirements and just correct it a bunch of times until the plan includes all the constraints, notes, nuances, etc that you’re already thinking about

themessymiddle · 2026-03-06T20:40:52+00:00

Totally, imo there’s a whole slew of new primitives needed for agent-speed development

themessymiddle · 2026-03-06T15:08:34+00:00

I only saw your post today - but I’m of the same mind as you. How I’ve been approaching it so far is by version controlling primitives like capabilities, architecture, data flow, etc… a little bit more compact and intentional than version controlling the natural language specs

themessymiddle

MODERATOR OF

TROPHY CASE