The planning documents for the behavioral evaluations workflow are
contributor-side working documents and should not land in main. Remove
them from the working tree and add gitignore rules so regenerated copies
do not reappear in future PRs.
Covers Cursor, Windsurf, GitHub Copilot, Codex, Gemini, Aider, and
Continue, plus CLAUDE.local.md and AGENTS.local.md, so contributors
using any of those tools don't accidentally commit their private
context.
opencode-power-pack bundles eleven Claude Code skills as an OpenCode plugin
under one config line, with each skill also exposed as a slash command.
Skills (by category):
Review
code-review multi-agent PR review with cross-check pass and
concrete reproduction scenarios
security-review OWASP-bucketed three-stage filtering with mandatory
PoC per finding
Feature dev
feature-dev seven-phase guided workflow
code-explorer deep codebase analysis sub-task
code-architect decisive architecture blueprint sub-task
code-reviewer two-pass adversarial review sub-task
Design
frontend-design distinctive, production-grade UI generation
Authoring
mcp-builder build high-quality MCP servers (Python or TypeScript)
skill-creator author new SKILL.md files
Project memory
agents-md-improver audit and update AGENTS.md / CLAUDE.md
agents-md-revise capture session learnings into the rules file
Architecture:
- .opencode/plugins/opencode-power-pack.js auto-registers skills/ via
config.skills.paths.push() (live config singleton modification, pattern
adapted from obra/superpowers).
- skills/<name>/SKILL.md hold the workflows the model executes.
- commands/<name>.md ship physical slash command files that inline the
full SKILL.md content, so the model receives the actual workflow as
its prompt rather than a meta-instruction. Symlinked into
~/.config/opencode/commands/ during install.
Almost all skill content is ported or translated from upstream Anthropic
projects (claude-code/plugins, skills, claude-code-security-review,
claude-plugins-official). The plugin loader pattern is adapted from
obra/superpowers. See README.md -> Acknowledgments for per-skill
attribution; each SKILL.md frontmatter also carries a license field
naming its specific upstream.