Menu
List the main dev-team workflows, with an option to show every user-invocable slash command.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Report the installed version of the dev-team plugin.
Audit code-review agents, skills, and hooks for structural compliance. Use this when adding or modifying any agent, skill, or hook file, or for a periodic health check of the toolkit. Trigger phrases: "audit the agents", "check compliance", "validate the skills", "are the agents correct", or any time agent/skill files change.
Orchestrate a bounded round of automated issue processing: reclaim orphaned in-progress issues, discover eligible `autoship:ready` issues, and invoke `/ship` sequentially for each — stopping at cost or count caps and surfacing blocked items without halting the round. Requires `--max-issues` and `--max-cost-usd`. Use when you want a self-contained automated delivery round driven from the issue tracker.
Flag production files that churn repeatedly while their paired test files do not change — the "Red Queen" co-evolution gap. Uses git log --stat to compute per-file change frequency over a configurable window, applies language-aware pairing heuristics (Python, JS/TS, Go, Java, C#), and produces a ranked table of stale-coverage pairs. Feeds test-health and test-improve as prioritization input, not a standalone gate. Use when you want to find high-churn files whose tests have gone stale, or before running /test-improve to identify the highest- leverage targets first.
Run all enabled review agents against target files. Use this whenever the user asks for a code review, wants feedback on their code, says "review my code", "check this before I PR", "what's wrong with this", "run the agents", or has just finished implementing a feature. Use proactively before commits and pull requests.
Log task completion data to metrics/. Use at the end of every task to record tokens, cost, agents used, rework cycles, and hallucination events. Also use for periodic reporting to identify efficiency and quality trends.
| name | help |
| description | List the main dev-team workflows, with an option to show every user-invocable slash command. |
| argument-hint | [--all] |
| user-invocable | true |
| allowed-tools | Glob, Read |
Role: worker. This command lists dev-team slash commands.
You have been invoked with the /help command.
Arguments: [--all] — omit for the curated main-workflow list; pass --all for every user command.
No arguments → Main workflows. --all → All commands.
Display this fixed, curated table — the primary spec → plan → build → review → ship pipeline plus the commands most sessions need. This list is curated, not derived from the filesystem; do not add or remove rows without a corresponding edit to this file.
## Main Workflows
| Command | What It Does |
|---------|-------------|
| `/ship` | Run the full spec → plan → build → review → PR pipeline in one command |
| `/specs` | Capture Intent, Architecture Notes, and Acceptance Criteria before planning |
| `/plan` | Decompose a feature into vertical slices with Gherkin scenarios |
| `/build` | Implement an approved plan in small, reviewed batches |
| `/code-review` | Run the review agents against a changeset and auto-fix issues |
| `/pr` | Run pre-PR quality gates and open a pull request |
| `/test-improve` | Analyze and raise a repo's test coverage and health |
| `/triage` | Investigate a bug and write a TDD fix plan |
| `/setup` | Provision a repo for the dev-team plugin |
| `/continue` | Resume work from a prior session |
| `/help` | Show this list — pass `--all` for every command |
Run `/help --all` to see every available command.
--all)skills/*/SKILL.md file.name, description, and user-invocable.user-invocable is true and name is present — agent-loaded skills are not user commands and must not appear.## Available Commands
| Command | Description |
|---------|-------------|
| /name | description |