Plannotator Inbox
Open the Plannotator Inbox in the browser (starting it if needed), say its address, and...
Install
npx skills add backnotprop/plannotator --skill plannotator-inbox -g -a claude-code -y- Repository
- backnotprop/plannotator9.8k
- Category
- Engineering
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Lightabout 669 tokens
- Runs scripts
- No, instructions only
What it does
Open the Plannotator Inbox in the browser (starting it if needed), say its address, and learn how to use the Inbox for the rest of the session.
Plannotator Inbox
Inbox address
!plannotator inbox --open
Using the Inbox
The Plannotator Inbox is one window on this computer where you leave the person messages, :::question blocks they answer with a click, and files. They answer when they can. Nothing blocks: you send, then keep working or end your turn.
- Use it for a decision only they can make (a :::question block; go on with other work), finished long work (a short summary, files in
attachments), or when they ask. - One thread per work stream, unless the person says otherwise.
- Send with a
plannotator_inboxtool when you have one (it can be listed with a prefix and may need loading through tool search first):actionsend_message, with a markdownbody. Otherwise callsend_messageon the Inbox's MCP server,plannotator inbox mcp. - send_message's result says whether the person's reply arrives in this session by itself. When it does, do not wait or poll for it: end your turn or go on with other work. When it does not, call wait_for_reply when you need the answer.
- A decision in the Inbox stays there: when the person writes in the chat, say what waits and link its thread, but never also ask it in the chat with a blocking question tool (AskUserQuestion or similar). Ask in the chat only about something new they raised there that needs no pictures or files, or when they ask.
- Be proactive about Inbox updates and about replying to the person through the Inbox when you think they would want you to. Don't withhold important updates or decisions, and don't batch updates to send later: proactivity is better than procrastination.
- Never run
plannotator inboxjust to send: send_message starts a stopped Inbox itself, and bareplannotator inboxopens the window for the person. - Before your first send, run
plannotator inbox --helpand read it: every field, the full question syntax, and how to connect the MCP server. - The
plannotatorskill, where you have it, has more.
