adam

Add a single sub-agent, skill, or hook to .claude/. Prompts interactively if details are missing.

One-time scaffolding — creates spec/, rewrites CLAUDE.md as a brief + spec index, then interactively suggests per-project hooks/skills/sub-agents

Read-only health check of spec/, CLAUDE.md, and .claude/ — reports issues, does not modify files

Add a new spec — either spec/<topic>.md for a concept/subsystem or spec/pipelines/<topic>.html for a workflow walkthrough (with --pipeline)

Refresh specs to match current code — drift detection across all markdown specs, or a single spec when a path is given (markdown or pipeline-spec HTML)

Spec-driven setup orchestrator. Use this agent when the user runs /adam:setup or asks to "set up adam", "scaffold spec-driven docs", "init spec/ folder", "convert CLAUDE.md into a spec index", "personalize claude code for this project", "add a workflow walkthrough / pipeline for <X>", or "draw a flow chart for <X>". Inspects the project, infers stack and architecture, then writes per-project artifacts directly into the target repo: spec/*.md skeletons, spec/pipelines/<slug>.html workflow walkthroughs (HTML, audit-exempt, viewer at spec/pipelines.html), a curated CLAUDE.md acting as a spec index, .claude/agents/*.md tailored sub-agents, and .claude/settings.json hooks suited to the detected stack. Does NOT ship static artifacts — every output is generated from what it observes in the working tree.

Add a single project-local Claude Code automation — sub-agent, skill, or hook — into .claude/. Use when the user runs /adam:claude-add, /claude-add, or asks to "add a sub-agent that...", "add a skill for X", "add a hook that runs Y on file write", "wire ruff into claude-code", "give me a code-reviewer agent for this project", or "create a new agent/skill/hook for the project". Distinct from /adam:setup (which suggests a batch); this adds exactly ONE artifact at a time, prompting for missing details via AskUserQuestion.

One-time scaffolding of a spec-driven Claude Code workflow in this project. Use when the user runs /adam:setup, /setup, or asks to "set up adam", "scaffold spec/ folder", "init spec-driven docs", "convert CLAUDE.md into a spec index", or "personalize claude code for this repo". Pipeline is strictly ordered: gitnexus analyze → spec scaffolding → per-class AskUserQuestion menus (hooks, subagents, skills) → create only what the user picks → CLAUDE.md → spec-lint verify → final brief.

Lint the spec-driven Claude Code ecosystem in this project — checks spec/, CLAUDE.md, and .claude/ for integration issues without rewriting anything. Use when the user runs /adam:spec-audit, /spec-audit (in this plugin's namespace), or asks to "lint specs", "check spec ecosystem", "verify CLAUDE.md is wired up", "audit my claude code setup", or "is my spec-driven workflow healthy?". Read-only — reports issues but does not modify files. For drift fixing, point users at /adam:spec-update.

Add a single new spec/<topic>.md when a fresh concept, subsystem, or integration enters the project — OR add a pipeline-spec (HTML workflow walkthrough) at spec/pipelines/<topic>.html when the user passes --pipeline or asks for a "flow chart", "pipeline", "workflow diagram". Use when the user runs /adam:spec-create, /spec-create, or asks to "add a spec for X", "document the new <subsystem>", "create a spec covering <topic>", "we just added <X>, write its spec", "draw a pipeline for <flow>", "add a workflow walkthrough for <X>". Will refuse if spec-driven scaffolding (`spec/INDEX.md`, `CLAUDE.md`) is missing — points the user at /adam:setup instead.

Refresh existing specs to match the current code. Use when the user runs /adam:spec-update, /spec-update, or asks to "update spec/", "refresh project docs", "audit specs against code", "check CLAUDE.md against the code", or "sync the spec after my refactor". Detects drift between spec/*.md and the actual working tree, rewrites stale specs, merges duplicates, and refreshes spec/INDEX.md plus the CLAUDE.md spec index table (including token counts). Accepts an optional path argument to update a single spec only.

1 hook across 1 event