@cristochang/spec-integration

Passive workflow reminders when working with OpenCode specs

Compatibility Warning

This plugin is version-locked to opencode.

It relies on internal Spec capabilities provided at runtime by opencode core. Do not expect compatibility across major opencode versions.

Current compatibility: opencode >=0.9.0 <0.10.0

What it does

Shows you which spec is currently active for your session
Warns you when making file edits while a spec is still in "pending" status
Reminds you of the spec's scope and success criteria when making changes

What it doesn't do

Does not block any operations (passive mode only)
Does not modify tool arguments or behavior
Does not persist any data to disk
Does not create files or directories

Installation

npm install @cristochang/spec-integration

Add to your .opencode/config.json:

{
  "plugin": [
    "@cristochang/spec-integration@latest"
  ]
}

Configuration

Add an experimental.specIntegration section to your .opencode/config.json:

{
  "experimental": {
    "specIntegration": {
      "enabled": true,
      "mode": "passive",
      "warningCooldown": 60000
    }
  }
}

Options

Option	Type	Default	Description
`enabled`	boolean	`true`	Enable or disable the plugin
`mode`	`"passive"`	`"passive"`	Warning mode (only "passive" is supported)
`warningCooldown`	number	`60000`	Milliseconds between warnings for the same session

How it works

The plugin monitors the following tools and shows reminders when an active spec exists:

edit - Editing existing files
write - Creating new files
multiedit - Batch edits
patch - Patch operations
bash - Shell commands

Failure Strategy

If the Spec capability is not available (e.g., running on an incompatible opencode version), the plugin silently disables itself and will not interfere with your workflow.

When to use this plugin

Use it when:

You want to maintain awareness of your active spec while coding
You're working in a team that uses specs for task tracking
You want gentle reminders about spec boundaries without enforced constraints

Don't use it when:

You prefer complete autonomy without any workflow suggestions
You're doing exploratory coding that doesn't align with spec-based workflows
You find the reminders distracting (just set enabled: false)

License

MIT