opencode-warcraft

An OpenCode plugin for structured, plan-first AI-assisted development.

Overview

Warcraft uses a plan-first workflow for AI coding assistants:

1. create a feature
2. write and review a plan
3. approve the plan
4. sync tasks
5. execute tasks through warcraft_execute

Core model

• beadsMode: "on" → bead-backed storage
• beadsMode: "off" → filesystem-backed storage
• Filesystem-backed stores live in packages/warcraft-core/src/filesystem/
• beadsMode controls storage backend only; it does not change the execution model

Installation

From npm (recommended)

Add to your project's opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["opencode-warcraft"]
}

OpenCode auto-installs npm plugins at startup via Bun.

From source (development)

git clone https://github.com/minhtri2710/opencode-warcraft.git
cd opencode-warcraft
bun install && bun run build
cd packages/opencode-warcraft
opencode plugin dev

Workflow

Planned mode

1. warcraft_feature_create({ name, request })
2. clarify as needed
3. warcraft_plan_write
4. optional warcraft_plan_read
5. warcraft_plan_approve
6. tasks auto-sync after approval
7. warcraft_execute({ task })
8. Issue the returned task() call and continue orchestration

Direct mode

For tiny work:

1. warcraft_feature_create({ name, request })
2. warcraft_task_create
3. warcraft_execute({ task })
4. Issue the returned task() call

Blocked worker resume

1. warcraft_status()
2. ask the user via question()
3. warcraft_execute({ task, continueFrom: "blocked", decision: "..." })
4. issue the returned task() call again

Tools

Current active Warcraft tools:

• warcraft_feature_create
• warcraft_feature_complete
• warcraft_plan_write
• warcraft_plan_read
• warcraft_plan_approve
• warcraft_tasks_sync
• warcraft_task_create
• warcraft_task_expand
• warcraft_task_update
• warcraft_execute
• warcraft_context_write
• warcraft_status
• warcraft_agents_md
• warcraft_doctor
• warcraft_skill
• warcraft_hashline_edit

Planning-mode delegation

Read-only exploration is still encouraged during planning.

• Delegate to Scout/Brann when you cannot name the file path upfront
• Delegate when investigation likely spans 2+ files
• “don’t execute” means “don’t implement”

E2E lanes

From packages/opencode-warcraft/:

• bun run test:e2e:smoke — default smoke coverage with no host tool prerequisites
• bun run test:e2e:host — host-backed plugin E2E; requires git and br
• bun run test:e2e:runtime — runtime/provider smoke; requires the host prerequisites first

Further reading

• docs/WARCRAFT-TOOLS.md
• ../warcraft-core/README.md
• ../warcraft-core/BEADS.md