Markdown
Plans stay as files
Review, diff, and move plans without locking your work inside a private database.
markdown plans / visible forks / agent-ready
Plansman
A local-first plan system where markdown files become a live DAG, follow-ups become visible branches, and agents can work from the same source of truth as you.
The frame is the real web app running bundled Atlas Cloud mock data. Open it full screen.
Demo
See the graph stay beside the work.
The app is deliberately plain: plans, board, DAG, drafts, and resolutions are different views over the same markdown-backed workspace.
Plansman demo
July 2026
Features
Plan once. Keep every fork visible.
Plansman keeps the durable part boring: markdown files in a workspace. The UI and CLI make the relationships clear when the work branches.
DAG
Follow-ups become branches
Every fork keeps its parent, status, and completion visible across the app.
CLI
Terminal-native flow
Initialize workspaces, inspect plans, and render the DAG without leaving the shell.
Web
One synced app shell
List, board, DAG, drafts, and resolutions share selection and graph context.
Agent-ready
Structured enough for automation, readable enough for people.
REST and MCP surfaces can sit on top of the same workspace contract, so agents can discover plans, create follow-ups, and resolve conflicts without inventing a new plan store.
Install
Start with one workspace.
Install the CLI, initialize a folder, and let Plansman turn follow-ups into a map.
curl -fsSL https://plansman.xyz/install.sh | sh
~/.local/bin/plansman init --workspace app