The devstride Claude Code plugin turns a DevStride roadmap into a delivery loop: plan the work, select the next unblocked item, branch, build, review, merge, update the item, and continue.
Version 0.9.0 ships seventeen skills. The source and release history live in devstride/claude-plugin.
/devstride:setup in your repository./devstride:doctor to catch missing tools, authentication, or CI wiring./devstride:plan I1234./devstride:build-item.Run one item before using /loop /devstride:build-item to walk the whole plan.
The skills use three roles instead of assuming your work-type names:
/devstride:setup maps your organization’s real work types to those roles and records repository-specific settings in .claude/ds-config.json.
| Item path | What happens |
|---|---|
| Planned leaf on a release-unit branch, fast merges enabled | Local review and local checks, then a local merge. No item pull request. Cloud review and CI run on the completed release unit. |
| Planned leaf on a release-unit branch, fast merges disabled | The item gets a pull request into the release-unit branch. |
| Planned leaf with release-unit branches disabled or no release-unit ancestor | The item gets a pull request into the repository’s base branch. |
One-off created with create-story or create-defect | The item always gets its own pull request into the base branch, even if it was filed under a release unit. |
The distinction matters: a one-off uses an explicit base-branch bypass. It is not safe to infer that one-offs have no release-unit ancestor, because the create skills allow them to be filed under one.
In the shipped draft-hold configuration, pull requests open as drafts. Local and cloud reviewers settle first; marking the pull request ready releases CI on the final reviewed diff.
That ordering depends on your GitHub Actions workflows listening for ready_for_review and declining to run their gated jobs while the pull request is a draft. Repositories that configure all three draft-hold settings as false intentionally run CI alongside review instead. /devstride:setup detects the current shape, and /devstride:doctor reports mismatches without editing a workflow.
Planning therefore asks for sign-off before creating a hierarchy. rationalize-gantt separately confirms scope because it overwrites stored dates and may remove or repoint dependency edges.
Code changes keep the normal git safety net: branches, diffs, review, tests, and merge history.
/devstride:release prepares the production pull request, review, configured local pre-ship checks, CI, and the optional documentation update. It then stops for explicit owner approval before merging the configured release source into the production branch.| Goal | Command |
|---|---|
| Check the installation and repository | /devstride:doctor |
| Understand an existing plan without changing it | /devstride:comprehend-plan I1234 |
| Create or extend a roadmap | /devstride:plan I1234 |
| Add one item to an existing plan | /devstride:insert-story ... or /devstride:insert-defect ... |
| Deliver the next planned item | /devstride:build-item |
| Create and deliver unplanned work once | /devstride:create-story ... or /devstride:create-defect ... |
| Promote the release source to production | /devstride:release |
/devstride:setup reads, writes, and validatesMaintenance & Codebase Checks
Codebase wiring audits, event-system delivery and topology checks, data cleanup and repair scripts, operational toggles, and historical one-off migrations available via ds script.
Getting the Skills
Install DevStride for Claude Code, connect it to your organization, set up a repository, and run your first plan and build.