Procedure name:

When it's used:

Current approach:

Pain points:
@claude tag approach has limitations such as inability to edit workflow files. it's also newer. we have gotten much more value historically out of /close-issue however close issue comes with its own tradeoffs in terms of worktree setup and teardown

Suggested improvements:
@claude tag method should have a name and we should be able to document our actual useage of the two methods contrasting comparing and iterating and ultimately both methods should get better, be audited, and apply verisikning mindset to them
Related procedures:
there are two related procedures the close-issue prociedure done in tmux locally and git worktrees and the making github issue and having it auto comment to have claude close it.

Ghost procedure?
no this is a new procedure we are getting ahead ealry and documetning it

Duplication:
Currently every time an issue is created, claude will start to implement it. even it its incomplete and shouldnt be worked on yet. thus if we use the shall we say traditional close-issue command to implement a github issue, by the wtime its done we will likely have two PRs, the one started when trigerred by the comment that was auto created and the one we create locally. not a huge waste, but still.