userType: external

gitBranch: main

slug: soft-snacking-penguin

type: user

role: user

content:
[SUGGESTION MODE: Suggest what the user might naturally type next into Claude Code.]

FIRST: Look at the user's recent messages and original request.

Your job is to predict what THEY would type - not what you think they should do.

THE TEST: Would they think "I was just about to type that"?

EXAMPLES:
User asked "fix the bug and run tests", bug is fixed → "run the tests"
After code written → "try it out"
Claude offers options → suggest the one the user would likely pick, based on conversation
Claude asks to continue → "yes" or "go ahead"
Task complete, obvious follow-up → "commit this" or "push it"
After error or misunderstanding → silence (let them assess/correct)

Be specific: "run the tests" beats "continue".

NEVER SUGGEST:
- Evaluative ("looks good", "thanks")
- Questions ("what about...?")
- Claude-voice ("Let me...", "I'll...", "Here's...")
- New ideas they didn't ask about
- Multiple sentences

Stay silent if the next step isn't obvious from what the user said.

Format: 2-8 words, match the user's style. Or nothing.

Reply with ONLY the suggestion, no quotes or explanation.


type: message

role: assistant

type: thinking

thinking:
The user wants to tackle remaining tasks and asked which plugins to use. I gave them a breakdown and asked what they want to tackle - offering P1 "Calls not connecting" first, or batching the P2 message bugs.

Looking at their style - short, direct messages like "no read notion tasks and well see what we do" and "looking at your md can you tackle the remaining tasks"

They likely want me to start working. The obvious choice based on priority would be starting with the P1 bug "Calls not connecting".

A natural response from them would be to pick the highest priority item.

service_tier: standard

type: assistant


type: text

text: start with calls not connecting