workflows

Workaholic

The development workflows we use at qmu, written down so our coding agents can run them the way we do. They're tuned to how we work, so they may not fit everyone, and they'll keep changing as we do. We keep it public so the people we work with can share the same base.

Concretely, it's a cross-agent distribution of structured development workflows and engineering-standard skills: ticket-driven development, AI-collaborative exploration, and the engineering-policy index (the planning / design / implementation / operation skills, mirrored from qmu.co.jp). It's richest on Claude Code (a plugin marketplace: slash commands, hooks, /trip Agent Teams); the same skills install on Codex, OpenCode, and 40+ other agents via the Agent Skills standard. Authored once under plugins/, generated into portable artifacts under outputs/.

[!WARNING] This drives git on your behalf. Workaholic lets your coding agent autonomously create branches, commit, amend, push, and open pull requests. Review the plugin/skill descriptions below before installing so you know what to expect.

Quick Start (Claude Code)

claude
/plugin marketplace add qmu/workaholic

Enable the plugins you want after installation. Auto update is recommended. For Codex, OpenCode, and other agents, see Use with other coding agents below.

Use with other coding agents

Workaholic follows the cross-agent Agent Skills standard. What's portable:

• Policy skills (planning / design / implementation / operation) — the engineering-policy index (pure prose, self-contained): title, one-line summary, and canonical qmu.co.jp link per policy, organized into the 企画 / 設計 / 実装 / 運用 pillars. Available on every Agent-Skills agent.
• write-release-note — release-note structure guidance (pure prose).
• Workflows — create-ticket, drive, report, ship, catch, mission as agent-neutral skills (trip stays Claude-only; it needs Agent Teams). On non-Claude agents the workflow runs the same steps without Claude's parallel subagents/AskUserQuestion — see each skill's Agent Compatibility note.
• Open Knowledge Format (OKF v0.1) — two surfaces, no install needed. The committed outputs/okf/ bundle exposes the four pillars' policy hard copies to any OKF reader straight from the repo path; and every project using the plugin gets an OKF-compatible .workaholic/ tree — generated documents carry type frontmatter and the workflows regenerate the index.md hierarchy (entry point: .workaholic/index.md) before each knowledge commit.

Install matrix

Agent	How
Claude Code	/plugin marketplace add qmu/workaholic (slash commands /ticket, /drive, /report, /ship, /trip)
OpenAI Codex	codex plugin marketplace add qmu/workaholic --ref main codex plugin add workaholic@workaholic codex plugin add workflows@workaholic
Cursor / OpenCode / Pi / 50+	npx skills add qmu/workaholic (exposes workaholic + workflows)

How the workflows reach other agents

The workflow skills share helper scripts across plugins/workaholic via the Claude-only ${CLAUDE_PLUGIN_ROOT} token, so they are not self-contained in source. scripts/build-plugins generates self-contained copies (each skill bundling its own scripts, references rewritten to relative paths) and assembles one neutral, committed plugin under outputs/workflows/. That single dir serves every non-Claude agent: Codex via .agents/plugins/marketplace.json (and the co-located .codex-plugin/plugin.json), and OpenCode/Cursor/40+ via the skills CLI reading the workflows entry in .claude-plugin/marketplace.json. Regenerate after changing a workaholic workflow skill:

node scripts/build-plugins/build.mjs   # regenerate outputs/workflows artifacts (no args = full build)
node scripts/build-plugins/verify.mjs  # assert every script reference resolves

The plugins/workaholic source stays Claude-Code-only (metadata.internal: true, ${CLAUDE_PLUGIN_ROOT}); the committed outputs/workflows/ artifacts are the public, portable versions, kept in sync by the Outputs Freshness CI check. The workaholic plugin's commands/hooks/Agent Teams remain Claude-Code-only.

The plugin

workaholic is a single plugin combining ticket-driven development (TiDD), AI-collaborative exploration, and context-aware reporting/shipping, plus the engineering-policy index. It auto-detects your development context from the current branch pattern.