ADLC Toolkit

Skills, agents, and templates for spec-driven development with Claude Code. Stack-agnostic at the core, with optional preset configs for common stacks (iOS+Firebase+Cloud Run, etc.).

Install

Two commands, run in your own terminal:

claude plugin marketplace add atelier-fashion/adlc-toolkit
claude plugin install adlc@adlc-toolkit

This repo is both the marketplace (adlc-toolkit) and the plugin (adlc). Start a new Claude Code session after installing. On this route every skill is namespaced: type /adlc:<skill>, for example /adlc:init, /adlc:spec or /adlc:proceed. The toolkit's agents are registered as adlc:<name>. The skill table below uses the bare names; add the adlc: prefix on the plugin route.

The plugin's version is pinned to this repo's VERSION, so it changes only when a release is cut, not on every merge; you get a new release when you update (see Updating). Contributors and the maintainer use a symlink live install instead, described under Contributing and live install. Use one route per machine, not both (see Known limitations).

Did it work? adlc doctor checks every dependency end to end and prints a copy-pasteable fix for anything that fails. On the plugin route, run it by path from any terminal once a Claude Code session has started (the session's start hook writes the pointer file this line reads):

"$(cat ~/.claude/adlc/plugin-root)/scripts/adlc" doctor

Inside a Claude Code session the same hook also appends the plugin's scripts/ directory to the shell's PATH, so skills can run plain adlc (see the loader table below for how far that is verified).

On the plugin route, the four checks that inspect the symlink install (skills-symlink, agents-symlink, toolkit-clean, path-shims) print SKIP with a notice. Two checks cover the routes themselves:

• plugin-route reports which route the doctor runs on and its version. On the plugin route it checks that this is the copy Claude Code loads, that ~/.claude/adlc/plugin-root names it, and that scripts/adlc is executable and, inside a Claude Code session, on PATH. Its fixes re-run what the hook does (CLAUDE_PLUGIN_ROOT='<root>' sh '<root>/scripts/session-start.sh', or just start a new session), chmod +x '<root>/scripts/adlc', or reinstall (claude plugin uninstall adlc@adlc-toolkit && claude plugin install adlc@adlc-toolkit). When the doctor cannot read the install record, it fails and points at claude plugin details adlc.
• doubled-install fails when the symlink install and the plugin are both installed. It prints one fix for each way out: claude plugin uninstall adlc@adlc-toolkit keeps the symlink install, and an rm of the ~/.claude/skills and ~/.claude/agents links (plus ~/bin/adlc when it runs the clone) keeps the plugin. The rm removes the links, not the clone.

See tools/adlc/README.md for the full check list.

What the plugin runs and writes

This paragraph is for anyone reviewing what the plugin does to a machine, including the Claude directory's security scan. The plugin registers one hook, in hooks/hooks.json. At session start Claude Code runs sh "${CLAUDE_PLUGIN_ROOT}/scripts/session-start.sh". scripts/session-start.sh is POSIX sh. It uses no network and no Python. It writes nothing until CLAUDE_PLUGIN_ROOT passes a check: the path must be absolute, must hold no newline, .. or shell metacharacter, and must contain a .claude-plugin/plugin.json naming adlc and a partials/ directory. Then it does three things:

1. Pointer file. It writes the plugin root, one line, to ~/.claude/adlc/plugin-root. The write goes through a temp file and mv, and happens only when the content changed. Skill text that Claude Code did not substitute reads this file to find the plugin (the third arm of the ToolkitRoot line, see .adlc/context/architecture.md).
2. Config scaffold. It writes ~/.claude/adlc/config.yml only when nothing exists at that path. The file sets delegate: enabled: false, so installing the plugin never turns delegation on. Its bytes are identical to the scaffold install.sh writes, and a test pins the two copies equal. That is why its comment says "scaffolded by install.sh" and suggests ./install.sh --with-delegation. On the plugin route, ignore that line. The plugin does not ship the delegation CLIs, and install.sh run from the plugin's copy would link that copy into ~/.claude and double the install. adlc doctor on the plugin route never prints install.sh as a fix: its pyyaml and delegate-gate checks print a pinned pip install and a config edit instead. To use delegation, install by the symlink route with ./install.sh --with-delegation.
3. PATH line. When Claude Code provides CLAUDE_ENV_FILE, the session's environment file, the hook appends one marked line, export PATH="$PATH:<plugin root>/scripts" # adlc-plugin-path, and only once. The plugin's directory goes after your own PATH, so a ~/bin/adlc you already have still wins. scripts/adlc is a POSIX shim that runs python3 <plugin root>/tools/adlc/adlc.py. That CLI uses only the Python standard library.

This is the beginning of the README. Read the rest at the original. Read the full README ↗