status
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
Best use case
status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
Teams using status should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/status/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How status Compares
| Feature / Agent | status | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Status Skill Generate a diagnostic report of the metaswarm installation, project configuration, and potential issues. Useful for troubleshooting and verifying setup or migration. --- ## Checks Run each check below and present results in a single formatted report. ### 1. Plugin Version - Read `.claude-plugin/plugin.json` from the plugin root -- report the `version` field - Fallback: read `package.json` at plugin root for `version` - If neither found: `Plugin version: UNKNOWN` ### 2. Project Setup State - Check if `.metaswarm/project-profile.json` exists in the working directory - If present, report key fields: `distribution`, `metaswarm_version`, `language`, `framework`, `test_runner` - If absent: `Project setup: NOT CONFIGURED -- run /metaswarm:setup` ### 3. Command Shims Check these 6 files in `.claude/commands/`: | Shim | Expected | |---|---| | `start-task.md` | Routes to `/metaswarm:start-task` | | `prime.md` | Routes to `/metaswarm:prime` | | `review-design.md` | Routes to `/metaswarm:review-design` | | `self-reflect.md` | Routes to `/metaswarm:self-reflect` | | `pr-shepherd.md` | Routes to `/metaswarm:pr-shepherd` | | `brainstorm.md` | Routes to `/metaswarm:brainstorm` | For each: report Present/Missing. If the file exists but does not contain "metaswarm" routing, flag as `present (non-metaswarm content)`. ### 4. Legacy Embedded Plugin - Check for `.claude/plugins/metaswarm/.claude-plugin/plugin.json` - If found: `DETECTED -- run /metaswarm:migrate` - If found alongside the marketplace plugin, flag prominently as a conflict ### 5. BEADS Plugin - Scan `~/.claude/plugins/cache/` for a directory containing `.claude-plugin/plugin.json` with `"name": "beads"` - If found: `installed (standalone)` -- metaswarm defers priming to BEADS - If not found: `not separately installed` ### 6. `bd` CLI ```bash command -v bd && bd --version 2>/dev/null ``` - If found: report path and version - If not found: `not installed -- knowledge priming and self-reflect require bd. Core orchestration works without it.` ### 7. External Tools - Read `.metaswarm/external-tools.yaml` -- if absent: `not configured (optional)` - If present, check each enabled adapter's availability: ```bash command -v codex # Codex CLI command -v gemini # Gemini CLI ``` Report per-tool: enabled (yes/no), status (available/not installed). ### 8. Coverage Thresholds - Read `.coverage-thresholds.json` -- if absent: `not configured` - If present, report threshold values (lines, branches, functions, statements) and enforcement command ### 9. Node.js ```bash node --version 2>/dev/null ``` - If found: report version - If not found: `not installed -- scripts/beads-*.ts require Node.js. Core orchestration works without it.` --- ## Output Format ```markdown ## Metaswarm Status Report | Component | Status | |---|---| | Plugin version | 1.0.0 | | Project setup | Configured (distribution: plugin) | | Command shims | 6/6 present | | Legacy embedded plugin | Not detected | | BEADS plugin | Not separately installed | | bd CLI | Available (v0.5.2) | | External tools | Codex: available, Gemini: not installed | | Coverage thresholds | 100% (all categories) | | Node.js | Available (v22.4.0) | ### Issues Found - None ### Recommendations - None ``` When issues are found: ```markdown ### Issues Found 1. Legacy embedded plugin detected alongside marketplace plugin -- run `/metaswarm:migrate` 2. Command shim `start-task.md` missing -- run `/metaswarm:setup` ### Recommendations 1. Install `bd` CLI for knowledge priming and self-reflect 2. Configure external tools for cross-model review (`.metaswarm/external-tools.yaml`) ``` --- ## Error Handling This skill is diagnostic-only and never fails fatally. If any individual check errors, report the failure for that check (e.g., `Plugin version: ERROR -- could not read plugin.json`) and continue with remaining checks.
Related Skills
visual-review
Take screenshots of web pages and UI using Playwright for visual review and iteration
start
Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work
setup
Interactive project setup — detects your project, configures metaswarm, writes project-local files
pr-shepherd
Monitor a PR through to merge — handle CI failures, review comments, and thread resolution automatically until all checks pass
plan-review-gate
Automatic adversarial review gate that spawns 3 independent reviewers in parallel after any plan is drafted - all must PASS before presenting to user
orchestrated-execution
4-phase execution loop for work units - IMPLEMENT, VALIDATE, ADVERSARIAL REVIEW, COMMIT
migrate
Migrate from npm-installed metaswarm to the marketplace plugin — removes redundant files with safety checks
handling-pr-comments
Address PR review feedback systematically — fetch inline comments, review bodies, handle outside-diff-range comments, resolve threads with proper attribution
external-tools
Delegate implementation and review tasks to external AI CLI tools (Codex, Gemini) with cross-model adversarial review
design-review-gate
Automatic review gate that runs after brainstorming completes - spawns PM, Architect, Designer, Security, and CTO agents in parallel, iterates until all approve
create-issue
Create comprehensive GitHub issues with TDD plans, acceptance criteria, and agent instructions for autonomous PR lifecycle management
brainstorming-extension
Enforces design review gate after brainstorming — bridges superpowers:brainstorming into the metaswarm quality pipeline