Is it adhoc or you use more structured approaches like openspec? I also tend to work on a plan first, but it stays as in-session todo, which is hard to reference later.
It's ad hoc / my own framework, just found something which works for me. The exact structure is
- Work Mode - HITL/AFK
- Problem Statement
- Who It Affects - Primary / Secondary User
- User Stories
- Business Case
- Why Now
- Success Critera
- In Scope/Out of Scope [Out of Scope v. important)
- Thinnest Slice (This I've found super valuable, means you max out the amount of 'product' for your buck and avoid diminishing marginal returns or overbuilding. Often I will build this)
- Eigenfeature - What is the larger feature we _could_ (but probably won't) which would solve for this use case and other stuff I might not have thought of
- Technical Notes
- Deps
- Schema Changes
- Risks
- Final Recommendation [go / no go, including on scope]
There's a note in my Claude / Agents MD which says no net new feature gets introduced without this and I get it to move through a pipeline of folders (active, approved, shipped, proposed etc). All runs in a system of MD files and have even created a little MD Kanban from the metadata!
I guess I've stumbled into something similar. Though I don't have a fixed format like yours. I first do a lot of back and forth to generate what I call a design document also includes rationales for various points or decisions. I use both Claude and Codex to iterate on this until I'm happy. The end result includes a lot of what you mention.
I then start a fresh conversation, make it analyze the design document and code, and for larger changes, generate a high-level implementation document which includes concrete phases or steps. I review this plan and iterate if necessary.
Then for each phase I make it generate a detailed plan for that phase and save it along side the other documents. Once the phase is over, I make it write a summary of what was done, decisions made and reasons for it. And typically a good point to compact the model's context.
These documents gives additional context for when I make another model do code review, and help illuminate drift or gaps from the main design document.
I found myself in a similar workflow.
Depending on the task at hand (starting a new project, enhancement, maintenance), I let the agent create/read the markdown files that I keep updated (AGENT, STATE, ROADMAP, DESIGN, ARCHITECTURE, (CODESTYLE if I plan to modi it myself)). Then I choose the various roles that I need in this session and and have a planning phase. After that, the agent is starting implement the changes and I have a manual correction phase.
This flow works for my needs, building idea demos, prototypes or tools for my own sake.
I don't let agent code in our main code base where everything is still hand tailored. That's a conscious decision.
I noticed that the cheaper models (flash, ...) are quite hard to hold back changing files. A question for possible options sometimes results in "yes, I'll go with option A" without asking back.
Frontier models on the other hand love to plan and ask you deliberately for your consent.
I use pi.dev with almost no skills at all to understand how models really work and "feel" to work with.
Just a guess: if you want to scale a sprite at anything less than a whole ratio (e.g. 1.5, 0.7, etc), you have to choose pixels to drop out and pixels to repeat , on some pattern that looks good. There are going to be scaling ratios that look like a hot mess, especially at a low resolution like 320x240.
In context, it's talking about sprites that are going to get non-integer scaled anyway (in-game pickups), so it's just about maintaining a consistent detail level. If those specific sprites had their resolution increased, everything else would need its resolution increased to match them.
Inconsistent resolution isn't necessarily a bad thing, e.g. Elite for the BBC Micro changes video mode part way down the screen so it can display both high resolution monochrome wireframe 3D and a lower resolution color map/UI below, but it's not idiomatic to the MS-DOS style this game is going for.
The secure/double slip knot that's linked in the story. I practiced it a few times (making sure the knots are in opposite directions took a bit of retraining muscle memory) and can tie it by heart now.
On the other hand we keep seeing only marginal generational imorovements in CPU space, yet performance gains over last 10 years in CPUs are very material.
Every new model might not be a leap like it used to be, but give it enough time and improvements add up.
Nobody is disputing that. I specifically said that I can see the improvements from the last six months. What I’m saying is we can’t assume that every two years it will improve at the same rate.
The further we get into this, the more AI feels like 3-D printing. Significantly bigger and will be more widely used for sure. But nowhere near the “new industrial revolution” that all these companies are making it out to be
Do you agree that economic and behaviour shift will be comparable to mobile and we are at the times of Nokia 3310. Does it count as industrial revolution?
I think that’s kind of a strange question/parallel that doesn’t have a concrete answer, partially because even the people making these tools don’t really know where it’s going to land or what the ultimate utility is. Hence why they’re begging all of us to figure out the billion dollar applications for them.
Ultimately they are clearly here to stay but I think they are going to be incredibly important in some industries and minimally present in others (a glorified chatbot/summarizing tool for instance). Whatever form it takes it’s definitely not going to be a model where individuals have subscriptions they pay for monthly.
> even the people making these tools don’t really know where it’s going to land
exactly my point to compare it with pre-iPhone mobile market: wide (and growing fast!) adoption, clear potential (WAP websites, J2ME games), many players in the game, some real market fit discovered already (Blackberry), influx of capitial and tinkerers alike, but still a lot of unknowns where it will ultimately land.
Even if no single improvement was revolutionary (even first iPhone was just a fancy phone without App Store), overall mobile made billion dollar industries possible, for better or worse, and changed the way we live. Counts as industrial revolution, comparable to the Internet itself in my eyes.
Everyone has one at home spitting out items they need daily/weekly like was promised. I don't know if you remember the 3D printer (somewhat) boom of the 2010's but the hype was crazy when it became more mainstream. Maker spaces popping up in cities everywhere, schools showing off their units, every conference had some talk on them, startups left and right. The AI boom is basically a more-funded version of that. It was hot hot hot and people thought every home was bound to have one.
It took a while, especially because the early 3D printers were a project of calibration unto themselves, but modern printers are fairly trouble free. I accidentally melted the bottom of my blender jug on my toaster oven so I'm printing a replacement one right now. Turns out the critical mass needed is someone else having already done the CAD so I can just hit print from my phone, which makes 3D printing a reality.
The difference with AI is it affects all technology at the same time. 3d printing only affected manufacturing. What we're seeing now has impact in chemistry, medicine, software, and all other knowledge industries at the same time.
How is offline support in their mobile app? I am looking for a protonmail alternative, because it didn't open emails when I really needed while being offline.
Currently just manual. I'm not pushing the frontier here, just getting my feet wet.
While both Claude Code and Codex are capable harnesses, I definitely think there's a lot more to be gained from the harnesses. Quite a few of the times I needed to nudge the steering wheel it was things that a separate agent with the right prompt could have picked up on.
How would one create custom tools for it? opencode offers TS SDK for it, but with rust it will be something more heavyweight like gRPC bridge (similar to how terrafoem providers work).
reply