Hacker News Reader

Comment by bilbo-b-baggins | Hacker News Reader

Look at the juxt/allium plugin. It’s a more mature version of what you’re attempting.

Also big requirements/tasks files will rot your context opening up hallucinations and drift. So I’d guess your starting point isn’t useful for larger codebases.

View on HN

Wondering if this is attempting what github.com/gsd-build/get-shit-done has done: plan your milestones, discuss them, execute them, review them. It can also review the plans by another agent before execution... Everything documented and checked in.

To be honest, I did not know what GSD was before publishing this skill (nerviousness).

I did some research after reading your and a discord comment i received and i agree that GSD is doing something more complete — full execution orchestration with context rotation. This skill is intentionally the spec layer only: interview → requirements.md + design.md + tasks.md + AI config files as I believe this is a more manageable as well as a core part of SDD to be tackled. I intend it to be composable with GSD rather than a replacement for it. After all even while using GSD one still needs a spec before execution begins and that is the gap I now want to fill.

Also thank you so much for your input, it is always good to have some proper references for a project in it's early stages to avoid redundancy.

Cool, thanks for the reply. GSD is great for new projects but it burns through tokes at quite the rate. Esp. in quality mode. Something more lightweight would sometimes also be welcome. Though there is /gsd-fast and /gsd-quick that partially fill that gap.. I'll definitely check yours out, thanks for publishing

To be fair allium is genuinely impressive, I checked it out and the custom language approach and autonomous tend/weed agents are more sophisticated than what I'm doing with this skill. The tradeoff I made deliberately was to use standard markdown files that any AI tool can read without installing anything. Allium's .allium format requires the skill to be installed to be useful; The requirements.md should work in any editor, any agent, any CI pipeline.

Also, context rot on large specs is a real limitation. I added a lightweight CONTEXT.md journal but nothing close to proper context rotation. That's filed for v2.0.

I'd also like to thank you so much for taking your time to revise this show HN and express that I appreciate your feedback.

Reply on news.ycombinator.com