For a long time, I've been talking with customers about what becomes possible when DevStride is more than the place where work is tracked — when it becomes the orchestration layer for the tools that actually deliver that work.
You've seen the pace and quality we can sustain by combining DevStride with Claude Code, Codex, and GitHub. Today, I'm releasing that same system directly to all of you as the DevStride plugin for Claude Code. My goal was to package the value in a form that is remarkably easy to adopt: install the plugin, connect your organization, let it learn your repository, and start with one real item.
The plugin ships seventeen skills that work together as one loop. They can shape a roadmap in DevStride, find the next unblocked item, create the right branch, build and review the change, open and merge the pull request, update the item, and continue through the release — while preserving the human approval points that matter.
Run these commands in Claude Code:
/plugin marketplace add devstride/claude-plugin
/plugin install devstride@devstride
Run /mcp, connect plugin:devstride:devstride, sign in, and deliberately choose the
organization whose live items the skills should use.
Open Claude Code in your repository and run:
/devstride:setup
Setup learns your real branches, package manager, test and type-check commands, GitHub Actions
shape, coding conventions, review tools, and DevStride work-item hierarchy. It asks about anything
it cannot prove, then writes and validates one repository file: .claude/ds-config.json.
That includes repositories whose branch names do not follow the old develop and master
convention. If you use names such as main, production, staging, canary, or test, setup
proposes branches that actually exist and asks whenever the names leave more than one plausible
answer.
Follow it with the read-only health check:
/devstride:doctor
Give the planning skill an existing DevStride parent item:
/devstride:plan I1234
It reads what is already there, works through scope and sequencing with you, and creates nothing until you approve the proposed plan.
/devstride:build-item
Start with one item so you can see the branch, build, review, test, merge, and DevStride update flow in your own repository. When it behaves the way you expect, let Claude Code walk the rest of the plan serially:
/loop /devstride:build-item
📚 Start with the installation guide · See the complete plugin overview · Understand the planning loop · Understand the delivery loop
/mcp. Changes to items,
comments, dates, status, and dependencies are immediately visible to your team. Start with one item,
and choose the organization deliberately.Unless you enabled marketplace auto-update, run both commands below and restart Claude Code:
claude plugin marketplace update devstride
claude plugin update devstride@devstride
The first refreshes the marketplace catalog; the second updates the installed plugin. Confirm that
Claude Code reports version 0.9.0 with claude plugin list.
I am genuinely excited to put this in your hands. DevStride has always been about turning plans into progress people can see. This release closes more of the distance between the plan and the work itself — and makes the delivery system we've been refining available to every team ready to try it.
2026-08-16
Create a DevStride account with the Google or Microsoft identity you already have — no password to invent, no invitation to wait for. Plus a reliability fix for organizations without a billing subscription.
2026-08-21
Log time at every level of the hierarchy: epics, features, and objectives can now carry their own time, and every surface shows an honest own-plus-descendants total.