fix(readme): standardize bare slash commands, rename status→health

README.md

@@ -79,7 +79,7 @@ npx playwright install chromium
 ### Verify
 
 ```bash
-/devkit:status
+/health
 ```
 
 This shows which CLIs are installed, which agents are available, and which commands are ready.
@@ -96,7 +96,7 @@ This shows which CLIs are installed, which agents are available, and which comma
 # "research the best auth library for Node"
 
 # Slash commands for complex workflows:
-/tri:review                   # Multi-agent code review
+/tri-review                   # Multi-agent code review
 # Or just describe: "submit a PR", "ship this" → pr-ready skill auto-activates
 ```
 
@@ -123,24 +123,12 @@ Enforcement (runs automatically):
 
 ---
 
-## Commands
-
-All skills are tab-completable slash commands in current Claude Code. The primary user-facing entry points:
-
-| Command | What it does |
-|---|---|
-| `/tri-review` | Code review from 1-3 agents, consolidated report |
-| `/tri-debug` | Independent root-cause analysis from each agent |
-| `/tri-security` | Security audit with severity-ranked consensus |
-| `/devkit:status` | Health check |
-| `/devkit:setup-rules` | Install language-specific coding rules to `~/.claude/rules/` (user-only — `disable-model-invocation` prevents auto-trigger) |
-
-Every workflow also has a dedicated slash command: `/feature`, `/bugfix`, `/audit`, `/refactor`, `/pr-ready`, `/self-*`, etc. Tasks like "ship this PR" or "submit a PR" also auto-activate the `pr-ready` skill via natural language.
-
-### Workflows
+## Workflows
 
 All 21 YAML workflows are invoked via the MCP engine. Every workflow has a trigger skill so natural-language keywords dispatch deterministically — saying "build a feature", "fix this bug", "tri review", or "deep research X" fires the matching skill, which calls `devkit_start` and the engine takes over.
 
+Every workflow is also a tab-completable slash command. Bare names work (`/feature`, `/bugfix`, `/tri-review`, `/health`, `/setup-rules`); the fully-qualified `/devkit:<name>` form also works if you want to disambiguate from another plugin or a Claude Code built-in.
+
 | Workflow | What it does |
 |---|---|
 | `feature` | Brainstorm, plan, implement, test, lint, review |
@@ -254,7 +242,7 @@ All agents run in worktree isolation.
 Language-specific rules that auto-activate when Claude reads matching files. Installed to `~/.claude/rules/` — rules guide how to write, hooks catch what you missed.
 
 ```bash
-/devkit:setup-rules
+/setup-rules
 ```
 
 | Language | Examples |

ROADMAP.md

@@ -3,7 +3,7 @@
 ## Implemented
 
 - **MCP engine** — Go server exposes `devkit_start`, `devkit_advance`, `devkit_status`, `devkit_list` tools inside Claude Code. Step ordering enforced via MCP tool scoping + PreToolUse hook exit 2. Session state in session.json (hot path, <50ms hook reads) + SQLite (cold history). ~65% token reduction vs old monolithic prompts.
-- **Skills-first architecture** — All entry points are skills in `skills/` (tab-completable slash commands in current Claude Code). Primary user-facing commands: `/tri-review`, `/tri-debug`, `/tri-security`, `/devkit:status`, `/devkit:setup-rules` (user-only via `disable-model-invocation`). Every workflow also has a dedicated skill for natural-language dispatch. The `commands/` directory is retained for backward compat but empty of new entries — redundant tri-* command files were removed (skills take precedence per Claude Code docs) and the generic `/devkit:workflow <name>` runner was removed since every workflow now has its own slash command (`/feature`, `/bugfix`, etc.).
+- **Skills-first architecture** — All entry points are skills in `skills/` (tab-completable slash commands in current Claude Code; bare names like `/tri-review` work, `/devkit:<name>` form also works for disambiguation). Primary user-facing commands: `/tri-review`, `/tri-debug`, `/tri-security`, `/health`, `/setup-rules` (user-only via `disable-model-invocation`). Every workflow also has a dedicated skill for natural-language dispatch. The `commands/` directory is retained for backward compat but empty of new entries — redundant tri-* command files were removed (skills take precedence per Claude Code docs) and the generic `/devkit:workflow <name>` runner was removed since every workflow now has its own slash command (`/feature`, `/bugfix`, etc.).
 - **Deterministic workflow conversion** — All command logic moved from LLM-interpreted markdown to Go-engine-driven YAML workflows; ~3,600 lines of inline logic removed
 - **38 skills** — 21 workflow trigger skills (feature, bugfix, refactor, audit, research, deep-research, pr-ready, autoloop, test-gen, doc-gen, onboard, tri-review, tri-debug, tri-security, tri-dispatch, self-audit, self-improve, self-lint, self-migrate, self-perf, self-test) + 7 coding principles (executing, clean-code, DRY, YAGNI, dont-reinvent, stuck, scratchpad) + 4 tools (gcli, scrape, screenshot, browser) + 1 meta-orchestration (mega-pr) + 2 content (changelog, adr) + 1 reference (creating-workflows)
 - **Deterministic skill dispatch for every workflow** — Every one of the 21 workflows has a natural-language trigger skill with keyword-rich description. Saying "build a feature", "tri review", "deep research X", etc. deterministically invokes the matching skill, which calls `devkit_start` and the engine enforces every step from there. Closes the entry-gate non-determinism where 11/18 workflows previously had no natural-language path. Skill tool added to the guard allowlist so nested mid-workflow skill dispatch works.

skills/status/SKILL.md → skills/health/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: status
-description: Check devkit health — which external CLIs (codex, gemini, gh, rtk, sg, gcli) are installed, which agents are available, which skills are ready to use. Use when asked about devkit status, "is devkit working?", "what's installed?", "what devkit capabilities do I have?", diagnosing devkit setup issues, or running /devkit:status. Read-only diagnostic, safe to auto-invoke.
+name: health
+description: Check devkit health — which external CLIs (codex, gemini, gh, rtk, sg, gcli) are installed, which agents are available, which skills are ready to use. Use when asked about devkit health, devkit status, "is devkit working?", "what's installed?", "what devkit capabilities do I have?", diagnosing devkit setup issues, or running /devkit:health. Read-only diagnostic, safe to auto-invoke.
 ---
 
 # Devkit Status
@@ -74,8 +74,8 @@ List all skills from `skills/` directory, marking which ones need external CLIs:
 | /tri-review | ⚠ partial | 2/3 agents available (no gemini) |
 | /tri-debug | ⚠ partial | 2/3 agents available |
 | /tri-security | ⚠ partial | 2/3 agents available |
-| /devkit:status | ✓ ready | This skill |
-| /devkit:setup-rules | ✓ ready | One-time setup |
+| /health | ✓ ready | This skill |
+| /setup-rules | ✓ ready | One-time setup |
 
 ### Agents
 | Agent | Model | Isolation | Status |