Read the relevant Slack context
The Slack integration can search messages, read available channel history, keep thread-level facts attached to their source, and draft a response in the user’s learned Slack style when that guidance is available.
Turn Slack messages into a to-do list that keeps the thread.
Ghost can search or read the relevant Slack conversation, distinguish a real request from discussion, and propose a Focus item that keeps the source permalink, stated details, and project context ready for review.
- Direct answer
- A Slack to-do list workflow turns actionable requests and commitments in Slack into trackable tasks without losing the original thread. Ghost can identify the action, retain the source permalink, propose an owner and timing only when stated, place the work in Focus or an Epic, and help follow through later.
One complete example.
In the Atlas launch channel, Maya asks Ahmed to send the readiness brief before Friday’s review. Ghost reads the surrounding thread, proposes “Send Maya the readiness brief,” keeps the Slack permalink attached, and places it in the Atlas launch Epic after review.
Where each capability enters.
This is one workflow across Ghost, not a bundle of disconnected products. Each feature owns a specific stage and keeps its own access boundary.
Move confirmed work into Focus
The AI to-do list gives the approved action a priority, timing label, Kanban status, source, ready-to-start brief, and optional Epic so both the task and the larger outcome remain visible.
Return to work that is still open
A configured Heartbeat can bring an unfinished item or relevant thread back when current context makes it useful. A Focus timing label alone is not a guaranteed Slack notification or scheduled run.
How the work moves.
The handoff stays inspectable from source to result. Every stage names what it received, what changed, and what needs review.
Find the intended Slack conversation
Ghost identifies the correct workspace, channel, message, or thread before extracting anything. Broad requests use Slack search; specific recent conversations can use available channel history and verified source permalinks.
Separate a task from discussion
A direct request, promise, decision, unresolved question, FYI, and casual suggestion have different consequences. Only an actionable commitment should become a to-do candidate.
Carry over stated task details
The proposed title, owner, due timing, priority, and project relationship come from the source thread and current work context. Missing details remain visible for review rather than being filled with a plausible guess.
Check the existing Focus board
Ghost can look for a matching task or Epic before creating a duplicate. The item can join To Do, In Progress, or an existing outcome while retaining the original Slack source.
Prepare the response separately
Creating a to-do does not post to Slack. Ghost can draft a short acknowledgment or status update, but the exact message enters the Slack Send/Deny approval path before it is sent.
Follow the work into completion
The task can move across the Kanban board, reopen its source thread, and feed a daily briefing or Heartbeat check. Team engineering work can continue through Jira issue preparation when that external record is appropriate.
What the workflow does not assume.
Connected work still needs accurate sources, explicit destinations, and review where an action changes another person’s system.
- Connecting Slack does not authorize Ghost to monitor every channel, read unavailable private conversations, or treat every message as an instruction.
- Ghost should not invent an owner, deadline, or commitment that the Slack thread does not support.
- Creating an internal Focus task, posting a Slack message, and creating or changing a Jira issue are separate actions.
Questions about slack to-do list.
Can Ghost turn a Slack message into a to-do?
Yes. Ghost can read the relevant supported Slack context, identify an actionable request, and propose a source-linked Focus item for review.
Does the task keep a link to the original Slack thread?
The workflow is designed to retain the source permalink or thread identity so the wording, participants, attachments, and surrounding decision remain available.
Can Ghost find tasks across several Slack channels?
Slack search can help locate relevant messages within the connected workspace and granted scopes. The workflow should stay tied to the requested subject rather than treating the whole workspace as an automatic task feed.
Does Ghost reply in Slack after creating the task?
Not automatically. Ghost can prepare a draft, but posting the exact message is a separate operation that uses Slack’s Send/Deny approval gate.
Can Slack tasks be grouped into Epics and a Kanban board?
Yes. Reviewed items can join a Ghost Epic and move through To Do, In Progress, and Done in Focus while the original Slack context stays attached.
Start with one real workflow.
Bring the source, the intended result, and the boundaries that matter. Ghost is in private beta for macOS.
Request access