[GH-ISSUE #27] OpenCode support plz

kerem commented

2026-03-03 18:50:01 +03:00

Owner

Originally created by @Realtyxxx on GitHub (Jan 13, 2026).
Original GitHub issue: https://github.com/OthmanAdi/planning-with-files/issues/27

as the name

Originally created by @Realtyxxx on GitHub (Jan 13, 2026). Original GitHub issue: https://github.com/OthmanAdi/planning-with-files/issues/27 as the name

kerem closed this issue

2026-03-03 18:50:02 +03:00

kerem commented

2026-03-03 18:50:03 +03:00

Author

Owner

@OthmanAdi commented on GitHub (Jan 13, 2026):

im on it

@OthmanAdi commented on GitHub (Jan 13, 2026): im on it

kerem commented

2026-03-03 18:50:03 +03:00

Author

Owner

@Realtyxxx commented on GitHub (Jan 13, 2026):

In my current usage, I’ve noticed the following issues: when skills are placed under ~/.config/opencode/skill, they can be discovered during search, but they are not actually respected or applied at runtime. Additionally, if oh-my-opencode is enabled, the planning-with-files skill cannot be recognized at all. It seems like this skill might be blocked or disabled in that setup.

@Realtyxxx commented on GitHub (Jan 13, 2026): In my current usage, I’ve noticed the following issues: when skills are placed under `~/.config/opencode/skill`, they can be discovered during search, but they are not actually respected or applied at runtime. Additionally, if `oh-my-opencode` is enabled, the `planning-with-files` skill cannot be recognized at all. It seems like this skill might be blocked or disabled in that setup.

kerem commented

2026-03-03 18:50:03 +03:00

Author

Owner

@flyGetHu commented on GitHub (Jan 15, 2026):

Looking forward to your support

@flyGetHu commented on GitHub (Jan 15, 2026): Looking forward to your support

kerem commented

2026-03-03 18:50:03 +03:00

Author

Owner

@OthmanAdi commented on GitHub (Jan 17, 2026):

Hi there,

Apologies for the delayed response! I'm excited about adding OpenCode support to planning-with-files.

Current IDE Support

Right now, planning-with-files officially supports:

✅ Claude Code - Full support (native plugin)
✅ Cursor - Full support (via .cursor/rules)
🔄 Kilocode - In progress (PR #30 pending review)

OpenCode Support - Need Your Help!

I'm absolutely willing to add OpenCode support, but I need some information from the community to do it right:

What I Need to Know

OpenCode Repository/Documentation
- Link to OpenCode's official repo or website
- Documentation on how OpenCode handles skills/plugins/rules
Configuration Method
- Does OpenCode use SKILL.md format (like Claude Code)?
- Does it use a rules file (like Cursor)?
- Does it have its own plugin system?
Installation Path
- Where would the skill files need to be located?
- What's the expected directory structure?
Your OpenCode Version
- Which version of OpenCode are you using?
- Is it the latest stable release?

Quick Assessment

If OpenCode:

Uses SKILL.md format → Already supported! Just copy files to OpenCode's skills directory
Uses rules like Cursor → I can create .opencode/rules configuration
Has custom format → I'll need to see documentation to implement it

How You Can Help

Please comment here with:

1. OpenCode repository: [link]
2. OpenCode version you're using: [version]
3. How you currently add skills/rules to OpenCode: [description]

With this info, I can:

Add proper OpenCode configuration
Create installation docs
Test the integration
Release it in the next version (2.3.0)

Timeline

Once I have the information:

Quick Win (if compatible): Hours to days
Custom Implementation: 1-2 weeks

Commitment

I'm committed to multi-IDE support. We already have Cursor working, Kilocode coming soon, and I want OpenCode to be next!

Your turn: Please drop the OpenCode details in a comment, and I'll prioritize getting this implemented!

Thanks for the feature request!

Best regards,
Ahmad

@OthmanAdi commented on GitHub (Jan 17, 2026): Hi there, Apologies for the delayed response! I'm excited about adding OpenCode support to planning-with-files. ## Current IDE Support Right now, planning-with-files officially supports: - ✅ **Claude Code** - Full support (native plugin) - ✅ **Cursor** - Full support (via `.cursor/rules`) - 🔄 **Kilocode** - In progress (PR #30 pending review) ## OpenCode Support - Need Your Help! I'm absolutely willing to add OpenCode support, but I need some information from the community to do it right: ### What I Need to Know 1. **OpenCode Repository/Documentation** - Link to OpenCode's official repo or website - Documentation on how OpenCode handles skills/plugins/rules 2. **Configuration Method** - Does OpenCode use SKILL.md format (like Claude Code)? - Does it use a rules file (like Cursor)? - Does it have its own plugin system? 3. **Installation Path** - Where would the skill files need to be located? - What's the expected directory structure? 4. **Your OpenCode Version** - Which version of OpenCode are you using? - Is it the latest stable release? ### Quick Assessment If OpenCode: - **Uses SKILL.md format** → Already supported! Just copy files to OpenCode's skills directory - **Uses rules like Cursor** → I can create `.opencode/rules` configuration - **Has custom format** → I'll need to see documentation to implement it ### How You Can Help Please comment here with: ``` 1. OpenCode repository: [link] 2. OpenCode version you're using: [version] 3. How you currently add skills/rules to OpenCode: [description] ``` With this info, I can: - Add proper OpenCode configuration - Create installation docs - Test the integration - Release it in the next version (2.3.0) ## Timeline Once I have the information: - **Quick Win** (if compatible): Hours to days - **Custom Implementation**: 1-2 weeks ## Commitment I'm committed to multi-IDE support. We already have Cursor working, Kilocode coming soon, and I want OpenCode to be next! --- **Your turn:** Please drop the OpenCode details in a comment, and I'll prioritize getting this implemented! Thanks for the feature request! Best regards, Ahmad

kerem commented

2026-03-03 18:50:03 +03:00

Author

Owner

@OthmanAdi commented on GitHub (Jan 17, 2026):

✅ OpenCode Support Added in v2.3.0!

I studied the obra/superpowers repository to understand the REAL OpenCode skill system, and I've added full support for planning-with-files.

How OpenCode Skills Work

OpenCode supports skills in three locations with priority:

Project skills: .opencode/skills/ (highest priority)
Personal skills: ~/.config/opencode/skills/ (medium priority)
Superpowers skills: ~/.config/opencode/superpowers/skills/ (lowest priority)

Installation (Two Options)

Option 1: Global Installation

mkdir -p ~/.config/opencode/skills
cd ~/.config/opencode/skills
git clone https://github.com/OthmanAdi/planning-with-files.git

Option 2: Project-Specific Installation

mkdir -p .opencode/skills
cd .opencode/skills
git clone https://github.com/OthmanAdi/planning-with-files.git

Usage

With superpowers plugin:

Use the use_skill tool with skill_name: "planning-with-files"

Without superpowers:
Read the skill manually:

cat ~/.config/opencode/skills/planning-with-files/planning-with-files/SKILL.md

oh-my-opencode Configuration

@Realtyxxx - You mentioned oh-my-opencode blocking. Here's the fix:

Check your ~/.config/opencode/oh-my-opencode.json and ensure planning-with-files is NOT in the disabled_skills array:

{
  "disabled_skills": []
}

If it's listed there, remove it and restart OpenCode.

Documentation

Full documentation available:

.opencode/INSTALL.md - Detailed installation
docs/opencode.md - OpenCode integration guide

What's Included in v2.3.0

✅ Real OpenCode skill installation instructions
✅ Global and project-specific installation paths
✅ oh-my-opencode compatibility notes
✅ Superpowers plugin integration
✅ Codex support also added (bonus!)

Research Sources

This implementation is based on real analysis of:

obra/superpowers OpenCode plugin
OpenCode INSTALL.md
OpenCode skill resolution priority system

Thanks

@Realtyxxx - Your feedback about ~/.config/opencode/skill path and oh-my-opencode blocking was spot-on. Thank you for the detailed info!

Let me know if you encounter any issues with the OpenCode setup!

Ahmad

@OthmanAdi commented on GitHub (Jan 17, 2026): ## ✅ OpenCode Support Added in v2.3.0! I studied the [obra/superpowers](https://github.com/obra/superpowers) repository to understand the REAL OpenCode skill system, and I've added full support for planning-with-files. ### How OpenCode Skills Work OpenCode supports skills in three locations with priority: 1. **Project skills:** `.opencode/skills/` (highest priority) 2. **Personal skills:** `~/.config/opencode/skills/` (medium priority) 3. **Superpowers skills:** `~/.config/opencode/superpowers/skills/` (lowest priority) ### Installation (Two Options) #### Option 1: Global Installation ```bash mkdir -p ~/.config/opencode/skills cd ~/.config/opencode/skills git clone https://github.com/OthmanAdi/planning-with-files.git ``` #### Option 2: Project-Specific Installation ```bash mkdir -p .opencode/skills cd .opencode/skills git clone https://github.com/OthmanAdi/planning-with-files.git ``` ### Usage **With superpowers plugin:** ``` Use the use_skill tool with skill_name: "planning-with-files" ``` **Without superpowers:** Read the skill manually: ```bash cat ~/.config/opencode/skills/planning-with-files/planning-with-files/SKILL.md ``` ### oh-my-opencode Configuration @Realtyxxx - You mentioned oh-my-opencode blocking. Here's the fix: Check your `~/.config/opencode/oh-my-opencode.json` and ensure planning-with-files is NOT in the `disabled_skills` array: ```json { "disabled_skills": [] } ``` If it's listed there, remove it and restart OpenCode. ### Documentation Full documentation available: - [.opencode/INSTALL.md](.opencode/INSTALL.md) - Detailed installation - [docs/opencode.md](docs/opencode.md) - OpenCode integration guide ### What's Included in v2.3.0 - ✅ Real OpenCode skill installation instructions - ✅ Global and project-specific installation paths - ✅ oh-my-opencode compatibility notes - ✅ Superpowers plugin integration - ✅ Codex support also added (bonus!) ### Research Sources This implementation is based on real analysis of: - [obra/superpowers OpenCode plugin](https://github.com/obra/superpowers/blob/main/.opencode/plugin/superpowers.js) - [OpenCode INSTALL.md](https://github.com/obra/superpowers/blob/main/.opencode/INSTALL.md) - OpenCode skill resolution priority system ### Thanks @Realtyxxx - Your feedback about `~/.config/opencode/skill` path and oh-my-opencode blocking was spot-on. Thank you for the detailed info! --- Let me know if you encounter any issues with the OpenCode setup! Ahmad

kerem commented

2026-03-03 18:50:03 +03:00

Author

Owner

@Roy-Tu commented on GitHub (Jan 18, 2026):

Hi, I ran into the same situation and found a workaround. (for the new release v2.3.0, still I have some bugs that cannot detect skills in opencode)

The Issue: Skill Not Detected in OpenCode

Currently, the opencode/SKILL.md appears to be strictly tailored for the Claude format.
Even with the correct directory structure (planning-with-files/planning-with-files/SKILL.md), OpenCode fails to recognize/load the skill entirely because of the specific hooks in the frontmatter.
The complex configuration below prevents the skill from being initialized in OpenCode environments:

---
name: planning-with-files
version: "2.3.0"
description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
user-invocable: true
allowed-tools:
  - Read
  - Write
  - Edit
  - Bash
  - Glob
  - Grep
  - WebFetch
  - WebSearch
hooks:
  PreToolUse:
    - matcher: "Write|Edit|Bash|Read|Glob|Grep"
      hooks:
        - type: command
          command: "cat task_plan.md 2>/dev/null | head -30 || true"
  PostToolUse:
    - matcher: "Write|Edit"
      hooks:
        - type: command
          command: "echo '[planning-with-files] File updated. If this completes a phase, update task_plan.md status.'"
  Stop:
    - hooks:
        - type: command
          command: |
            if command -v pwsh &> /dev/null && [[ "$OSTYPE" == "msys" || "$OSTYPE" == "win32" || "$OS" == "Windows_NT" ]]; then
              pwsh -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.ps1" 2>/dev/null || powershell -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.ps1" 2>/dev/null || bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.sh"
            else
              bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.sh"
            fi
---

Temporary Solution

I found that stripping the frontmatter down to just the essential metadata allows OpenCode to recognize and execute the skill(albeit without the auto-hooks):

---
name: planning-with-files
version: "2.3.0"
description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.

Potential Long-term Fix (Plugin Architecture)

While OpenCode doesn't parse the hooks inside the Markdown frontmatter, this automation logic is likely achievable via the OpenCode Plugin architecture (reference: https://opencode.ai/docs/plugins/).

I believe we can make this fully compatible. I'd be happy to help with the implementation if needed!

@Roy-Tu commented on GitHub (Jan 18, 2026): Hi, I ran into the same situation and found a workaround. (for the new release v2.3.0, still I have some bugs that cannot detect skills in opencode) ### The Issue: Skill Not Detected in OpenCode Currently, the `opencode/SKILL.md` appears to be strictly tailored for the Claude format. Even with the correct directory structure (`planning-with-files/planning-with-files/SKILL.md`), OpenCode **fails to recognize/load the skill** entirely because of the specific hooks in the frontmatter. The complex configuration below prevents the skill from being initialized in OpenCode environments: ```yaml --- name: planning-with-files version: "2.3.0" description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear. user-invocable: true allowed-tools: - Read - Write - Edit - Bash - Glob - Grep - WebFetch - WebSearch hooks: PreToolUse: - matcher: "Write|Edit|Bash|Read|Glob|Grep" hooks: - type: command command: "cat task_plan.md 2>/dev/null | head -30 || true" PostToolUse: - matcher: "Write|Edit" hooks: - type: command command: "echo '[planning-with-files] File updated. If this completes a phase, update task_plan.md status.'" Stop: - hooks: - type: command command: | if command -v pwsh &> /dev/null && [[ "$OSTYPE" == "msys" || "$OSTYPE" == "win32" || "$OS" == "Windows_NT" ]]; then pwsh -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.ps1" 2>/dev/null || powershell -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.ps1" 2>/dev/null || bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.sh" else bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.sh" fi --- ``` ### Temporary Solution I found that stripping the frontmatter down to just the essential metadata allows OpenCode to recognize and execute the skill(albeit without the auto-hooks): ```yaml --- name: planning-with-files version: "2.3.0" description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear. ``` ### Potential Long-term Fix (Plugin Architecture) While OpenCode doesn't parse the hooks inside the Markdown frontmatter, this automation logic is likely achievable via the OpenCode Plugin architecture (reference: https://opencode.ai/docs/plugins/). I believe we can make this fully compatible. I'd be happy to help with the implementation if needed!

kerem commented

2026-03-03 18:50:03 +03:00

Author

Owner

@OthmanAdi commented on GitHub (Jan 18, 2026):

Hi, I ran into the same situation and found a workaround. (for the new release v2.3.0, still I have some bugs that cannot detect skills in opencode)

The Issue: Skill Not Detected in OpenCode

Currently, the opencode/SKILL.md appears to be strictly tailored for the Claude format. Even with the correct directory structure (planning-with-files/planning-with-files/SKILL.md), OpenCode fails to recognize/load the skill entirely because of the specific hooks in the frontmatter. The complex configuration below prevents the skill from being initialized in OpenCode environments:

name: planning-with-files
version: "2.3.0"
description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
user-invocable: true
allowed-tools:

Read

Write

Edit

Bash

Glob

Grep

WebFetch

WebSearch
hooks:
PreToolUse:

matcher: "Write|Edit|Bash|Read|Glob|Grep"
hooks:

type: command
command: "cat task_plan.md 2>/dev/null | head -30 || true"
PostToolUse:

matcher: "Write|Edit"
hooks:

type: command
command: "echo '[planning-with-files] File updated. If this completes a phase, update task_plan.md status.'"
Stop:

hooks:

type: command
command: |
if command -v pwsh &> /dev/null && ; then
pwsh -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.ps1" 2>/dev/null || powershell -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.ps1" 2>/dev/null || bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.sh"
else
bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.sh"
fi

Temporary Solution

I found that stripping the frontmatter down to just the essential metadata allows OpenCode to recognize and execute the skill(albeit without the auto-hooks):

name: planning-with-files
version: "2.3.0"
description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.

Potential Long-term Fix (Plugin Architecture)

While OpenCode doesn't parse the hooks inside the Markdown frontmatter, this automation logic is likely achievable via the OpenCode Plugin architecture (reference: https://opencode.ai/docs/plugins/).

I believe we can make this fully compatible. I'd be happy to help with the implementation if needed!

absolutely! hit me with a PR let me review it and deliver the fix. thanks alot!

@OthmanAdi commented on GitHub (Jan 18, 2026): > Hi, I ran into the same situation and found a workaround. (for the new release v2.3.0, still I have some bugs that cannot detect skills in opencode) > > ### The Issue: Skill Not Detected in OpenCode > Currently, the `opencode/SKILL.md` appears to be strictly tailored for the Claude format. Even with the correct directory structure (`planning-with-files/planning-with-files/SKILL.md`), OpenCode **fails to recognize/load the skill** entirely because of the specific hooks in the frontmatter. The complex configuration below prevents the skill from being initialized in OpenCode environments: > > --- > name: planning-with-files > version: "2.3.0" > description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear. > user-invocable: true > allowed-tools: > - Read > - Write > - Edit > - Bash > - Glob > - Grep > - WebFetch > - WebSearch > hooks: > PreToolUse: > - matcher: "Write|Edit|Bash|Read|Glob|Grep" > hooks: > - type: command > command: "cat task_plan.md 2>/dev/null | head -30 || true" > PostToolUse: > - matcher: "Write|Edit" > hooks: > - type: command > command: "echo '[planning-with-files] File updated. If this completes a phase, update task_plan.md status.'" > Stop: > - hooks: > - type: command > command: | > if command -v pwsh &> /dev/null && [[ "$OSTYPE" == "msys" || "$OSTYPE" == "win32" || "$OS" == "Windows_NT" ]]; then > pwsh -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.ps1" 2>/dev/null || powershell -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.ps1" 2>/dev/null || bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.sh" > else > bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.sh" > fi > --- > ### Temporary Solution > I found that stripping the frontmatter down to just the essential metadata allows OpenCode to recognize and execute the skill(albeit without the auto-hooks): > > --- > name: planning-with-files > version: "2.3.0" > description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear. > ### Potential Long-term Fix (Plugin Architecture) > While OpenCode doesn't parse the hooks inside the Markdown frontmatter, this automation logic is likely achievable via the OpenCode Plugin architecture (reference: https://opencode.ai/docs/plugins/). > > I believe we can make this fully compatible. I'd be happy to help with the implementation if needed! absolutely! hit me with a PR let me review it and deliver the fix. thanks alot!

Rows
Columns

[GH-ISSUE #27] OpenCode support plz #20

Current IDE Support

OpenCode Support - Need Your Help!

What I Need to Know

Quick Assessment

How You Can Help

Timeline

Commitment

✅ OpenCode Support Added in v2.3.0!

How OpenCode Skills Work

Installation (Two Options)

Option 1: Global Installation

Option 2: Project-Specific Installation

Usage

oh-my-opencode Configuration

Documentation

What's Included in v2.3.0

Research Sources

Thanks

The Issue: Skill Not Detected in OpenCode

Temporary Solution

Potential Long-term Fix (Plugin Architecture)

The Issue: Skill Not Detected in OpenCode

Temporary Solution

Potential Long-term Fix (Plugin Architecture)