MUST be loaded when setting up, installing, migrating, reviewing, auditing, or checking CLAUDE.md files in projects. Covers installing the promode CLAUDE.md into new projects, migrating existing CLAUDE.md content to READMEs (progressive disclosure), and auditing projects for conformance. Invoke PROACTIVELY when user mentions CLAUDE.md, project setup, agent configuration, or code meta files.
Manages CLAUDE.md installation, migration to READMEs, and audits for progressive disclosure. Automatically invoked when you mention CLAUDE.md, project setup, or agent configuration.
/plugin marketplace add mikekelly/opencode-promode/plugin install promode@promodeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/claude-md-sections.mdreferences/progressive-disclosure.mdstandard/MAIN_AGENT_CLAUDE.mdworkflows/audit.mdworkflows/install.mdworkflows/migrate.md<essential_principles> This skill manages projects that adopt the promode methodology — a set of principles and workflows for AI agents to develop software. The methodology emphasises TDD, context conservation, progressive disclosure, and clear delegation patterns.
1. CLAUDE.md is for main agent behaviour CLAUDE.md defines the main agent's role: conversing with users, delegating to sub-agents, and following the promode methodology. It does NOT contain project-specific technical details — those belong in README.md files.
2. Sub-agents use the promode-subagent
Claude Code sub-agents don't inherit CLAUDE.md. The promode-subagent mirrors the same methodology so sub-agents apply the same principles. Main agents delegate to promode-subagent rather than instructing sub-agents to read CLAUDE.md.
3. README.md files are the knowledge graph Each package/directory can have a README.md with domain-specific context. Agents read these just-in-time when working in that area. This keeps initial context lean while making deep knowledge available.
4. Tests are the documentation Long-lived markdown should cover architecture and principles only. Detailed behaviour documentation belongs in executable tests. If behaviour isn't tested, it's not guaranteed.
5. CLAUDE.md is standardised
The standard CLAUDE.md (standard/MAIN_AGENT_CLAUDE.md) should be copied exactly into projects. It is designed to work universally. All project-specific content belongs in README.md files.
</essential_principles>
<never_do>
standard/MAIN_AGENT_CLAUDE.md content — it must be copied exactly into projectsWait for response before proceeding. </intake>
<routing> | Response | Next Action | Workflow | |----------|-------------|----------| | 1, "install", "setup", "new", "create" | Confirm project path | workflows/install.md | | 2, "migrate", "refactor", "move", "convert" | Analyze existing CLAUDE.md | workflows/migrate.md | | 3, "audit", "check", "review", "assess" | Scan project structure | workflows/audit.md |Intent-based routing:
After reading the workflow, follow it exactly. </routing>
<quick_reference>
CLAUDE.md: Copy standard/MAIN_AGENT_CLAUDE.md exactly. Do not modify. This configures the main agent with promode methodology.
Sub-agents: Main agents delegate to promode-subagent, which already knows the methodology.
README.md distribution:
project/
├── CLAUDE.md # Main agent behaviour (promode methodology)
├── README.md # Project overview, links to main components of system, etc
└── docs/
└── {feature}/ # Ephemeral planning docs, and task specs
</quick_reference>
<reference_index>
standard/MAIN_AGENT_CLAUDE.md — The canonical CLAUDE.md (copy exactly into projects)references/progressive-disclosure.md — Why and how to distribute content to READMEsreferences/claude-md-sections.md — Purpose of each CLAUDE.md section
</reference_index><workflows_index>
All in workflows/:
| Workflow | Purpose |
|---|---|
| install.md | Install standard CLAUDE.md into new project |
| migrate.md | Migrate existing CLAUDE.md content to READMEs |
| audit.md | Audit project for progressive disclosure conformance |
| </workflows_index> |
<success_criteria> A well-configured project:
standard/MAIN_AGENT_CLAUDE.mdThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.