OPEN SOURCE / EXECUTION METHOD
Direct the intent.Inspect the evidence.
Director Mode Lite packages a repeatable operating method around Claude Code. It does not make model output deterministic; it makes acceptance criteria, delegation, local state, tests, and review boundaries easier to see.
Repository verified / 2026.07.20
CONTRACT / NOT MAGIC
A visible loop around a probabilistic worker.
The toolkit adds structure around the model. Completion still comes from observable evidence and human acceptance, not from a checkbox or checkpoint alone.
- 01 / INTENT
Define scope and acceptance criteria.
- 02 / ROUTE
Select a workflow, agent, or external CLI handoff.
- 03 / EXECUTE
Run a bounded TDD-oriented iteration.
- 04 / VERIFY
Inspect tests, diffs, logs, and installer health.
- 05 / ACCEPT
A human accepts, revises, or stops the run.
SYSTEM / LAYERS
What the toolkit actually adds.
Each layer has a job and a boundary. Use only the parts your repository can safely support.
Repeatable workflows
`/workflow`, planning, test-first, review, documentation, and commit routines package a consistent sequence.
Bounded continuation
Auto-Loop and Evolving-Loop use local hooks, state, stop files, and configurable iteration limits.
Context isolation
Fourteen agent definitions cover review, debugging, documentation, Claude configuration, and evolution roles.
External handoffs
Codex, Gemini, and separate Claude profiles can receive scoped tasks when those CLIs are installed and authenticated.
INSTALL / TWO MODES
Choose between portable plugin access and project-integrated hooks.
The native plugin path exposes namespaced skills and agents. The repository installer copies project-local assets and activates only the hooks selected in the wizard.
claude plugin marketplace add claude-world/director-mode-lite
claude plugin install director-mode-lite@director-mode-lite
/reload-pluginsAdd the marketplace first. Plugin-only installs do not wire project hooks.
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/projectReview the repository, run the wizard, then verify the target. Existing `.claude/` is backed up before changes.
AUTO-LOOP / EVIDENCE PATH
Continuation has an exit path.
A Stop hook may ask Claude to continue when tracked criteria remain. Set a finite iteration budget, keep the stop file available, and treat test output plus the final diff as the evidence.
- 01Acceptance criteria
- 02Failing test
- 03Minimal change
- 04Test + diff
- 05Accept / stop
SAFETY / LOCAL FIRST
The safe default is inspectable and reversible.
The project installer backs up an existing `.claude/` directory before merging files.
The setup wizard lets you choose no automation, Auto-Loop, or Auto-Loop plus Evolving-Loop.
Iteration limits and `.auto-loop/stop` are operational controls, not decoration.
Generated skills and strategy notes are code-adjacent inputs; inspect them before reuse.
Checkpoints help resume a loop. Version control remains the recovery and review boundary.
The bundled verifier checks installation shape; your own tests must establish product behavior.
RELEASE / 1.9.0
Guided setup without hiding the controls.
v1.9.0 added `install.sh --wizard`, three automation levels, optional observability and safety hooks, seven wizard regression tests, and version consistency fixes.
Use the method. Keep the judgment.
Start from a real repository, install only the controls you understand, and require an artifact you can review.