This is a really good framing honestly. Spec-first tools are useful, but milestone-first feels way better for actually learning and not getting lost after step 2.
I like that you keep things verifiable at each step too, thats the part most AI coding tools skip and then people think theyre progressing when theyre just generating code.
how do you decide milestone size so its not too tiny but also not overwhelming?
do you track failed attempts/retries as part of progress, or only completed milestones?
Also are you planning a mode where users can switch between learning path and spec mode in the same project? I think that could be very strong.
How do you think Primer will evolve as agents get better at long-horizon tasks? The milestone and verification loop make sense now as agents fail unpredictably on complex tasks. Do tasks just get bigger and milestones scale with them?
Yes. They are trying to make AI-assisted development more structured. I am focusing with Primer more on learning-path oriented side. It means breaking things into small, verifiable milestones that one completes step by step, rather than defining a full spec upfront.
I like that you keep things verifiable at each step too, thats the part most AI coding tools skip and then people think theyre progressing when theyre just generating code.
how do you decide milestone size so its not too tiny but also not overwhelming? do you track failed attempts/retries as part of progress, or only completed milestones? Also are you planning a mode where users can switch between learning path and spec mode in the same project? I think that could be very strong.