PHANTOM v4.0.0 DOCS
Website GitHub

Features

Phantom is a local-first PM mission system. It helps product teams turn requests from chat, docs, and code into context-aware missions, PM artifacts, approvals, and publish flows.

Current release truth from the runtime capability manifest:

  • 32 capability contracts tracked in code
  • 8 GA-ready
  • 2 working, not GA
  • 22 partial
SurfaceCurrent stateIncludes
Mission cockpitWorking, not GAOrchestrated missions, provenance, approvals, artifact readiness, publish targets, and legacy history
PM dashboardPartialInterviews, feedback, analytics, discovery, and browser-capture intake wired to live APIs, but still heuristic in key areas
Context + memoryGAFile ingestion, memory files, memory graph, context export, and support bundle export
PM artifactsPartialPRD, story, sprint, and spec generation with provenance and readiness-aware validation, but fallback-heavy
ChannelsPartialSlack, Telegram, and WhatsApp mission control with diagnostics and operator allowlists, but more lifecycle hardening is still needed
Workspace syncPartialGitHub, Notion, Linear, Figma, and Jira publish flows with reflected mission status, but broader real-world verification is still in progress
RuntimeWorking, not GAphantom boot, phantom server, and MCP access for editors and tools

Working Now

  • Mission cockpit: orchestrated missions, provenance, approvals, artifact readiness, publish targets, and legacy history.
  • Dashboard PM surfaces: interviews, feedback, analytics, discovery, and browser-capture intake are wired to live server APIs, but several remain heuristic or thin.
  • Context and memory: file ingestion, memory files, memory graph, context export, and support bundle export.
  • PM artifacts: PRD, story, sprint, and spec generation with provenance, fallback metadata, and readiness-aware validation.
  • Channels: Slack, Telegram, and WhatsApp mission control with diagnostics and operator allowlists.
  • Workspace sync: GitHub, Notion, Linear, Figma, and Jira publish flows with reflected mission sync status.
  • Local-first runtime: phantom boot, phantom server, and editor access through MCP.

Prototype Surfaces Not Counted As Shipped Product

  • Voice interface: WisprFlow remains a prototype stub and is not part of the shipped public runtime.
  • Distributed agent bus: the local AgentProtocol helper is internal-only and not a real cross-process transport.

Useful Commands

phantom capabilities
phantom mission run "Ship PM approvals in WhatsApp" --publish github
phantom context add .
phantom doctor

Capability labels in the CLI and UI are generated from the codebase and should be treated as the source of truth. Treat the technical-spec section as design/reference material, not a release-status page.