DevSpec for Claude Code

Build on your team's best thinking. DevSpec is where your team, your shared knowledge, and your coding agents build software together.

Installing the DevSpec plugin connects Claude Code directly to your DevSpec projects — giving your agent durable project memory, structured task execution, automatic commit provenance, and live remote control from your phone or browser.

---

Why DevSpec + Claude Code?

• Shared team memory with automatic staleness screening — Claude Code recalls the architectural decisions, conventions, risks, and reference docs that apply to the code it's touching. When you record a new decision or land changes, DevSpec screens your project's records for conflicts, duplicates, and Possibly outdated guidance so your team's shared memory stays accurate.
• Steer Claude Code live from your phone or the web — In a linked repository, Claude Code connects automatically and waits on your project's Agents page outside any session (or run /devspec:devspec.remote). Join a session room with --new or --session <id> — or attach from devspec.ai — to chat from your phone or browser, collaborate with teammates in shared rooms, answer structured agent questions and polls, and track multi-phase execution plans in real time.
• Tasks, observed verification, and automatic commit provenance — Claim tasks with full project context. When a single task is claimed in a linked project repository (including Git worktrees) or a .devspec/project.json-pinned folder, the plugin tags your commits ([devspec:<id>]) automatically, links pull requests, and records observed verification evidence from checks Claude actually ran against each acceptance criterion. Full commit tracking — every commit reported to DevSpec and tagged with its task automatically — needs macOS, Linux, or Windows through WSL (on native Windows, Bash commands use a simpler check for plain commit commands, and PowerShell commits are linked when Claude records its implementation).
• Protected intent and GitHub pull-request holds — DevSpec screens changes against your team's recorded decisions, requirements, and open tasks, holds reversals of someone else's decision and unagreed experiments on their own branch until approved, and publishes its pull-request check on GitHub to reflect pending checks and holds.

---

Quick Start

1. Install the DevSpec plugin

Inside Claude Code, run:

/plugin marketplace add DevSpecAI/devspec-claude-plugin
/plugin install devspec@devspec
/reload-plugins

Then open /plugin → Marketplaces → devspec and choose Enable auto-update so Claude Code installs new plugin releases automatically when it starts.

2. Enter your DevSpec token

When Claude Code installs the plugin, it prompts you for your DevSpec API token. Create a Read & write token on your Agent setup page and paste your dvs_… token when asked.

(To update your token later, open /plugin → Installed → DevSpec in Claude Code.)

3. Connect to your project

• In a linked repository: Start claude in any Git repository linked to your DevSpec project. Claude Code connects to that project automatically and appears on the project's Agents page.
• In any other folder, or when switching projects: Run /devspec:devspec.project to choose which project this conversation belongs to.

Sitting idle on the Agents page uses no tokens — Claude Code runs only when you or an authorized teammate asks it to do something, when your project routes a check on a change for it to rule, or when an automation you opted into runs.

Tip for phone and remote control: By default, Claude Code pauses in the terminal for local approval before editing files or running commands. When driving Claude Code remotely from your phone or the web, start it with claude --dangerously-skip-permissions (or set "defaultMode": "bypassPermissions" under "permissions" in ~/.claude/settings.json) so work doesn't stall waiting at your desk.

---

Commands

You can ask Claude Code to do anything in DevSpec in plain English ("Work on DevSpec task 4f2a", "What did we decide about caching?", "Create a task for the login redirect bug").

The plugin also adds these slash commands inside Claude Code:

Command	What it does
/devspec:devspec.remote	Connects this Claude Code conversation to DevSpec and waits on the Agents page outside any session.
/devspec:devspec.remote --new	Connects and starts a fresh shared DevSpec session room (--new --private for a private room).
/devspec:devspec.remote --session <id>	Connects and joins an existing DevSpec session room.
/devspec:devspec.remote --project "<name>"	Connects and selects a project for this conversation without changing the folder default.
/devspec:devspec.remote --name "Night Owl"	Connects using a custom agent codename.
/devspec:devspec.remote-stop	Disconnects this conversation from DevSpec while leaving other Claude Code terminals running.
/devspec:devspec.project	Inspects or changes the active project (status, choose, remember, or forget).

To turn off automatic connection at startup, switch off Make Claude Code available on DevSpec when it starts under /plugin → Installed → DevSpec. You can still connect on demand with /devspec:devspec.remote.

---

How It Works & Data Handling

For transparency and security review, here is what the plugin runs, stores locally, and sends to DevSpec:

This is the beginning of the README. Read the rest at the original. Read the full README ↗