claude-world/director-mode-lite / skills/director-mode
director-mode
VerifiedDirect 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.
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |