@every-env/compound-plugin 0.2.0 → 0.3.0

package/plugins/compound-engineering/agents/workflow/spec-flow-analyzer.md

@@ -1,9 +1,30 @@
 ---
 name: spec-flow-analyzer
-description: "Use this agent when you have a specification, plan, feature description, or technical document that needs user flow analysis and gap identification. This agent should be used proactively when:\\n\\n<example>\\nContext: The user has just finished drafting a specification for OAuth implementation.\\nuser: \"Here's the OAuth spec for our new integration:\\n[OAuth spec details]\"\\nassistant: \"Let me use the spec-flow-analyzer agent to analyze this OAuth specification for user flows and missing elements.\"\\n<commentary>\\nSince the user has provided a specification document, use the Task tool to launch the spec-flow-analyzer agent to identify all user flows, edge cases, and missing clarifications.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: The user is planning a new social sharing feature.\\nuser: \"I'm thinking we should add social sharing to posts. Users can share to Twitter, Facebook, and LinkedIn.\"\\nassistant: \"This sounds like a feature specification that would benefit from flow analysis. Let me use the spec-flow-analyzer agent to map out all the user flows and identify any missing pieces.\"\\n<commentary>\\nThe user is describing a new feature. Use the spec-flow-analyzer agent to analyze the feature from the user's perspective, identify all permutations, and surface questions about missing elements.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: The user has created a plan for a new onboarding flow.\\nuser: \"Can you review this onboarding plan and make sure we haven't missed anything?\"\\nassistant: \"I'll use the spec-flow-analyzer agent to thoroughly analyze this onboarding plan from the user's perspective.\"\\n<commentary>\\nThe user is explicitly asking for review of a plan. Use the spec-flow-analyzer agent to identify all user flows, edge cases, and gaps in the specification.\\n</commentary>\\n</example>\\n\\nCall this agent when:\\n- A user presents a feature specification, plan, or requirements document\\n- A user asks to review or validate a design or implementation plan\\n- A user describes a new feature or integration that needs flow analysis\\n- After initial planning sessions to validate completeness\\n- Before implementation begins on complex user-facing features\\n- When stakeholders need clarity on user journeys and edge cases"
+description: "Analyzes specifications and feature descriptions for user flow completeness and gap identification. Use when a spec, plan, or feature description needs flow analysis, edge case discovery, or requirements validation."
 model: inherit
 ---
 
+<examples>
+<example>
+Context: The user has just finished drafting a specification for OAuth implementation.
+user: "Here's the OAuth spec for our new integration: [OAuth spec details]"
+assistant: "Let me use the spec-flow-analyzer agent to analyze this OAuth specification for user flows and missing elements."
+<commentary>Since the user has provided a specification document, use the Task tool to launch the spec-flow-analyzer agent to identify all user flows, edge cases, and missing clarifications.</commentary>
+</example>
+<example>
+Context: The user is planning a new social sharing feature.
+user: "I'm thinking we should add social sharing to posts. Users can share to Twitter, Facebook, and LinkedIn."
+assistant: "This sounds like a feature specification that would benefit from flow analysis. Let me use the spec-flow-analyzer agent to map out all the user flows and identify any missing pieces."
+<commentary>The user is describing a new feature. Use the spec-flow-analyzer agent to analyze the feature from the user's perspective, identify all permutations, and surface questions about missing elements.</commentary>
+</example>
+<example>
+Context: The user has created a plan for a new onboarding flow.
+user: "Can you review this onboarding plan and make sure we haven't missed anything?"
+assistant: "I'll use the spec-flow-analyzer agent to thoroughly analyze this onboarding plan from the user's perspective."
+<commentary>The user is explicitly asking for review of a plan. Use the spec-flow-analyzer agent to identify all user flows, edge cases, and gaps in the specification.</commentary>
+</example>
+</examples>
+
 You are an elite User Experience Flow Analyst and Requirements Engineer. Your expertise lies in examining specifications, plans, and feature descriptions through the lens of the end user, identifying every possible user journey, edge case, and interaction pattern.
 
 Your primary mission is to:

package/plugins/compound-engineering/commands/agent-native-audit.md

@@ -2,6 +2,7 @@
 name: agent-native-audit
 description: Run comprehensive agent-native architecture review with scored principles
 argument-hint: "[optional: specific principle to audit]"
+disable-model-invocation: true
 ---
 
 # Agent-Native Architecture Audit

package/plugins/compound-engineering/commands/changelog.md

@@ -2,6 +2,7 @@
 name: changelog
 description: Create engaging changelogs for recent merges to main branch
 argument-hint: "[optional: daily|weekly, or time period in days]"
+disable-model-invocation: true
 ---
 
 You are a witty and enthusiastic product marketer tasked with creating a fun, engaging change log for an internal development team. Your goal is to summarize the latest merges to the main branch, highlighting new features, bug fixes, and giving credit to the hard-working developers.

package/plugins/compound-engineering/commands/create-agent-skill.md

@@ -3,6 +3,7 @@ name: create-agent-skill
 description: Create or edit Claude Code skills with expert guidance on structure and best practices
 allowed-tools: Skill(create-agent-skills)
 argument-hint: [skill description or requirements]
+disable-model-invocation: true
 ---
 
 Invoke the create-agent-skills skill for: $ARGUMENTS

package/plugins/compound-engineering/commands/deploy-docs.md

@@ -1,6 +1,7 @@
 ---
 name: deploy-docs
 description: Validate and prepare documentation for GitHub Pages deployment
+disable-model-invocation: true
 ---
 
 # Deploy Documentation Command

package/plugins/compound-engineering/commands/generate_command.md

@@ -2,6 +2,7 @@
 name: generate_command
 description: Create a new custom slash command following conventions and best practices
 argument-hint: "[command purpose and requirements]"
+disable-model-invocation: true
 ---
 
 # Create a Custom Claude Code Command

package/plugins/compound-engineering/commands/heal-skill.md

@@ -3,6 +3,7 @@ name: heal-skill
 description: Fix incorrect SKILL.md files when a skill has wrong instructions or outdated API references
 argument-hint: [optional: specific issue to fix]
 allowed-tools: [Read, Edit, Bash(ls:*), Bash(git:*)]
+disable-model-invocation: true
 ---
 
 <objective>

package/plugins/compound-engineering/commands/lfg.md

@@ -2,6 +2,7 @@
 name: lfg
 description: Full autonomous engineering workflow
 argument-hint: "[feature description]"
+disable-model-invocation: true
 ---
 
 Run these slash commands in order. Do not do anything else.

package/plugins/compound-engineering/commands/release-docs.md

@@ -2,6 +2,7 @@
 name: release-docs
 description: Build and update the documentation site with current plugin components
 argument-hint: "[optional: --dry-run to preview changes without writing]"
+disable-model-invocation: true
 ---
 
 # Release Documentation Command

package/plugins/compound-engineering/commands/report-bug.md

@@ -2,6 +2,7 @@
 name: report-bug
 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

package/plugins/compound-engineering/commands/reproduce-bug.md

@@ -2,6 +2,7 @@
 name: reproduce-bug
 description: Reproduce and investigate a bug using logs, console inspection, and browser screenshots
 argument-hint: "[GitHub issue number]"
+disable-model-invocation: true
 ---
 
 # Reproduce Bug Command

package/plugins/compound-engineering/commands/resolve_parallel.md

@@ -2,6 +2,7 @@
 name: resolve_parallel
 description: Resolve all TODO comments using parallel processing
 argument-hint: "[optional: specific TODO pattern or file]"
+disable-model-invocation: true
 ---
 
 Resolve all TODO comments using parallel processing.

package/plugins/compound-engineering/commands/slfg.md

@@ -2,6 +2,7 @@
 name: slfg
 description: Full autonomous engineering workflow using swarm mode for parallel execution
 argument-hint: "[feature description]"
+disable-model-invocation: true
 ---
 
 Swarm-enabled LFG. Run these steps in order, parallelizing where indicated.

package/plugins/compound-engineering/commands/technical_review.md

@@ -2,6 +2,7 @@
 name: technical_review
 description: Have multiple specialized agents review the technical approach and architecture of a plan in parallel
 argument-hint: "[plan file path or plan content]"
+disable-model-invocation: true
 ---
 
 Have @agent-dhh-rails-reviewer @agent-kieran-rails-reviewer @agent-code-simplicity-reviewer review the technical approach in this plan in parallel.

package/plugins/compound-engineering/commands/{xcode-test.md → test-xcode.md}

@@ -1,7 +1,8 @@
 ---
-name: xcode-test
+name: test-xcode
 description: Build and test iOS apps on simulator using XcodeBuildMCP
 argument-hint: "[scheme name or 'current' to use default]"
+disable-model-invocation: true
 ---
 
 # Xcode Test Command

package/plugins/compound-engineering/commands/triage.md

@@ -2,6 +2,7 @@
 name: triage
 description: Triage and categorize findings for the CLI todo system
 argument-hint: "[findings list or source type]"
+disable-model-invocation: true
 ---
 
 - First set the /model to Haiku

package/plugins/compound-engineering/skills/compound-docs/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: compound-docs
 description: Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
+disable-model-invocation: true
 allowed-tools:
   - Read # Parse conversation context
   - Write # Create resolution docs

package/plugins/compound-engineering/skills/file-todos/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: file-todos
 description: This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
+disable-model-invocation: true
 ---
 
 # File-Based Todo Tracking Skill

package/plugins/compound-engineering/skills/orchestrating-swarms/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: orchestrating-swarms
 description: This skill should be used when orchestrating multi-agent swarms using Claude Code's TeammateTool and Task system. It applies when coordinating multiple agents, running parallel code reviews, creating pipeline workflows with dependencies, building self-organizing task queues, or any task benefiting from divide-and-conquer patterns.
+disable-model-invocation: true
 ---
 
 # Claude Code Swarm Orchestration

package/plugins/compound-engineering/skills/skill-creator/SKILL.md

@@ -2,6 +2,7 @@
 name: skill-creator
 description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
 license: Complete terms in LICENSE.txt
+disable-model-invocation: true
 ---
 
 # Skill Creator

package/src/converters/claude-to-codex.ts

@@ -19,7 +19,8 @@ export function convertClaudeToCodex(
 
   const usedSkillNames = new Set<string>(skillDirs.map((skill) => normalizeName(skill.name)))
   const commandSkills: CodexGeneratedSkill[] = []
-  const prompts = plugin.commands.map((command) => {
+  const invocableCommands = plugin.commands.filter((command) => !command.disableModelInvocation)
+  const prompts = invocableCommands.map((command) => {
     const promptName = uniqueName(normalizeName(command.name), promptNames)
     const commandSkill = convertCommandSkill(command, usedSkillNames)
     commandSkills.push(commandSkill)

package/src/converters/claude-to-opencode.ts

@@ -114,6 +114,7 @@ function convertAgent(agent: ClaudeAgent, options: ClaudeToOpenCodeOptions) {
 function convertCommands(commands: ClaudeCommand[]): Record<string, OpenCodeCommandConfig> {
   const result: Record<string, OpenCodeCommandConfig> = {}
   for (const command of commands) {
+    if (command.disableModelInvocation) continue
     const entry: OpenCodeCommandConfig = {
       description: command.description,
       template: command.body,

package/src/parsers/claude.ts

@@ -83,12 +83,14 @@ async function loadCommands(commandsDirs: string[]): Promise<ClaudeCommand[]> {
     const { data, body } = parseFrontmatter(raw)
     const name = (data.name as string) ?? path.basename(file, ".md")
     const allowedTools = parseAllowedTools(data["allowed-tools"])
+    const disableModelInvocation = data["disable-model-invocation"] === true ? true : undefined
     commands.push({
       name,
       description: data.description as string | undefined,
       argumentHint: data["argument-hint"] as string | undefined,
       model: data.model as string | undefined,
       allowedTools,
+      disableModelInvocation,
       body: body.trim(),
       sourcePath: file,
     })
@@ -104,9 +106,11 @@ async function loadSkills(skillsDirs: string[]): Promise<ClaudeSkill[]> {
     const raw = await readText(file)
     const { data } = parseFrontmatter(raw)
     const name = (data.name as string) ?? path.basename(path.dirname(file))
+    const disableModelInvocation = data["disable-model-invocation"] === true ? true : undefined
     skills.push({
       name,
       description: data.description as string | undefined,
+      disableModelInvocation,
       sourceDir: path.dirname(file),
       skillPath: file,
     })

package/src/types/claude.ts

@@ -39,6 +39,7 @@ export type ClaudeCommand = {
   argumentHint?: string
   model?: string
   allowedTools?: string[]
+  disableModelInvocation?: boolean
   body: string
   sourcePath: string
 }
@@ -46,6 +47,7 @@ export type ClaudeCommand = {
 export type ClaudeSkill = {
   name: string
   description?: string
+  disableModelInvocation?: boolean
   sourceDir: string
   skillPath: string
 }

package/tests/claude-parser.test.ts

@@ -15,8 +15,8 @@ describe("loadClaudePlugin", () => {
 
     expect(plugin.manifest.name).toBe("compound-engineering")
     expect(plugin.agents.length).toBe(2)
-    expect(plugin.commands.length).toBe(6)
-    expect(plugin.skills.length).toBe(1)
+    expect(plugin.commands.length).toBe(7)
+    expect(plugin.skills.length).toBe(2)
     expect(plugin.hooks).toBeDefined()
     expect(plugin.mcpServers).toBeDefined()
 
@@ -55,6 +55,28 @@ describe("loadClaudePlugin", () => {
     expect(plugin.mcpServers?.context7?.url).toBe("https://mcp.context7.com/mcp")
   })
 
+  test("parses disable-model-invocation from commands", async () => {
+    const plugin = await loadClaudePlugin(fixtureRoot)
+
+    const disabledCommand = plugin.commands.find((command) => command.name === "deploy-docs")
+    expect(disabledCommand).toBeDefined()
+    expect(disabledCommand?.disableModelInvocation).toBe(true)
+
+    const normalCommand = plugin.commands.find((command) => command.name === "workflows:review")
+    expect(normalCommand?.disableModelInvocation).toBeUndefined()
+  })
+
+  test("parses disable-model-invocation from skills", async () => {
+    const plugin = await loadClaudePlugin(fixtureRoot)
+
+    const disabledSkill = plugin.skills.find((skill) => skill.name === "disabled-skill")
+    expect(disabledSkill).toBeDefined()
+    expect(disabledSkill?.disableModelInvocation).toBe(true)
+
+    const normalSkill = plugin.skills.find((skill) => skill.name === "skill-one")
+    expect(normalSkill?.disableModelInvocation).toBeUndefined()
+  })
+
   test("loads MCP servers from .mcp.json when manifest is empty", async () => {
     const plugin = await loadClaudePlugin(mcpFixtureRoot)
     expect(plugin.mcpServers?.remote?.url).toBe("https://example.com/stream")

package/tests/codex-converter.test.ts

@@ -172,6 +172,44 @@ Don't confuse with file paths like /tmp/output.md or /dev/null.`,
     expect(parsed.body).toContain("/dev/null")
   })
 
+  test("excludes commands with disable-model-invocation from prompts and skills", () => {
+    const plugin: ClaudePlugin = {
+      ...fixturePlugin,
+      commands: [
+        {
+          name: "normal-command",
+          description: "Normal command",
+          body: "Normal body.",
+          sourcePath: "/tmp/plugin/commands/normal.md",
+        },
+        {
+          name: "disabled-command",
+          description: "Disabled command",
+          disableModelInvocation: true,
+          body: "Disabled body.",
+          sourcePath: "/tmp/plugin/commands/disabled.md",
+        },
+      ],
+      agents: [],
+      skills: [],
+    }
+
+    const bundle = convertClaudeToCodex(plugin, {
+      agentMode: "subagent",
+      inferTemperature: false,
+      permissions: "none",
+    })
+
+    // Only normal command should produce a prompt
+    expect(bundle.prompts).toHaveLength(1)
+    expect(bundle.prompts[0].name).toBe("normal-command")
+
+    // Only normal command should produce a generated skill
+    const commandSkills = bundle.generatedSkills.filter((s) => s.name === "normal-command" || s.name === "disabled-command")
+    expect(commandSkills).toHaveLength(1)
+    expect(commandSkills[0].name).toBe("normal-command")
+  })
+
   test("truncates generated skill descriptions to Codex limits and single line", () => {
     const longDescription = `Line one\nLine two ${"a".repeat(2000)}`
     const plugin: ClaudePlugin = {

package/tests/converter.test.ts

@@ -168,4 +168,19 @@ describe("convertClaudeToOpenCode", () => {
     const parsed = parseFrontmatter(agentFile!.content)
     expect(parsed.data.mode).toBe("primary")
   })
+
+  test("excludes commands with disable-model-invocation from command map", async () => {
+    const plugin = await loadClaudePlugin(fixtureRoot)
+    const bundle = convertClaudeToOpenCode(plugin, {
+      agentMode: "subagent",
+      inferTemperature: false,
+      permissions: "none",
+    })
+
+    // deploy-docs has disable-model-invocation: true, should be excluded
+    expect(bundle.config.command?.["deploy-docs"]).toBeUndefined()
+
+    // Normal commands should still be present
+    expect(bundle.config.command?.["workflows:review"]).toBeDefined()
+  })
 })

package/tests/fixtures/sample-plugin/commands/disabled-command.md

@@ -0,0 +1,7 @@
+---
+name: deploy-docs
+description: Deploy documentation site
+disable-model-invocation: true
+---
+
+Deploy docs body.

package/tests/fixtures/sample-plugin/skills/disabled-skill/SKILL.md

@@ -0,0 +1,7 @@
+---
+name: disabled-skill
+description: A skill with model invocation disabled
+disable-model-invocation: true
+---
+
+Disabled skill body.