what is the most minimal way to build a working software loop (or factory) especially if working on a greenfield project where the specs are very messy?
i think before we even consider a loop we need to solidify the guardrails first:
1. tech stack, db schema, folder structure, etc
2. strict linting, formatting and ci implemented, future lint rules can come later
3. wire up some form of code review agent,
4. i think this is the most important, build one golden path feature iteratively with one single agent such that future sessions mirror this path.
5. one single agents.md? (i've not been seeing this being super influential recently)
and from there:
1. plan and design with an orchestrator agent (opus 5.5?) that has all the context from slack, granola notes etc.
2. once aligned, create tickets for the big plan. have the orchestrator spawn subagents
3. verification step
4. if step 3 requires it, then do a human review
5. merge
2
32
Dominic Cabansay retweeted
It's been nearly 6 months since I posted a 'watch me work' deep dive on my skills.
Since then, they've become the most-starred skills repo in the world.
So, here's 70 minutes of me building a 21,000-line PR, especially focusing on:
- DDD with /grill-with-docs
- Improving your codebase with /retro
- How to do human review effectively
Enjoy!
hmmm marginally better than opus 5.5, here we go again
Introducing Claude Fable 5.2 and Claude Mythos 5.2, designed to tackle the most daunting technical challenges.
They’re capable collaborators on ambitious projects in many fields, and show improvements in areas like coding, reasoning, and vision.
22
super proud of this experiment! check it out, some really cool findings in here 🙌
withpanorama.substack.com/p/…
honestly i get more excited when a new model fits on one GPU than when it tops a leaderboard. like the first thing i want to know is whether i can fine-tune it without having to worry about budgeting
1
62
pstack is built on the idea that agents extend whatever patterns your codebase already has, so the foundations need to be right.
which raises the question: how do you get a messy codebase into solid shape before you start using pstack?
1
42




