mantaray0

crew-config

The crew config schema and the project-type/tag registry — the source of truth for config.json, global defaults, and archetypes. Use when running /crew:init or /crew:setup, or when reading/writing any crew config.

crew-context

How crew holds project state across sessions — the .planning state model and what each file owns. Use when reading/writing .planning state or resuming work.

crew-conventions

How crew runs every command — the step-by-step interaction flow (surface every decision via free-text / single-select / multi-select, batch the independent ones in a stepper, stay sequential on dependencies, never silently applying defaults) and language (respond in the user's language; repo content stays English). Apply at the start of every crew command.

Code & Development Listed

deploy

How crew turns a verified commit into a release/deployment — config.workflow.ship (enabled + runDeploy + releaseTool), config.git as the single git authority, provider handling (gh/glab), and the safety rules. Use during /crew:ship.

learn

How crew turns finished work into reusable assets — distilling patterns/decisions into proposed skills, tags, or PROJECT.md updates. Use during /crew:learn.

planning

Conventions for crew roadmaps and plans — milestone/phase structure, status markers, inter-phase dependencies, and the permanent-`_spec.md`-plus-referencing-phase-plans format. Use when writing or adjusting ROADMAP.md and plans/.

verify

How crew verifies a change — the test → review → harden → simplify pipeline, run in fresh contexts, with config-driven steps and model selection. Use after implementing any phase.

Code & Development Listed

crew-deploy

How crew turns a verified commit into a release/deployment — the config.deploy mode contract (off/orchestrate/execute), composition with config.git as the ceiling, provider handling (gh/glab), and the safety rules. Use during /crew:ship.

crew-planning

Conventions for crew roadmaps and plans — milestone/phase structure, status markers, inter-phase dependencies, and the spec-head-in-plan format. Use when writing or adjusting ROADMAP.md and plans/.

Code & Development Listed

git-merge

How crew isolates parallel work and integrates it — worktree-per-feature, claims, rolling integration, and intent-aware conflict resolution. Use during `/crew:execute dispatch` and merging.

crew-learn

How crew turns finished work into reusable assets — distilling patterns/decisions into proposed skills, tags, or PROJECT.md updates. Use during /crew:retro.

verification-loop

How crew verifies a change — the verify → review → harden → simplify pipeline, run in fresh contexts, with config-driven steps and model selection. Use after implementing any phase.