DIRECTOR MODE LITE / INSTALL

Choose the boundary before the command.

Plugin access and project automation are different products. Pick the smallest installation that gives you the behavior you need.

v1.9.0 / released 2026.07.08 / CLI last tested 2.1.201

Dependency matrix

Python 3 and jq are required for the complete hook-driven modes, not optional polish.

MODE	CLAUDE CODE	GIT + BASH	PYTHON 3	JQ
Native plugin	Required	—	—	—
Project assets / no hooks	Required	Required	—	—
Auto-Loop hooks	Required	Required	Required	Required
Evolving-Loop hooks	Required	Required	Required	Required

MODE / 01Portable

Native plugin

Adds the ClaudeWorld marketplace, installs the namespaced skills and agents, then reloads them. This path does not register project hooks.

claude plugin marketplace add claude-world/director-mode-lite
claude plugin install director-mode-lite@director-mode-lite
/reload-plugins

Use this when you want callable methods without modifying a repository’s `.claude/` setup.

MODE / 02Hooks opt-in

Project integrated

Clone and inspect the repository, run the guided installer against an explicit target, then run the bundled structural verifier.

git clone https://github.com/claude-world/director-mode-lite.git
cd director-mode-lite
./install.sh /path/to/project --wizard
./scripts/verify-install.sh /path/to/project

The wizard offers no automation, Auto-Loop, or Auto-Loop plus Evolving-Loop. Existing `.claude/` is backed up first.

First ten minutes

After reopening Claude Code in the target repository, establish context before starting a loop.

01/getting-started
Inspect the available methods and operating assumptions.
02/project-init
Build project-local context and conventions.
03/workflow
Run one bounded development workflow with explicit acceptance criteria.

What verification proves

The bundled verifier checks installation structure and integration signals. It cannot prove that your product behavior is correct.

CHECKS

Required command, agent, and skill inventory is present.
Settings JSON parses and selected Director Mode hooks are registered.
Bundled hook scripts needed by the selected mode are executable.

DOES NOT PROVE

Your application tests pass.
Model output is correct or deterministic.
Custom hooks are semantically compatible with the selected loop.

Recovery is part of installation

S-01
Commit or back up the target repository first.
S-02
Review hook collisions; an existing event may need manual composition.
S-03
Keep `.auto-loop/stop` reachable and set finite iteration limits.
S-04
Use the interactive uninstaller; the hooks-only path removes only Director Mode Lite hook files and keeps unrelated custom hooks.

Uninstall from the same checkout

Review the interactive choices before confirming complete removal. Shared agents and skills may belong to other workflows.

cd /path/to/director-mode-lite
./uninstall.sh /path/to/project

Install only what you can inspect.

Read the source, verify the target, and treat tests plus the final diff as the acceptance evidence.