121–130 of 187 posts
I’m a solopreneur working on a fairly large number of independent projects. I use Claude Code to initiate a project using Sahil’s ME skill pack and write a high-level spec to a Linear ticket. If/when I’m ready to work on that idea, I convert it to a project, decompose the top ticket into more issues. I also have Claude code add to each issue with deepseek, sonnet or opus tags based on which is most appropriate for th…
I am using Spec Driven Development approach implemented as a Claude Code plugin since Feb for all mid + size tasks. The idea is to write detailed specs first using agent help doing research and interviewing, decompose the task into smaller subtasks, write detailed spec for each task, implement each task separately. You can restart the session after every step in the workflow and after each subtask implementation sinc…
Github spec kit, spec-kitty, symphony, GSD, this.
How do people decide on the framework other than try them all.
p.s. found this mind-boggling list of them all https://github.com/cameronsjo/spec-compare
There's lots of ways. You have to upskill through the stages IMO. Write code, write w/ agent, write w/ multi agents, write w/orchestrators. My way is to just run a giant AI agent factory engine and make the agents full flow do everything. (plan long term, write prd, task, review). Here's ~4000 commits in last month as an example, i have about ~10k ish including private/work stuff? https://github.com/portpowered/you-a…
Have you been able to build anything substantial with AI factory itself? I have done some of these experiments myself on these sort of things and found they ended up often being less effective than using the latest tools in harnesses like claude code. But curious if you've found it to be a big unlock. I have been doing some of this industrial engineering myself.
For example we had this problem where we had to take in customer inputs for requests and calculate out the projected downstream TPS. This is fairly complex since we run a query parser/orchestrator.
This is expensive to write myself or to have engi's do it, but the scaling algorithms are all there and we have excel sheets for spreading out overall costs.
so then all was needed was basically write out a big spec of the reqs - give it the docs/parser code/excel sheets, then just have it span out the pieces as a sequential checklist. 1. CI/OPS 2. docs 3. test infra 4. incremental build out in phases to chain it all together.
There's lots of ways. You have to upskill through the stages IMO. Write code, write w/ agent, write w/ multi agents, write w/orchestrators. My way is to just run a giant AI agent factory engine and make the agents full flow do everything. (plan long term, write prd, task, review). Here's ~4000 commits in last month as an example, i have about ~10k ish including private/work stuff? https://github.com/portpowered/you-a…
Genuinely curious - in your case, where do the requirements for what needs to be built come from? In every project I've touched, business requirements are always the bottleneck - so I've never been able to wrap my head around what kind of requirements can be fed into a setup like this at high enough volume to justify it.
IDK i've always been able to get senior managers/managers to give me lots of leeway to do wtv i want and figure out problems. At least in most places i've worked at.
i work on platform stuff mostly, so there's always a large need for stuff. the backlog alone b4 all the agentic stuff was roughly 20-30x the capacity of any team (per year). 80% of requests were usually SVP goals and we'd just outright drop them due to lack of capacity or request HC transfer/away teams.
i.e. internal improvements alone were always massive (not gonna talk about prod code/cross team organization).
1. we need better test coverage for x,y,z
2. we need to be able to eval the long term costs (XX growth YOY, how to reduce)
3. the internal system streaming is inefficient, need to eval the alternative systems
4. we need better ops handling/management automation for issues and sev3s/sev2s. i.e. scaling, anomaly analysis, bugs introduced, improved metrics, dashboards.
5. DX stuff needs better handling, people keep confusing themselves on how to onboard. better docs on how to onboard, automation,
6. teams x,y,z are fighting with each other bcz they don't have a good grasp on systems, improve internal docs on arch and interop
7. we need automation to be able to more easily test our systems in an adhoc fashion
8. there's no linters for API platform, leading to bad results and inconsistency.
9. we're seeing bugs in the code, but aren't appropriately manualy testing after deployments. spawn 100 agents to do it, compile the results. do it every X days, feed the bugs back into the system.
i could go on and on. and this is one service, usually you own quite a few, and each one has their unique set of challenges.
Earlier quoted context omitted.
Naive question: how much time do you spend doing so vs. Doing the actual work yourself?
I am building AI agents full time since Nov 2024. I stopped coding completely around mid summer 2025 using Cursor at that time. When you build platform-like application, and have few plugins already, ai coder can create next one in a way you won't recognize which one is written by you. At the end of 2025 I switched to Claude Code. Compared to Cursor this opened a different level of automation, including fe possibilit…
I am using Spec Driven Development approach implemented as a Claude Code plugin since Feb for all mid + size tasks. The idea is to write detailed specs first using agent help doing research and interviewing, decompose the task into smaller subtasks, write detailed spec for each task, implement each task separately. You can restart the session after every step in the workflow and after each subtask implementation sinc…
I would love to see examples for various types of specs written, as in actual texts of the specs for various types of it. It would also help to understand how are changes to specs handled? Is the agent given both old and new versions to figure out the updates needed? Thanks.
-- https://github.com/sermakarevich/chunker/blob/master/.sddw/c...
-- https://github.com/sermakarevich/chunker/blob/master/.sddw/m...
- ccw (claude code workflow - plugin to compile generic claude code workflows based on sdd approach) - https://github.com/sermakarevich/ccw/blob/main/.sddw/claude_...
Btw you can use ccw to create your own custom version of sddw quite fast - with specs format and sequence of steps that suit you best.