Roadmap Skill

AI-readable docs: llms.txt · llms-full.txt · Architecture · Tool Interface Standard

What Makes It Different

Shared context — Chat with your Agent to plan tasks, or edit directly in the Kanban — both stay in sync. Your Agent always sees the latest state.

Agent-native — Built as an MCP server. Your AI can create, update, and query tasks directly in conversation.

Visual workspace — Open localhost:7860 when you feel like it, or ask your Agent to open it with open_web_interface. Kanban for status, Graph View for sequencing. Or just stay in chat. All three work.

Local-first — Your data lives on your machine. No accounts, no cloud sync, no vendor lock-in.

Related MCP server: crunchy-work

New in v0.3.0: Graph View

Graph View is one of the headline features in v0.3.0.

Kanban is great for tracking status. Graph View is for understanding execution order.

It helps you and your Agent answer questions like:

• What has to happen first?

• Which tasks are ready right now?

• What is blocked by unfinished work?

• Which dependency should be added, reversed, or removed?

Instead of treating roadmap tasks as a flat list, Graph View turns them into a visual dependency map with node connections, ready/done states, detailed task cards, and export support. It is designed for planning sessions where sequencing matters just as much as status.

If you are using Roadmap Skill as an MCP workspace, this is the view that makes agent-assisted planning feel concrete: your Agent can build and update dependency graphs in chat, and you can immediately inspect the structure visually in the web UI.

Quick Start (Zero Config)

# Integrate with your AI assistant (MCP config below)

claude mcp add roadmap "npx -y roadmap-skill"

{
  "mcpServers": {
    "roadmap": {
      "command": "npx",
      "args": ["-y", "roadmap-skill"]
    }
  }
}

/mcp add

Or edit ~/.copilot/mcp-config.json:

{
  "mcpServers": {
    "roadmap": {
      "type": "local",
      "command": "npx",
      "args": ["-y", "roadmap-skill"]
    }
  }
}

{
  "mcpServers": {
    "roadmap": {
      "command": "npx",
      "args": ["-y", "roadmap-skill"]
    }
  }
}

Install Cline plugin, then add to cline_mcp_settings.json:

{
  "mcpServers": {
    "roadmap": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "roadmap-skill"]
    }
  }
}

{
  "mcpServers": {
    "roadmap": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "roadmap-skill"]
    }
  }
}

Edit ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "roadmap": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "roadmap-skill"
      ],
      "enabled": true
    }
  }
}

Go to Settings -> MCP -> Add new MCP Server:

{
  "mcpServers": {
    "roadmap": {
      "command": "npx",
      "args": ["-y", "roadmap-skill"]
    }
  }
}

{
  "mcp": {
    "servers": {
      "roadmap": {
        "command": "npx",
        "args": ["-y", "roadmap-skill"]
      }
    }
  }
}

Follow Windsurf MCP documentation and use:

{
  "mcpServers": {
    "roadmap": {
      "command": "npx",
      "args": ["-y", "roadmap-skill"]
    }
  }
}

{
  "context_servers": {
    "roadmap": {
      "command": {
        "path": "npx",
        "args": ["-y", "roadmap-skill"]
      }
    }
  }
}

One-liner (recommended):

codex mcp add roadmap -- npx -y roadmap-skill

Manual config — edit ~/.codex/config.toml:

[mcp_servers.roadmap]
command = "npx"
args = ["-y", "roadmap-skill"]

Windows: No cmd /c wrapper needed — Codex handles the subprocess directly.

Server name: Must match ^[a-zA-Z0-9_-]+$. Names with spaces or parentheses are rejected.

Note: Both Codex CLI and the Codex VSCode extension share the same ~/.codex/config.toml. A syntax error breaks both.

After setup, simply tell your AI:

"Create a website redesign project with tasks for homepage, about page, and contact form"

The AI will immediately create the project and tasks, saving them to local storage. You can open http://localhost:7860 anytime to view the visual Kanban board.

Agent Skills

This repository includes installable skills under skills/, distributed through the git repository rather than the published npm package.

Available skills:

• skills/roadmap/ - lightweight background and routing for roadmap-skill

• skills/roadmap-task-flow/ - capture, enrich, tag, and prioritize roadmap tasks

• skills/roadmap-planning-views/ - build focused planning graphs from task subsets

• skills/roadmap-web-visualization/ - open and use the local roadmap web workspace

Recommended installation pattern for skill-aware tools:

# install from the git repository when the installer supports repo sources
npx skills add shiquda/roadmap-skill

These skills are still in beta. If you run into issues or have suggestions, feedback is very welcome.

Who Is This For?

Solo developers, AI power users, and vibe coders who want their Agent to be a real collaborator — not just a code generator.

Typical Use Cases

1. Capture Ideas Without Breaking Flow

Mid-session, something pops into your head:

"Note this down: switch the auth module to JWT + refresh token rotation"

Use /quick-capture or just say "help me note this down" — your Agent turns it into a task, saves it locally, and you keep going. No context switch, no forgotten ideas.

2. Let Agent Help You Prioritize

"This month's OKR is finishing the user system refactor — can you list the related tasks and figure out which ones should come first?"

Use /auto-prioritize to let your Agent analyze the current project state and reorder task priorities accordingly.

3. Let Agent Recommend What to Do Next

"What's left on the current project? Any high-priority tasks I haven't touched yet?"

Or use /suggest-tasks — your Agent recommends the next actions based on current progress and priorities.

No tab switching. No copy-pasting. Just ask

Core Features

Supported Platforms

• ✅ Claude Code, Codex, OpenCode — Command-line AI assistants

• ✅ Cursor, VS Code — AI-powered IDEs

• ✅ Any MCP Client — Standard MCP protocol support

Data Storage

Roadmap Skill uses pure local JSON file storage. All data is saved in your user directory:

You can export or import backup files from the web interface.

License

MIT © shiquda