Bail-out protocol: always reflect FIRST, then clean up. All commands use absolute paths and git -C.
Inputs
WORKTREE: absolute path to current worktree (or primary if no worktree)
Optional reason string (if not provided, ask for one)
Steps
Detect current step by examining what exists:
What exists
Estimated step
Just an issue, no branch
Step 0 (Capture)
.branch-context.md, no worktree
Step 1 (Orient)
Worktree exists, no code changes
Step 2 (Isolate)
Plan file on branch
Step 3-4 (Design/Review)
Code changes committed
Step 5-7 (Build/Verify/Archive)
PR open on GitHub
Step 8 (Ship)
related skills
semantically similar in the cross-vendor index
don't have the plugin yet? install it then click "run inline in claude" again.
+clear input contract with absolute path requirement and optional reason string
+intelligent state detection via artifact inspection (branch-context.md, plan file, code changes) rather than asking user
+maps detected state to workflow step number, providing context for retrospective
weaknesses
~procedure section is a lookup table, not actionable steps - doesn't say what 'reflect' means, what github api calls happen, what 'clean up' entails
