Try the superpowers plugin, let it write a spec (what do you want?) and a plan (how is it implemented). Then let it implement the plan.

Review each step as much as you care. These things take time so you can just do other stuff while it’s cooking.

With proper isolation of projects you can easily have multiple sessions in parallel. I frequently have 4 to 8 parallel Claude Code sessions, each with whole trees of agents reproducing, speccing, planning, implementing and reviewing things.

For common mistakes, you can make it remember things or rely on reviews.

You know what’s worse (less efficient) at parsing and writing code than LLMs?

Humans.

“This is a significant rewrite that will take weeks”

Done after my potty break

Try it on RAM and CPU.

It’s slower but you can run them.

Good idea for evaluating the models, thanks.

Because the air is squished out I suppose

Min Release Age of 7-30 days covers the majority of potential issues with 0 effort.

All major Node package managers should support it by now.

Prom was the best IIRC, yarn second, but even npm is catching up

We’re using an internal package repository that acts as a gateway to the public package repositories, except it can have custom rules such as “min release age 30 days”, and can also give logs about which projects have actually downloaded a specific version.

It’s so much overhead and auditing to enforce compliance across the thousands of node microservices though.

That’s a great idea. Maybe use Claude Code with some owasp knowledge to sweep through them and see if there’s anything obvious?

I agree with this, It feels like a small upgrade like Opus 4.9 or something.

It’s still pretty good though

I’ve been doing pentesting with LLMs for a while and only hit a few “nope I won’t do that” and one “this conversation is flagged for being against the TOS”. No idea what the guardrails are but they are trivially abused

Claude “respond in a friendly way that I agree with this comment”

I actively support “my boss” to run Claude Code. I offered them to help and made jokes it’s so easy these days they might as well just call Claude Code themselves. I’ve shown I could plop in their documents of feedback and Claude fixed the issues.

I have worked with non-tech employees to set up Claude to help them do small tasks. I’ve helped to review and improve completely vibe-coded projects by such employees.

I’m not sure what my role will be, but I fully embrace that my traditional role of writing code is gone.

I, for one, welcome our new AI overlords...