Thought · shared yesterday

Claude Code plugin

You shared

Recently I built a Claude Code plugin that can take a task number, fetch the ticket, check the repository to see what's already there, and plan the work before writing anything. It also updates the task status when it's done and can point out blockers before implementation starts. Honestly the planning part is more useful than the coding part.

What I understood

Your main point

“Honestly the planning part is more useful than the coding part.”

Details worth keeping

“It can take a task number, fetch the ticket, check the repository to see what's already there, and plan the work before writing anything.”
“It can point out blockers before implementation starts.”

I'll ask before I write anything I don't know.

I found 3 different posts in this.

They overlap, so I'd write one now and keep the others for later.

There's a potentially strong post here.

You mentioned that your plugin can identify blockers before implementation.

Did it ever find something that you would otherwise have missed?

I'll ask rather than invent it · ⌘↵

I stopped manually preparing every development ticket
Angle: Workflow automation
MarginWhy it could work
Before/after workflow posts are easy to relate to. Most engineers know the ticket-prep routine you described, so they'll recognise themselves in it.
The best thing my AI plugin does isn't writing code
Angle: Contrarian / insight
MarginWhy it could work
It goes against the usual “AI writes my code” story — and it's grounded in your own tool, so it reads as experience, not a hot take.
AI should understand the task before writing code
Angle: AI-assisted engineering
Open draft
MarginWhy it could work
It comes from something you actually built, and it supports the positioning you want around AI-era software engineering.

You shared

What I understood

What I noticed

I stopped manually preparing every development ticket

The best thing my AI plugin does isn't writing code

AI should understand the task before writing code