Skip to content

dynatrace-oss/opencode-coder

@dynatrace-oss/opencode-coder

OpenCode plugin for story-driven development with agents and commands.

Features

  • Beads Integration (Optional) - Local-first issue tracking with stealth mode (local-only) or team mode (git-synced)
  • Custom Agents - Four specialized agents for planning, review, task execution, and verification
  • Knowledge Base Commands - Rich command library for issue management (bd/*)
  • Skills as Commands - Skills from ai-resources/skills/ and other locations automatically available as /skills/* commands
  • Template Support - Customizable workflows and issue templates

Prerequisites

Installation

1. Configure the plugin

Add the plugin to your OpenCode configuration (~/.config/opencode/config.json):

{
  "plugins": ["@dynatrace-oss/opencode-coder"]
}

Since this package is published to GitHub Packages, you may need to configure npm to use the GitHub registry for this scope. Create or update ~/.npmrc:

@dynatrace-oss:registry=https://npm.pkg.github.com

2. Initialize your project (optional)

If you want to use beads for issue tracking, you can initialize it in your project directory using the beads CLI (bd init). This is optional - the plugin works without beads too.

Using with Beads

Beads integration is optional. You can use the plugin without beads at all. If you want to use beads, initialize it with bd init in your project directory.

Stealth Mode (Recommended default)

  • Beads files stay local to your machine (gitignored)
  • Won't affect git history or other team members
  • Perfect for: personal use, OSS contributions, teams not using beads yet
  • Use bd init --stealth to enable this mode

Team Mode

  • Beads files are committed and synced via git
  • Enables multi-device sync and team collaboration
  • Perfect for: teams adopting beads together
  • Use bd init (default) to enable this mode

aimgr Integration (Optional)

The plugin includes automatic integration with aimgr, a CLI tool for discovering and managing AI resources (commands, skills, agents).

How It Works

When the plugin starts, it automatically:

  1. Checks if ai.package.yaml exists in your project
  2. Detects if aimgr is installed on your system
  3. Initializes aimgr if available (aimgr init)
  4. Installs the opencode-coder package if available in your aimgr repository
  5. Notifies you via toast when initialization completes

All operations run in the background and won't block the plugin from loading.

Installing aimgr

To use this feature, install aimgr:

# See installation instructions
https://github.com/hk9890/ai-config-manager

Disabling Auto-Initialization

If you have aimgr installed but don't want automatic initialization:

  • Create an ai.package.yaml file in your project (even an empty one)
  • Or uninstall/remove aimgr from your PATH

The plugin will skip auto-initialization in these cases.

Benefits

  • Auto-discovery: Automatically finds relevant AI resources for your project
  • Zero-config: Works out-of-the-box if aimgr is installed
  • Non-intrusive: Fails gracefully if aimgr is not available
  • Project-specific: Each project can have its own AI resource configuration

Quick Start

With Beads

Initialize beads in your project, then track issues:

# Create your first issue
bd create "Setup project structure" --type task --priority 2

# Find available work
bd ready

# Start working on a task
bd update <id> --status in_progress

# Close a completed task
bd close <id>

Available Commands

Plugin Commands

These commands are provided by this plugin and available in OpenCode:

Command Description
/init Initialize project for opencode-coder (skill discovery, beads init, AGENTS.md creation)
/simplify Review and simplify recently changed files using the opencode-coder workflow
/opencode-coder/doctor Diagnose plugin health and configuration
/opencode-coder/status Show plugin status
/opencode-coder/report-bug Report a bug with session context
/opencode-coder/dump-session Export current session data
/opencode-coder/update-agent-md Refresh AGENTS.md after installing new resources
/opencode-coder-dev/analyze-logs Analyze OpenCode logs for errors (dev use)
/opencode-coder-dev/fix-bugs Triage and fix bugs from logs (dev use)
/opencode-coder-dev/import-tasks Import tasks from GitHub issues (dev use)
/opencode-coder-dev/release Run the release workflow (dev use)

Beads CLI Commands (requires bd installed separately)

The following are not plugin commands — they are commands from the beads CLI (bd), which must be installed separately. Agents use them as shell commands when beads is initialized in your project.

Command Description
bd create Create a new issue
bd list List issues with filters
bd ready Show issues ready to work
bd show Display issue details
bd update Update issue properties
bd close Close an issue
bd blocked Show blocked issues
bd stats Project statistics
bd export Export issues to JSONL
bd dep Manage dependencies
bd epic Create an epic with tasks
bd template Manage issue templates

Available Skills

Skills extend the agent's capabilities with specialized workflows and domain expertise.

Core Plugin Skills

Skill Description
opencode-coder Core workflow hub for planning, setup, troubleshooting, and the /simplify cleanup workflow.

Task Synchronization Skills

Bidirectional sync between beads and external task systems (GitHub, Jira, etc.).

Skill Description
task-sync System-agnostic orchestrator for task synchronization. Provides workflow guidance and delegates to backend-specific skills.
github-task-sync GitHub backend for task sync. Syncs beads with GitHub issues using gh CLI. Supports import, export, and bidirectional workflows.

Usage Examples:

Sync with GitHub
Import GitHub issues to beads
Export beads to GitHub  
Sync tasks bidirectionally

Features:

  • Import: Fetch GitHub issues into beads with automatic priority mapping
  • Export: Create GitHub issues from beads (NEW capability)
  • Bidirectional: Full two-way sync with conflict detection and resolution
  • Smart Deduplication: Never import the same issue twice
  • Label Tracking: source:external and github:<number> labels for sync direction

Prerequisites:

  • GitHub CLI (gh) authenticated: gh auth login
  • Beads initialized: bd init

For detailed workflow documentation, see the skills at ai-resources/skills/task-sync/ and ai-resources/skills/github-task-sync/.

Available Agents

Agent Role
orchestrator Planning, structure, orchestration - creates epics and tasks, delegates implementation
reviewer Reviews plans and structure (not code)
tasker Implements tasks and closes them when complete
verifier Verifies outcomes and owns acceptance review tasks

Workflow

  1. Orchestrator creates epic + tasks + acceptance review task
  2. Reviewer reviews plans and creates additional tasks/review work if needed
  3. Tasker implements tasks and closes when complete
  4. Verifier validates acceptance review tasks and closes them or creates bugs

License

MIT

About

No description, website, or topics provided.

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors