executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
asking-the-userUse when a decision is the user's to make (which option, which target, go or stop), when a question has a handful of answers rather than a conversation, or when the user is watching the board rather than the chat. Asks on the stickypane board with a form that has buttons, waits for the press, and reads the answer back.
Independent GitHub snapshot · Automated classification · Original documentation governs
# 1. write .sticky/deploy.md (below), then
stickypane show deploy
# 2. wait for a button, always with a limit
stickypane wait deploy --timeout 10m
The form:
---
type: form
title: Deploy now?
---
The build is green. Where should it go?
## Target
- ( ) staging
Try it there first.
- ( ) production
## Also
- [ ] run migrations
## Note
>
[ Deploy ] [ Cancel ]
| Line | Is |
|---|---|
- ( ) text | one choice among the options under the same heading |
- [ ] text | any number of choices |
| indented line under an option | what choosing it means |
> | a line the user types into |
[ Label ] [ Label ] | the buttons; a form without any gets [ Submit ] |
wait prints one line per question:
submitted: Deploy
at: 2026-10-02T14:03:05+09:00
Target: production
Also: run migrations
Note: after lunch
--json gives {"submitted":true,"button":"Deploy","answers":[...]}. Exit
code 3: the time ran out and nothing is printed. Exit code 1: the note is
not a form or is not there. stickypane answers deploy prints the same now,
without waiting (submitted: no until a button is pressed).
Report the answer in one line; acting on it is the caller's job. Then
stickypane hide deploy, or leave the form as the record of the decision.
[ Deploy ] [ Cancel ]), never [ OK ].submitted keys; a form that
still has them answers at once with the old choice.talking-in-chat.${CLAUDE_PLUGIN_ROOT}/rules/touching-the-board.md applies.