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.
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.
Slack Lists provides task tracking inside Slack, including list items and configurable fields. Use Slack’s own guide if that is the destination you need. ghost’s workflow takes a request from Slack into Focus, where it can sit beside work from meetings, notes, and other sources. It does not claim to edit Slack Lists or keep Focus and Slack Lists synchronized. The original thread remains the place to inspect the request and surrounding discussion.
A request in a busy channel can disappear below new messages even though the work is still open. A Focus item gives it a title, brief, source, priority, and Kanban state. Related items can belong to an Epic so you can review the outcome as well as the individual actions. Keep Jira as the team system when the request belongs there; the Slack-to-Jira workflow covers that handoff. A personal follow-up can remain in Focus without pretending it is the same record as the team issue.
Ask ghost to read the surrounding conversation and look for an existing task before proposing another. Preserve the stated owner and timing, and leave missing information visible. “Before Friday’s review” should retain the meeting context; it should not become an invented clock time or guaranteed reminder. Moving an item to Done should reflect work that actually finished, not merely that a reply was drafted. Sending an update to Slack remains a separate action.
Illustrative Slack message and task; the people and project details are fictional.
This is one workflow across ghost, not a bundle of disconnected products. Each feature owns a specific stage and keeps its own access boundary.
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.
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.
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.
The handoff stays inspectable from source to result. Every stage names what it received, what changed, and what needs review.
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.
A direct request, promise, decision, unresolved question, FYI, and casual suggestion have different consequences. Only an actionable commitment should become a to-do candidate.
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.
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.
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.
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.
Connected work still needs accurate sources, explicit destinations, and review where an action changes another person’s system.
Yes. ghost can read the relevant supported Slack context, identify an actionable request, and propose a source-linked Focus item for review.
The workflow is designed to retain the source permalink or thread identity so the wording, participants, attachments, and surrounding decision remain available.
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.
Not automatically. ghost can prepare a draft, but posting the exact message is a separate operation that uses Slack’s Send/Deny approval gate.
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.
Bring the source, the intended result, and the boundaries that matter. ghost is in private beta for macOS.
Request access