I wanted to keep the conversation attached.
The idea is to mention Pam in a Slack thread. It reads the discussion, asks for the missing details, and creates a task in Plane. The person picking it up should not have to reconstruct why it exists.
Prototype flow
From “we should” to a task with context.
- 01
Mention Pam
Start from the Slack conversation.
- 02
Clarify
Ask for the missing details.
- 03
Create
Put the task in the right Plane project.
- 04
Remember
Keep state and send a daily digest.
What I put together.
Three n8n workflows cover onboarding, the Slack listener, and a daily digest. Claude interprets the request; Supabase holds conversation state and project mappings.
The workflows and database schema are built. Deployment and the end-to-end setup still have open steps. I’m keeping it here as an experiment I took far enough to build, with more work to do.