Begin with an editable source note
The AI note taker can hold meeting context, research findings, project plans, browser evidence, and manual writing with the relevant sources attached.
Ghost can identify actions inside meeting notes, research briefs, planning documents, browser findings, and manually written notes, then propose structured Focus items without disconnecting them from the evidence.
An Atlas launch note contains three findings, one decision, and a request to verify the export path. Ghost proposes only the request as a task, keeps the launch note attached, and places it under the existing release Epic.
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 AI note taker can hold meeting context, research findings, project plans, browser evidence, and manual writing with the relevant sources attached.
The AI to-do list carries the concise action, priority, timing, status, source note, and Epic context through To Do, In Progress, and Done.
AI memory can help find the relevant note or earlier context. The note and current task record remain the places to verify the work now.
The handoff stays inspectable from source to result. Every stage names what it received, what changed, and what needs review.
The user selects the relevant note and identifies what kind of follow-through is expected. The workflow does not scan every note and turn every sentence into work.
Findings describe what is known. Decisions record what changed. Questions identify a gap. Only a concrete action or commitment should become a task candidate.
Ghost suggests a concise title, brief, owner, timing, priority, and project relationship using details present in the note. Missing information stays marked for review.
Before creating a duplicate, the workflow can compare the candidate with active Focus items or an existing Epic and update the relevant record when that is the better action.
The reviewed item moves onto the Kanban board, joins the right Epic, and retains a link to the source note so the reason behind the work remains available.
If the note changes or the task encounters a blocker, the user can return to the evidence, revise the brief, and keep the task status honest.
Connected work still needs accurate sources, explicit destinations, and review where an action changes another person’s system.
Meeting notes, research briefs, project plans, browser findings, email-derived notes, and manual notes can all contain actionable work. The selected note remains available as the source.
No. The workflow distinguishes findings, decisions, questions, and context from real actions. The user can review what should become a Focus item.
Yes. Retaining the source note is central to the workflow because it preserves the reason, evidence, and surrounding decision behind the task.
Yes. After review, related tasks can be grouped into an Epic and move through To Do, In Progress, and Done on the Focus board.
This page covers many note sources, including research and planning. The meeting workflow focuses specifically on transcript-grounded commitments, speakers, and meeting follow-through.
Bring the source, the intended result, and the boundaries that matter. Ghost is in private beta for macOS.
Request access