Set up harness

/implement carries a ticket through review to merge. Three things around it are properties of the repository rather than of the skill:

• Repository hooks — behavior invoked by agent and Git events
• Merge automation — what merges a pull request once its conditions hold, so the agent never merges its own work
• Worktree cleanup — what a repository releases when a merged worktree goes away

This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write. The configuration is the working files themselves; this skill writes no documentation describing them.

Process

1. Explore