Skip to content

Slash commands reference

All commands are namespaced under /dezycro:. Each one is a guided skill — Claude reads the instructions and walks you through the steps interactively.

/dezycro:init

Wire a repo to a Dezycro workspace. Run once per repository.

Interactively asks for workspace and project, detects your dev / staging / prod environments, writes .dezycro/config.json.

/dezycro:work <feature>

Start or resume work on a feature.

Accepts a feature name or UUID. If you don't pass one, the skill helps you pick interactively. Before letting you start, it gates on PRD/TRD/graph approval — features that aren't ready won't unlock until they are. Once accepted, the session is bound to that feature's workbook: every Companion action takes the active feature as context.

/dezycro:author [--doc prd | --doc trd] [--revise-existing]

Guided PRD or TRD authoring.

V2 flow: discovery → clarifying Q&A → drafting → quality gate → finalize. Built on a state machine that survives compaction — you can step away and come back without losing progress.

The TRD quality gate is deterministic + LLM-reviewed: a TRD can't be approved until it has all required sections, no placeholder tokens (TBD/TODO/FIXME), and is grounded in the source PRD's pillars.

Pass --revise-existing to load and edit the current PRD/TRD instead of drafting fresh.

/dezycro:status

Compact workbook snapshot for the active feature. Shows journeys, tasks, recent decisions, open issues, latest verifier results. Requires an active feature (run /dezycro:work first).

/dezycro:sync

Sync the current chunk of work to the workbook. Creates tasks for unfinished work, records decisions from the conversation, links commits, flags issues you've discussed. Use it periodically during longer sessions so the workbook reflects reality.

Also doubles as the explicit trigger for Companion's workbook sweep — say "save progress" or run this command, and the Stop hook will run a sweep on the next turn-end.

/dezycro:publish-spec

Auto-detect + upload an OpenAPI spec for the active feature. Triggers JEP generation (the verifier binary). Run this whenever you've added or changed endpoints — Companion will also nudge you automatically if it detects controller-file edits since the last publish.

/dezycro:verify [--env <name>]

Run the verifier against your local (or remote) environment. Pulls the latest verifier binary, executes the test journeys, uploads the result run to the workbook.

Steps it runs:

  1. Check for pending spec publishes (Companion's controller-edit tracker).
  2. Pull the verifier binary (cached by content hash).
  3. Load auth fixtures from .dezycro/auth.local.json.
  4. Run the verifier against the configured env's apiUrl.
  5. Upload the result run via MCP record_verifier_run.
  6. Surface failing journeys + the top-3 coverage gaps.
  7. Update Companion state (lastVerifyCompletionTs + coverageSnapshot).

Step 7 is what arms the post-verify workbook sweep and the pre-PUSH coverage nudge.

/dezycro:import-features

Reverse-engineer an existing codebase into Dezycro features. Scans for product behavior, generates PRDs and TRDs for each detected feature, lets you review and accept. Most useful when onboarding a legacy repo.