Specboard is an integrated documentation and planning platform. It combines a Git-backed markdown editor with a lightweight task manager, designed for teams that want their specs and tasks to live together.
A collaborative markdown editor built for technical documentation:
- WYSIWYG and raw markdown modes — switch between rich editing and direct markdown
- Inline comments — Google Docs-style margin comments with reply threads
- AI assistance — sidebar chat powered by Anthropic Claude and Google Gemini for writing help
- Git-backed storage — documents are markdown files in a GitHub repository, with full version history
- Real-time sync — edit in the browser, commit back to GitHub with conflict detection
A kanban-style task manager with document integration:
- Epic/task hierarchy — organize work into epics with nested tasks
- Three-column board — drag-and-drop between status columns
- Document linking — connect specs to the epics and tasks they describe
- MCP integration — AI coding assistants (Claude Code) can read and update tasks via the Model Context Protocol
Specboard runs as a web application backed by AWS services. Users sign in, connect their GitHub repositories, and get a synced workspace where they can edit documents and manage tasks. Changes are stored in the cloud and can be committed back to GitHub.
For AI-assisted development workflows, the MCP server exposes planning data to tools like Claude Code, allowing AI agents to check current work, update task status, and read specs — creating a feedback loop between documentation, planning, and implementation.
Specboard ships with a /whats-next command for Claude Code that connects your AI coding sessions to your planning board. It queries Specboard's MCP server to show current work, suggest what to pick up next, and manage the full development lifecycle — from scoping to PR.
1. Register the Specboard MCP server:
claude mcp add specboard --url https://specboard.io/mcpThe OAuth flow will handle authentication automatically.
2. Install the /whats-next command and helper script:
# From the specboard repo root
mkdir -p ~/.claude/commands ~/.claude/scripts
ln -sf "$(pwd)/tools/whats-next.md" ~/.claude/commands/whats-next.md
ln -sf "$(pwd)/tools/assess-git-state.sh" ~/.claude/scripts/assess-git-state.sh3. Add MCP tool permissions to your Claude Code settings (global or per-project .claude/settings.local.json):
{
"permissions": {
"allow": [
"Skill(whats-next)",
"Bash(bash ~/.claude/scripts/assess-git-state.sh)",
"mcp__specboard__list_projects",
"mcp__specboard__get_items",
"mcp__specboard__create_item",
"mcp__specboard__create_items",
"mcp__specboard__update_item",
"mcp__specboard__delete_item"
]
}
}From any project directory in Claude Code:
/whats-next
This will:
- Query your Specboard projects via MCP
- Check local git state (branches, worktrees, PRs)
- Cross-reference to identify active, paused, and available work
- Recommend what to work on next
During a session, Claude uses the Specboard MCP tools to track progress — starting tasks, adding notes on completion, linking branches, and signaling PRs for review.
| Tool | Description |
|---|---|
list_projects |
Discover your projects and their IDs |
get_items |
Query items with filtering by status, type, search; optional task/note includes |
create_item |
Create an epic, chore, bug, or task |
create_items |
Bulk create tasks under a work item |
update_item |
Update status, sub-status, branch, notes, etc. |
delete_item |
Delete a work item or task |
| Document | Description |
|---|---|
| Architecture | System design, infrastructure, and monorepo structure |
| Setup Guide | Local development environment setup |
| Tech Stack | Technology choices, coding standards, and conventions |
Detailed feature specifications live in docs/specs/.
Specboard runs entirely in Docker. No local Node.js installation required.
# Clone and start
git clone https://github.com/kcjonson/specboard.git
cd specboard
docker compose up
# Open in browser
open http://localhostSee the Setup Guide for full instructions including local overrides and database access.
Private — not currently open source.