Agentic Skills

Skill Audit

A compact reference for all seventeen skills shipped by the DevStride Claude Code plugin.

Skill Audit: All Seventeen Skills

Version 0.9.0 ships the seventeen skills below. They always invoke as /devstride:<name>, including when the plugin was installed through the shorter ds@devstride marketplace entry.

Planning

SkillInvocationWhat it does
plan/devstride:plan <parent-item> [description]Interactively shapes a grouping item → release unit → leaf roadmap, writes approved items and dependencies, rationalizes dates, and numbers the execution order. Reads the existing plan first.
comprehend-plan/devstride:comprehend-plan <item> [focus question]Reads the complete descendant tree, descriptions, comments, status, and dependencies. Strictly read-only.
insert-story/devstride:insert-story [parent-item] <description>Creates one Story and splices it into an existing plan’s dependency order. It does not build the code.
insert-defect/devstride:insert-defect [parent-item] <description>Creates and splices one Defect. It asks before moving an urgent defect ahead of the normal next item.
rationalize-gantt/devstride:rationalize-gantt <plan-root>Recomputes a synthetic one-day-per-leaf timeline and reviews invalid dependency edges. It overwrites selected dates and may remove or repoint edges.

Planning writes to the connected DevStride organization except for comprehend-plan. None of these skills writes repository code.

Delivery

SkillInvocationWhat it does
build-item`/devstride:build-item [itemnext
create-story/devstride:create-story <description>Creates, places, assigns, and delivers one standalone Story. No plan numbering or dependency splice.
create-defect/devstride:create-defect <description>Creates, places, assigns, and delivers one standalone Defect.
branch-feature/devstride:branch-feature <branch-name>Creates and pushes a feature branch from the resolved working base. Stops on a dirty tree.
branch-hotfix/devstride:branch-hotfix <branch-name>Creates a hotfix branch from a fresh production branch. It does not open the pull request.
ultracode-build/devstride:ultracode-build <item> <scope>Understands, implements, tests, commits, and adversarially reviews one item. It does not open or merge a pull request.
pr/devstride:pr [item]Opens the pull request, requests configured cloud reviewers, delegates review and CI settlement, runs matching local pre-ship checks, and optionally links the item.
review/devstride:review [PR#]Resolves the configured roster, verifies and settles findings, writes qualifying lessons, releases draft-held CI, and requires green at the final head commit. Also has local-only and pre-ship-resume modes for callers.
push/devstride:pushStages intended tracked and named new files, commits, runs configured typechecks, and pushes. It never opens a pull request.
release`/devstride:release [no docsskip docs

build-item chooses between two delivery shapes:

  • A planned leaf on a release-unit branch uses a local merge with no item pull request when fast merges are enabled. With fast merges disabled, it gets a pull request into that release-unit branch.
  • A one-off always targets the base branch and gets its own full pull-request path, even when filed under a release unit.

Setup and diagnostics

SkillInvocationWhat it does
setup`/devstride:setup [validateecosystem
doctor`/devstride:doctor [envplugin

Which command should I use?

SituationUse
No buildable roadmap existsplan
You need to understand a plan before changing itcomprehend-plan
New work belongs in a sequenced planinsert-story or insert-defect
New work is an unplanned, standalone requestcreate-story or create-defect
The item already exists and should shipbuild-item
A production fix must start from production codebranch-hotfix, then build and pr
The release source is ready for productionrelease
The loop behaves unexpectedlydoctor