changelog-observer
Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.
@claude-worldInstall SkillDevelopment
Skill
/project-init
Set up concise, guidance-first Claude/Codex/Grok project context after inspecting the repository. Use on first setup, after cloning, or when the user runs /project-init.
Claude Code
$ npx -y skills add claude-world/director-mode-lite --skill project-init --agent claude-code
Codex
$ npx skills add claude-world/director-mode-lite --skill project-init -a codex -y
Cursor
$ npx skills add claude-world/director-mode-lite --skill project-init -a cursor -y
Gemini CLI
$ npx skills add claude-world/director-mode-lite --skill project-init -a gemini-cli -y
GitHub Copilot
$ npx skills add claude-world/director-mode-lite --skill project-init -a github-copilot -y
OpenCode
$ npx skills add claude-world/director-mode-lite --skill project-init -a opencode -y
Windsurf
$ npx skills add claude-world/director-mode-lite --skill project-init -a windsurf -y
SKILL.md
project-init.SKILL.mdname: project-init
description: "Set up concise, guidance-first Claude/Codex/Grok project context after inspecting the repository. Use on first setup, after cloning, or when the user runs /project-init."
user-invocable: true
Project initialization
Create the smallest useful project context without adding permission gates, blocking hooks, or mandatory process rules.
1. Inspect before writing
- Read existing `CLAUDE.md`, `AGENTS.md`, README, manifests, scripts, and CI.
- Detect the language, framework, build, test, lint, and development commands
from repository evidence.
- Preserve existing user guidance and unrelated configuration.
- If the stack or desired workflow cannot be inferred safely, ask one focused
question instead of inventing it.
2. Add concise shared context
Keep permanent guidance focused on facts useful in most sessions:
# Project name
## Purpose
[What this repository delivers]
## Stack and structure
- [Language/framework]
- [Important entry points]
## Commands
- dev: [verified command]
- test: [verified command]
- build: [verified command]
- lint: [verified command]
## Local conventions
- [Only repository-specific conventions supported by evidence]
Use the Director managed block in both `CLAUDE.md` and `AGENTS.md` so all three CLIs can find `.director-mode/GUIDANCE.md`. Put detailed, conditional procedures in skills rather than expanding the permanent files.
3. Verify native assets
Check the selected CLI surfaces:
Claude: .claude/skills/ and .claude/agents/
Codex: .agents/skills/ and .codex/agents/
Grok: shared Claude-compatible skills and .grok/agents/
Relay: .director-mode/bin/director-relay
Run `scripts/verify-install.sh` when available. Do not require every optional tool merely to declare setup complete.
4. Optional integrations
MCP servers, hooks, TDD, autonomous loops, and extra agents are choices, not defaults. Suggest one only when it materially helps the current repository and explain its effect. Install or register it only after the user requests it.
In particular, never register a Stop hook, deny rule, validator, security guard, or background tracker as part of ordinary project initialization.
5. Report the result
Summarize detected facts, files created or updated, validation actually run, and optional next steps. A useful default next step is `director-mode` or `workflow`; use `session-relay` when another CLI should take over.
Read more
name: project-init description: "Set up concise, guidance-first Claude/Codex/Grok project context after inspecting the repository. Use on first setup, after cloning, or when the user runs /project-init." user-invocable: true
Project initialization
Create the smallest useful project context without adding permission gates, blocking hooks, or mandatory process rules.
1. Inspect before writing
- Read existing `CLAUDE.md`, `AGENTS.md`, README, manifests, scripts, and CI.
- Detect the language, framework, build, test, lint, and development commands
from repository evidence.
- Preserve existing user guidance and unrelated configuration.
- If the stack or desired workflow cannot be inferred safely, ask one focused
question instead of inventing it.
2. Add concise shared context
Keep permanent guidance focused on facts useful in most sessions:
# Project name ## Purpose [What this repository delivers] ## Stack and structure - [Language/framework] - [Important entry points] ## Commands - dev: [verified command] - test: [verified command] - build: [verified command] - lint: [verified command] ## Local conventions - [Only repository-specific conventions supported by evidence]
Use the Director managed block in both `CLAUDE.md` and `AGENTS.md` so all three CLIs can find `.director-mode/GUIDANCE.md`. Put detailed, conditional procedures in skills rather than expanding the permanent files.
3. Verify native assets
Check the selected CLI surfaces:
Claude: .claude/skills/ and .claude/agents/ Codex: .agents/skills/ and .codex/agents/ Grok: shared Claude-compatible skills and .grok/agents/ Relay: .director-mode/bin/director-relay
Run `scripts/verify-install.sh` when available. Do not require every optional tool merely to declare setup complete.
4. Optional integrations
MCP servers, hooks, TDD, autonomous loops, and extra agents are choices, not defaults. Suggest one only when it materially helps the current repository and explain its effect. Install or register it only after the user requests it.
In particular, never register a Stop hook, deny rule, validator, security guard, or background tracker as part of ordinary project initialization.
5. Report the result
Summarize detected facts, files created or updated, validation actually run, and optional next steps. A useful default next step is `director-mode` or `workflow`; use `session-relay` when another CLI should take over.
Ships withdirector-mode-lite
Use Claude Code like a Director, not a Programmer. MIT toolkit with Auto-Loop, guided setup, 27 commands, 14 agents, and 32 skills.
8036 skills14 agents
Stars on GitHub
Momentum
- stars in total
- 80
Other skills on director-mode-lite.
@claude-worldInstall Skillagent-check
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when…
@claude-worldInstall Skillagent-template
Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct…
@claude-worldInstall Skillagents
List all available agents (core, expert, self-evolving). Use when the user asks what agents are available or runs /agents.
@claude-worldInstall Skillauto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog
@claude-worldInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about project-init.
- Which coding agents can use project-init?
- project-init installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.