margin
Home

Thought · shared

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.

What I noticed

I found 3 different posts in this.

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

  • I stopped manually preparing every development ticket

    Angle: Workflow automation

    How do you want to approach it?

    Your old routine, then the new one. · I'd go with this

    Before I write this, I'd like to understand it better.

    I'll ask rather than invent it · ⌘↵

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

    Angle: Contrarian / insight

  • AI should understand the task before writing code

    Angle: AI-assisted engineering

    Open draft