Stats
Actions
Tags
From dev-standards
You are working in the commands directory. Commands are the framework's public API: the `/` entries a user types to invoke a workflow.
How this command is triggered — by the user, by Claude, or both
Slash command
/dev-standards:CLAUDEFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
# commands/ — User-invoked workflows You are working in the commands directory. Commands are the framework's public API: the `/` entries a user types to invoke a workflow. ## What goes here One markdown file per command. File name is the command name minus the slash: `/validate` lives at `validate.md`, `/tdd` at `tdd.md`, `/new-agent` at `new-agent.md`. ## Required frontmatter Every command declares: ## Composition rules (non-negotiable) 1. **Commands compose agents. Agents never call commands.** Composition flows one way. 2. **Each command has exactly one responsibility.** `/valid...
You are working in the commands directory. Commands are the framework's public API: the / entries a user types to invoke a workflow.
One markdown file per command. File name is the command name minus the slash: /validate lives at validate.md, /tdd at tdd.md, /new-agent at new-agent.md.
Every command declares:
---
context: fork | none # fork = run in an isolated subagent context (dominant choice)
model: opus | sonnet | haiku # resource allocation (opus for judgment, haiku for summaries)
allowed-tools: <list> # tools the command can invoke
argument-hint: <string> # autocomplete hint shown in the CC UI
---
/validate validates. /tdd runs TDD. /scaffold scaffolds. No mixed responsibilities. meta-command-composition-reviewer enforces this at commit time.meta-session-planner as its first step. The planner sizes the work against the current session's budget, decomposes if necessary, writes the plan to session-state.md. Skipping this is blocked by the composition reviewer..current_phase (read by context_budget.py). The last step clears it.See docs/phases/README.md for the 11-phase roadmap. Each command is associated with one lifecycle phase (discover, research, design, develop, test, validate, deploy, operate, maintain, document, meta).
Commands use kebab-case verbs or verb-noun pairs:
validate.mdscaffold.mdtdd.mdnew-agent.mdvalidate-agents.mdhandoff.mdUse meta-command-scaffolder via /new-command <name> once Phase 1 is live. Do not hand-write new commands afterwards — the scaffolder enforces frontmatter, composition rules, and graph registry updates.
@docs/architecture/principles/psf.md — commands sit at the fifth rung of the PSF (public API, highest privilege)@docs/architecture/principles/context-awareness.md — why meta-session-planner runs first@docs/architecture/components/commands.md — full command catalog (populated as commands are built)npx claudepluginhub myenquiringmind/dev-standards-plugin --plugin dev-standards/CLAUDEDisplays recent activity log from claude-mem context in auto-generated <claude-mem-context> section, listing actions or 'No recent activity'.
/CLAUDEProvides reference documentation on slash command system: required YAML headers, category overview, protocols, and directory contents analysis.
/CLAUDEDisplays documentation on git behaviors for /commit, /save, /pr, /rebase, /push: staging logic, branch naming, CI monitoring, autonomous fixes, rebase conflicts, push gates.
/CLAUDEProvides specialized modes: extract takeaways to file (/learn), run structured interviews (/interview), collaborate read-only with tools (/collaborate), spawn parallel agents for epiphanies (/epiphany).
/CLAUDESeeds discovery configs/setup scripts and plants project environments with grove CLI: registers sources, clones repos, copies/patches ports/files, installs deps. Also lists, doctors, uproots.
/CLAUDEScans recent user messages for behavioral signals to auto-propose hookify rules (/hookify). Lists (/list) and configures (/configure) rules in .claude/hookify.*.local.md files.