director-mode
Skill80 starsChanged 8 months agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use .director-mode/GUIDANCE.md when the project runtime is installed.
- Distinctive: line 14
Keep the working contract small:
- Distinctive: line 19
Use independent agents when parallel work or an independent review helps.
- Distinctive: line 20
Keep one integrator responsible for the final diff and verification.
- Very specific: line 21
If another CLI should take over, use the session-relay skill.
- Distinctive: line 23
Keep guidance proportional.
- Very specific: line 29
When discovery, adapters, or hooks seem wrong, run director-doctor from the first available location:
- Very specific: line 36
Use --json --no-probe for deterministic inspection.
- Very specific: line 42
If the user explicitly chooses an unrestricted session in a trusted workspace, the installed director-open launcher can express that choice …
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- game1991/awesome-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- changelog-observerSkill
- agent-checkSkill
- agentsSkill
- agent-templateSkill
- auto-loopSkill
- changelogSkill
- check-environmentSkill
- claude-md-checkSkill
- claude-md-templateSkill
- code-reviewerSkill
- debuggerSkill
- doc-writerSkill
- evolving-loopSkill
- evolving-statusSkill
- focus-problemSkill
- getting-startedSkill
- handoff-claudeSkill
- handoff-codexSkill
- handoff-geminiSkill
- handoff-grokSkill
- hooks-checkSkill
- hook-templateSkill
- interop-routerSkill
- mcp-checkSkill
- planSkill
- project-health-checkSkill
- project-initSkill
- session-relaySkill
- skill-checkSkill
- skillsSkill
- skill-templateSkill
- smart-commitSkill
- test-firstSkill
- test-runnerSkill
- workflowSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.