Director mode
Direct substantial repository work across Claude Code, Codex CLI, or Grok Build with a concise brief, parallel agents, evidence-based completion, and optional cross-CLI continuation. Use for project onboarding, multi-step implementation, agent coordination, verification planning, low-interruption setup, or deciding how another CLI should take over. Do not use it as a permission gate or mandatory workflow.From its SKILL.md
npx -y skills add claude-world/director-mode-lite --skill director-modeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- runs commandsInstructs the agent to run 4 commands, including `.director-mode/bin/director-doctor` and 3 more.
SKILL.md
2.3 KB, 403 tokens by cl100k_base, as published. Nobody here has run it
Director Mode
Use .director-mode/GUIDANCE.md when the project runtime is installed. For a
plugin-only install, use this skill's bundled references/GUIDANCE.md instead.
The project guide wins because a repository may intentionally adapt the shared
guidance.
Keep the working contract small:
- State the outcome, relevant context, meaningful constraints, and completion evidence.
- Inspect the repository before choosing an approach.
- Use independent agents when parallel work or an independent review helps.
- Keep one integrator responsible for the final diff and verification.
- If another CLI should take over, use the
session-relayskill.
Keep guidance proportional. A small request does not need a ceremony, a plan file, or an agent team. For larger work, expose assumptions early and let the user redirect the approach without adding approval checkpoints of your own.
Read-only diagnosis
When discovery, adapters, or hooks seem wrong, run director-doctor from the
first available location:
.director-mode/bin/director-doctorin the project;$HOME/.claude/bin/director-doctorfrom Bootstrap Kit;- this skill's bundled
scripts/director-doctor.pyfor plugin-only use.
Use --json --no-probe for deterministic inspection. The doctor reports known
runtime, CLI, asset, and hook surfaces; it never repairs, installs, deletes, or
changes permissions. Treat its recommendations as diagnostic leads, not gates.
Capability boundary
If the user explicitly chooses an unrestricted session in a trusted workspace,
the installed director-open launcher can express that choice with the CLI's
native controls. Do not launch it or rewrite persistent settings merely because
this skill was selected.
These are operating suggestions, not a policy engine. Do not change the CLI's permissions, approvals, sandbox, network access, or hook trust on behalf of this skill.
What ships with it: 4 files
20.6 KB alongside SKILL.md, 1 of them executable
agents/
- openai.yaml342 B
evals/
- evals.json2.3 KB
references/
- GUIDANCE.md4.9 KB
scripts/
- director-doctor.pyruns13.1 KB