markdown plans / visible forks / resolved conflicts

Plansman

A centralized plan system for humans and agents. Markdown files become a navigable DAG, follow-ups become forks, and conflicting threads resolve in one place before they drift.

Download CLI Watch demo See the model plansman dag --workspace app
Files stay plain. The structure becomes the map. CLI / REST / MCP / Web UI
The model

One folder of plans. Every follow-up keeps its place on the graph.

Plansman is built around real planning behavior: start with a plan, execute it, fork the next necessary follow-up, and keep the whole lineage visible instead of losing it in a chat thread.

1 init

Create a workspace

Give agents and humans the same markdown-backed planning home.

plansman init --workspace app
ResultCreates workspace metadata, plan folders, and resolution storage.
2 plan

Write plans as files

Folder structure acts as categories; markdown remains easy to diff and review.

plans/
  platform/
    plan-12.md
  launch/
    plan-13.md
ResultA durable corpus that works without a proprietary database.
3 fork

Follow up without wandering

When execution reveals another task, mark it as a follow-up instead of changing the main path.

follow_up: plan-12
ResultThe branch appears on the DAG and keeps its parent context.
Why it works

The plan graph is always visible.

Plansman makes the cost of a detour visible. You can inspect where a card sits in the tree, keep a DAG pane open beside the work, and see whether a new idea is on the main path or a fork that should wait.

Root planstarts the spine
Follow-upcreates a visible fork
Selectionsyncs list, board, and DAG
Resolutionmerges decisions back
Plansman DAG view with a visible follow-up graph and right-side DAG pane
DAG-first planning root -> follow_up -> fork -> decision -> plan update
Surfaces

Same workspace, four ways in.

The markdown corpus is the center. The web UI helps you navigate it, the CLI keeps it fast, REST connects product surfaces, and MCP gives agents a structured way to read and write plans.

CLI

Operate from the terminal

Initialize, list, inspect DAGs, and open resolutions without leaving the repo.

REST

Expose the plan system

Back app screens and automation with the same workspace operations.

MCP

Give agents a contract

Agents can discover, update, and resolve plans through structured tools.

Web

See the work clearly

Plans, board, DAG, drafts, and resolutions stay synced in one app shell.

CLI DAG

The branch graph works in a terminal too.

plansman dag renders the same follow-up lineage as the web view: branch filters, colored paths, status, completion, and parent relationships, all without leaving the shell. 

plansman dag --workspace atlas-cloud-demo
Plansman CLI rendering a colored DAG diagram in a terminal
Product proof

Built for the moment when plans start branching.

The interface keeps the graph beside the work, so the current plan, its parent, and its follow-up branches are not abstract metadata. They are visible while you decide what to do next.

Plansman plan list with a persistent DAG position pane

List view with DAG context

Select a plan and keep its graph position visible while scanning the backlog.

Plansman kanban board with synchronized DAG pane

Board view for execution

Move through running, waiting, and done plans without losing branch context.

Plansman DAG page showing branch filters and a full graph

DAG view for lineage

Filter a branch, inspect forks, and see where follow-ups came from.

Video demo

Watch the plan graph move through the real product.

The walkthrough shows how markdown plans become list rows, board cards, a DAG position pane, and a resolution centre without losing the file-backed source of truth.

Prefer a full tab? Open the demo video on X.

Live demo

Open a mock workspace without installing anything.

This is the real Plansman web app running against bundled Atlas Cloud demo data. Inspect plans, board columns, DAG forks, resolutions, and section notes without connecting a local workspace.

If the frame feels cramped, open the demo in a new tab.

Resolution center

When planning threads conflict, resolve once and stitch the decision back.

Multiple agents can work on different plans and still share one conflict path. Plansman gives the disagreement a file, collects positions, records a decision, then updates the affected plans so the corpus stops contradicting itself.

Open the conflict

Capture which plans disagree, who is involved, and what needs a decision.

plan-9 main plan-26 branch RES-42 open 
plansman resolutions open \
  --title "Lifecycle naming" \
  --plans plan-9,plan-26 \
  --party agent-a

Decide and merge back

The resolution becomes the place where a decision is accepted and reflected into the plans.

positions recorded decision accepted plans updated 
plansman resolutions decide 42 \
  --status agreed \
  --decision "Use soft-delete and restore"
Download

Start with one plan. Let the system show you when it forks.

Install Plansman CLI to keep planning practical: markdown in folders, visible DAG lineage, and a resolution center for the decisions that would otherwise scatter across threads. 

curl -fsSL https://plansman.xyz/install.sh | sh
plansman init --workspace app
Latest release Back to top plansman init --workspace app