lkzppm

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.

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.

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 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.

Merge one branch into another by opening a pull request, then arming auto-merge (GitHub) or auto-complete (Azure DevOps) so the merge only lands once CI / branch policies pass. Detects the remote platform automatically. Use this skill whenever the user runs /merge, asks to "merge branch X into Y", "integrate branch", "fold branch", or wants to combine branch history. Always invoke this skill before any git merge / gh pr merge / az repos pr work.

Render a terminal flowchart of a Claude Code dynamic-workflow .js file — phases, per-phase agent calls, fan-out / concurrent / pipelined structure, and structured-output markers. Use this skill whenever the user runs /workflow-viz or asks to "visualize a workflow", "show the workflow flowchart", "diagram this workflow", or "map out .claude/workflows". Pure bash wrapper around a Node parser — do NOT reason about the workflow yourself.

Stage and commit changes using Lucas's conventional commit style. Use this skill whenever the user runs /commit, asks to "commit changes", "make a commit", "git commit", "stage and commit", or wants to save their current work to git. Always invoke this skill before doing any git add or git commit work.

Run docker compose against the current working directory (up, down, or rebuild), optionally with a specific compose file and/or service list. Use this skill whenever the user runs /compose or asks to "compose up", "compose down", "rebuild the containers", "restart docker services", or similar. This skill is a pure bash wrapper — do NOT reason about the task, do NOT inspect compose files, do NOT run auxiliary commands.

A working reference for cleaning and reshaping tabular / CSV data — robust reading, type coercion, dedupe, reshape, join, and the encoding traps. Load it for a data task, then drop it.

A working reference for building and debugging regular expressions — anchors, classes, quantifiers, groups, lookarounds, ready-made patterns, and the common traps. Load it to write a pattern, then drop it.

How to phrase and format every reply — lead with the answer, stay concise, plain prose. A behavioral skill, so keep it active for the whole session.