How to Fork and Customize the i‑have‑adhd Skill for Your Organization

Fork the ayghri/i-have-adhd repository, edit skills/i-have-adhd/SKILL.md to modify the ten‑rule response style, publish your fork with a unique name, and swap the plugin in your AI runtime to replace the default behavior.

The i‑have‑adhd skill is an open‑source AI assistant customization that enforces ADHD‑friendly response patterns across multiple runtimes including Claude Code, Codex, Pi, OMP, and OpenCode. Because the skill uses a single canonical definition consumed by all platforms, you can create an organization‑specific version by forking the repository and modifying one authoritative file. This guide walks through the complete workflow based on the actual source code structure in ayghri/i-have-adhd.

Why Fork Instead of Configure?

The i‑have‑adhd skill architecture separates behavior from packaging. The ten‑rule response logic lives exclusively in skills/i-have-adhd/SKILL.md, while runtime‑specific plugin manifests (.claude-plugin/plugin.json, package.json, opencode.json) merely reference that file. This design means:

• One edit to SKILL.md propagates to every supported runtime
• No code changes are required to adapt the skill for internal use
• Your fork becomes a drop‑in replacement for the upstream plugin

According to the source code, the manifests "do not contain the rule logic themselves; they simply point to the skill file." By publishing a fork with its own URL, the manifests automatically resolve to your customized rules.

Step 1: Fork the Repository on GitHub

Create your own copy of the codebase to modify independently.

1. Navigate to https://github.com/ayghri/i-have-adhd
2. Click Fork in the top‑right corner
3. Select your organization or personal account as the destination

This gives you a private https://github.com/<your-org>/i-have-adhd repository.

Step 2: Clone and Locate the Skill Definition

The canonical skill definition lives at a predictable path regardless of runtime.

git clone https://github.com/<your-org>/i-have-adhd.git
cd i-have-adhd

Open skills/i-have-adhd/SKILL.md — this is the only file you need to edit to change the skill's behavior.

What SKILL.md Contains

Per the source analysis, this file encodes the ten‑rule response style that the skill enforces at runtime. Rules cover structure (tl;dr first), formatting (bullet lists, short paragraphs), and tone (direct, no filler). You can:

• Reword existing rules for your organization's voice
• Add organization‑specific directives (e.g., "Always cite internal ticket numbers")
• Remove rules that conflict with your workflows

Step 3: Customize the Skill Rules

Edit skills/i-have-adhd/SKILL.md in your preferred editor. The file uses markdown with rule headings that the runtime parses to guide model behavior.

Example modification adding an organizational rule:

## Org‑Specific Rule: Cite Source Documentation

When referencing internal systems, include a link to the relevant Confluence page.

Commit your changes:

git add skills/i-have-adhd/SKILL.md
git commit -m "Add organization‑specific guidance and tone adjustments"
git push origin main

Step 4: Update Plugin Manifests (Optional)

If you want your fork to appear with a distinct name in marketplace listings, modify the runtime‑specific manifests:

File	Purpose	What to Change
.claude-plugin/plugin.json	Claude Code plugin metadata	name field
package.json	NPM‑style manifest for Node‑based runtimes	name and repository fields
opencode.json	OpenCode runtime configuration	id and repository fields

The manifests reference the repository URL, so as long as the URL points to your fork, the runtime will load your customized SKILL.md.

Step 5: Publish Your Forked Skill

Push your repository and make it discoverable. The runtime adapters discover plugins from marketplace listings or direct Git URLs.

# Ensure your fork is public or accessible to your organization's runtimes

git push origin main

For internal use, you can reference the fork directly by Git URL without publishing to a public marketplace.

Step 6: Swap the Runtime Plugin

Remove the upstream i‑have‑adhd plugin and install your fork. The README.md "Tune it" section documents this workflow for each runtime.

For Claude Code:

# Remove upstream version

claude plugin uninstall i-have-adhd
claude plugin marketplace remove i-have-adhd

# Add your fork to the marketplace

claude plugin marketplace add <your-org>/i-have-adhd

# Install the customized version

claude plugin install i-have-adhd@i-have-adhd

# Restart Claude Code for changes to take effect

For Other Runtimes

The same pattern applies with runtime‑specific CLI prefixes:

• Codex: codex plugin uninstall i-have-adhd → codex plugin install ...
• Pi, OMP: Use the respective plugin management commands documented in INSTALL.md

Verification: Test Your Customized Skill

After restarting your AI runtime, invoke a task that would normally trigger the skill. Verify that:

• New rules appear in the model's response structure
• Removed rules are absent from the behavior
• Custom directives are followed consistently

The runtime reads SKILL.md at invocation time, so subsequent pushes to your fork take effect on the next conversation without reinstallation.

Key Files in the Repository

Understanding the codebase structure helps with advanced customization:

• skills/i-have-adhd/SKILL.md — Canonical skill definition; the single source of truth for all ten response rules
• README.md — Quick‑start guide with the "Tune it" section for plugin swapping
• AGENTS.md — Runtime compatibility matrix and manifest file listings
• INSTALL.md — Platform‑specific installation instructions
• .claude-plugin/plugin.json — Claude Code manifest pointing to the skill repository
• package.json — Node‑ecosystem manifest for cross‑runtime compatibility
• opencode.json — OpenCode runtime configuration

Summary

• Fork ayghri/i-have-adhd to create an independent, modifiable copy
• Edit skills/i-have-adhd/SKILL.md — the only file controlling response behavior
• Customize rules, tone, and add organization‑specific directives as needed
• Publish your fork under a unique name or Git URL
• Swap the upstream plugin for your fork in each target runtime
• Verify that all supported platforms (Claude Code, Codex, Pi, OMP, OpenCode) adopt the customized behavior automatically

Frequently Asked Questions

Can I customize the skill without forking?

No. The architecture requires a repository URL to resolve the SKILL.md file. While you could theoretically host a modified skill elsewhere, the plugin manifests expect a Git repository structure. Forking is the supported path for organization‑specific customization.

Will my customizations work across all runtimes simultaneously?

Yes. Because every runtime reads the same SKILL.md file from your fork's URL, a single edit propagates to Claude Code, Codex, Pi, OMP, and OpenCode automatically. The runtime‑specific manifests only differ in how they reference the repository, not in behavior implementation.

What happens if the upstream repository updates?

Your fork remains independent. You can pull upstream changes via standard Git workflows (git remote add upstream, git fetch upstream, git merge), but apply them selectively to preserve your customizations. The plugin system does not auto‑update; you control when to integrate upstream improvements.

Do I need to modify code to add organizational rules?

No code modifications are required. The SKILL.md file is parsed as configuration by the runtimes. Simply add markdown‑formatted rules to this file, commit, and push. The runtime extracts and enforces these rules at conversation time without compilation or deployment steps.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}