feat: make skills platform-agnostic across coding agents

plugins/compound-engineering/AGENTS.md

@@ -84,6 +84,18 @@ When adding or modifying skills, verify compliance with the skill spec:
 - [ ] When a skill needs to ask the user a question, instruct use of the platform's blocking question tool and name the known equivalents (`AskUserQuestion` in Claude Code, `request_user_input` in Codex, `ask_user` in Gemini)
 - [ ] Include a fallback for environments without a question tool (e.g., present numbered options and wait for the user's reply before proceeding)
 
+### Cross-Platform Task Tracking
+
+- [ ] When a skill needs to create or track tasks, describe the intent (e.g., "create a task list") and name the known equivalents (`TaskCreate`/`TaskUpdate`/`TaskList` in Claude Code, `update_plan` in Codex)
+- [ ] Do not reference `TodoWrite` or `TodoRead` — these are legacy Claude Code tools replaced by `TaskCreate`/`TaskUpdate`/`TaskList`
+- [ ] When a skill dispatches sub-agents, prefer parallel execution but include a sequential fallback for platforms that do not support parallel dispatch
+
+### Script Path References in Skills
+
+- [ ] In bash code blocks, reference co-located scripts using relative paths (e.g., `bash scripts/my-script ARG`) — not `${CLAUDE_PLUGIN_ROOT}` or other platform-specific variables
+- [ ] All platforms resolve script paths relative to the skill's directory; no env var prefix is needed
+- [ ] Always also include a markdown link to the script (e.g., `[scripts/my-script](scripts/my-script)`) so the agent can locate and read it
+
 ### Cross-Platform Reference Rules
 
 This plugin is authored once, then converted for other agent platforms. Commands and agents are transformed during that conversion, but `plugin.skills` are usually copied almost exactly as written.

plugins/compound-engineering/README.md

@@ -94,16 +94,15 @@ Core workflow commands use `ce:` prefix to unambiguously identify them as compou
 | `/changelog` | Create engaging changelogs for recent merges |
 | `/create-agent-skill` | Create or edit Claude Code skills |
 | `/generate_command` | Generate new slash commands |
-| `/heal-skill` | Fix skill documentation issues |
 | `/sync` | Sync Claude Code config across machines |
-| `/report-bug` | Report a bug in the plugin |
+| `/report-bug-ce` | Report a bug in the compound-engineering plugin |
 | `/reproduce-bug` | Reproduce bugs using logs and console |
 | `/resolve_parallel` | Resolve TODO comments in parallel |
 | `/resolve_pr_parallel` | Resolve PR comments in parallel |
 | `/resolve-todo-parallel` | Resolve todos in parallel |
 | `/triage` | Triage and prioritize issues |
 | `/test-browser` | Run browser tests on PR-affected pages |
-| `/xcode-test` | Build and test iOS apps on simulator |
+| `/test-xcode` | Build and test iOS apps on simulator |
 | `/feature-video` | Record video walkthroughs and add to PR description |
 
 ## Skills

plugins/compound-engineering/skills/report-bug/SKILL.md → plugins/compound-engineering/skills/report-bug-ce/SKILL.md

@@ -1,17 +1,17 @@
 ---
-name: report-bug
+name: report-bug-ce
 description: Report a bug in the compound-engineering plugin
 argument-hint: "[optional: brief description of the bug]"
 disable-model-invocation: true
 ---
 
-# Report a Compounding Engineering Plugin Bug
+# Report a Compound Engineering Plugin Bug
 
-Report bugs encountered while using the compound-engineering plugin. This command gathers structured information and creates a GitHub issue for the maintainer.
+Report bugs encountered while using the compound-engineering plugin. This skill gathers structured information and creates a GitHub issue for the maintainer.
 
 ## Step 1: Gather Bug Information
 
-Use the AskUserQuestion tool to collect the following information:
+Ask the user the following questions (using the platform's blocking question tool — e.g., `AskUserQuestion` in Claude Code, `request_user_input` in Codex, `ask_user` in Gemini — or present numbered options and wait for a reply):
 
 **Question 1: Bug Category**
 - What type of issue are you experiencing?
@@ -39,18 +39,25 @@ Use the AskUserQuestion tool to collect the following information:
 
 ## Step 2: Collect Environment Information
 
-Automatically gather:
-```bash
-# Get plugin version
-cat ~/.claude/plugins/installed_plugins.json 2>/dev/null | grep -A5 "compound-engineering" | head -10 || echo "Plugin info not found"
-
-# Get Claude Code version
-claude --version 2>/dev/null || echo "Claude CLI version unknown"
+Automatically gather environment details. Detect the coding agent platform and collect what is available:
 
-# Get OS info
+**OS info (all platforms):**
+```bash
 uname -a
 ```
 
+**Plugin version:** Read the plugin manifest or installed plugin metadata. Common locations:
+- Claude Code: `~/.claude/plugins/installed_plugins.json`
+- Codex: `.codex/plugins/` or project config
+- Other platforms: check the platform's plugin registry
+
+**Agent CLI version:** Run the platform's version command:
+- Claude Code: `claude --version`
+- Codex: `codex --version`
+- Other platforms: use the appropriate CLI version flag
+
+If any of these fail, note "unknown" and continue — do not block the report.
+
 ## Step 3: Format the Bug Report
 
 Create a well-structured bug report with:
@@ -63,8 +70,9 @@ Create a well-structured bug report with:
 
 ## Environment
 
-- **Plugin Version:** [from installed_plugins.json]
-- **Claude Code Version:** [from claude --version]
+- **Plugin Version:** [from plugin manifest/registry]
+- **Agent Platform:** [e.g., Claude Code, Codex, Copilot, Pi, Kilo]
+- **Agent Version:** [from CLI version command]
 - **OS:** [from uname]
 
 ## What Happened
@@ -83,16 +91,14 @@ Create a well-structured bug report with:
 
 ## Error Messages
 
-```
 [Any error output]
-```
 
 ## Additional Context
 
 [Any other relevant information]
 
 ---
-*Reported via `/report-bug` command*
+*Reported via `/report-bug-ce` skill*
 ```
 
 ## Step 4: Create GitHub Issue
@@ -125,7 +131,7 @@ After the issue is created:
 ## Output Format
 
 ```
-✅ Bug report submitted successfully!
+Bug report submitted successfully!
 
 Issue: https://github.com/EveryInc/compound-engineering-plugin/issues/[NUMBER]
 Title: [compound-engineering] Bug: [description]
@@ -136,16 +142,16 @@ The maintainer will review your report and respond as soon as possible.
 
 ## Error Handling
 
-- If `gh` CLI is not authenticated: Prompt user to run `gh auth login` first
-- If issue creation fails: Display the formatted report so user can manually create the issue
-- If required information is missing: Re-prompt for that specific field
+- If `gh` CLI is not installed or not authenticated: prompt the user to install/authenticate first
+- If issue creation fails: display the formatted report so the user can manually create the issue
+- If required information is missing: re-prompt for that specific field
 
 ## Privacy Notice
 
-This command does NOT collect:
+This skill does NOT collect:
 - Personal information
 - API keys or credentials
-- Private code from your projects
+- Private code from projects
 - File paths beyond basic OS info
 
 Only technical information about the bug is included in the report.

plugins/compound-engineering/skills/resolve-pr-parallel/SKILL.md

@@ -12,7 +12,7 @@ Resolve all unresolved PR review comments by spawning parallel agents for each t
 
 ## Context Detection
 
-Claude Code automatically detects git context:
+Detect git context from the current working directory:
 - Current branch and associated PR
 - All PR comments and review threads
 - Works with any PR by specifying the number
@@ -21,10 +21,10 @@ Claude Code automatically detects git context:
 
 ### 1. Analyze
 
-Fetch unresolved review threads using the GraphQL script:
+Fetch unresolved review threads using the GraphQL script at [scripts/get-pr-comments](scripts/get-pr-comments):
 
 ```bash
-bash ${CLAUDE_PLUGIN_ROOT}/skills/resolve-pr-parallel/scripts/get-pr-comments PR_NUMBER
+bash scripts/get-pr-comments PR_NUMBER
 ```
 
 This returns only **unresolved, non-outdated** threads with file paths, line numbers, and comment bodies.
@@ -37,31 +37,25 @@ gh api repos/{owner}/{repo}/pulls/PR_NUMBER/comments
 
 ### 2. Plan
 
-Create a TodoWrite list of all unresolved items grouped by type:
+Create a task list of all unresolved items grouped by type (e.g., `TaskCreate` in Claude Code, `update_plan` in Codex):
 - Code changes requested
 - Questions to answer
 - Style/convention fixes
 - Test additions needed
 
 ### 3. Implement (PARALLEL)
 
-Spawn a `pr-comment-resolver` agent for each unresolved item in parallel.
+Spawn a `compound-engineering:workflow:pr-comment-resolver` agent for each unresolved item.
 
-If there are 3 comments, spawn 3 agents:
-
-1. Task pr-comment-resolver(comment1)
-2. Task pr-comment-resolver(comment2)
-3. Task pr-comment-resolver(comment3)
-
-Always run all in parallel subagents/Tasks for each Todo item.
+If there are 3 comments, spawn 3 agents — one per comment. Prefer running all agents in parallel; if the platform does not support parallel dispatch, run them sequentially.
 
 ### 4. Commit & Resolve
 
 - Commit changes with a clear message referencing the PR feedback
-- Resolve each thread programmatically:
+- Resolve each thread programmatically using [scripts/resolve-pr-thread](scripts/resolve-pr-thread):
 
 ```bash
-bash ${CLAUDE_PLUGIN_ROOT}/skills/resolve-pr-parallel/scripts/resolve-pr-thread THREAD_ID
+bash scripts/resolve-pr-thread THREAD_ID
 ```
 
 - Push to remote
@@ -71,7 +65,7 @@ bash ${CLAUDE_PLUGIN_ROOT}/skills/resolve-pr-parallel/scripts/resolve-pr-thread
 Re-fetch comments to confirm all threads are resolved:
 
 ```bash
-bash ${CLAUDE_PLUGIN_ROOT}/skills/resolve-pr-parallel/scripts/get-pr-comments PR_NUMBER
+bash scripts/get-pr-comments PR_NUMBER
 ```
 
 Should return an empty array `[]`. If threads remain, repeat from step 1.

plugins/compound-engineering/skills/resolve-todo-parallel/SKILL.md

@@ -16,19 +16,13 @@ If any todo recommends deleting, removing, or gitignoring files in `docs/brainst
 
 ### 2. Plan
 
-Create a TodoWrite list of all unresolved items grouped by type. Make sure to look at dependencies that might occur and prioritize the ones needed by others. For example, if you need to change a name, you must wait to do the others. Output a mermaid flow diagram showing how we can do this. Can we do everything in parallel? Do we need to do one first that leads to others in parallel? I'll put the to-dos in the mermaid diagram flow-wise so the agent knows how to proceed in order.
+Create a task list of all unresolved items grouped by type (e.g., `TaskCreate` in Claude Code, `update_plan` in Codex). Analyze dependencies and prioritize items that others depend on. For example, if a rename is needed, it must complete before dependent items. Output a mermaid flow diagram showing execution order — what can run in parallel, and what must run first.
 
 ### 3. Implement (PARALLEL)
 
-Spawn a pr-comment-resolver agent for each unresolved item in parallel.
+Spawn a `compound-engineering:workflow:pr-comment-resolver` agent for each unresolved item.
 
-So if there are 3 comments, it will spawn 3 pr-comment-resolver agents in parallel. Like this:
-
-1. Task pr-comment-resolver(comment1)
-2. Task pr-comment-resolver(comment2)
-3. Task pr-comment-resolver(comment3)
-
-Always run all in parallel subagents/Tasks for each Todo item.
+If there are 3 items, spawn 3 agents — one per item. Prefer running all agents in parallel; if the platform does not support parallel dispatch, run them sequentially respecting the dependency order from step 2.
 
 ### 4. Commit & Resolve
 
@@ -40,7 +34,7 @@ GATE: STOP. Verify that todos have been resolved and changes committed. Do NOT p
 
 ### 5. Compound on Lessons Learned
 
-Run the `ce:compound` skill to document what was learned from resolving the todos.
+Load the `ce:compound` skill to document what was learned from resolving the todos.
 
 The todo resolutions often surface patterns, recurring issues, or architectural insights worth capturing. This step ensures that knowledge compounds rather than being lost.