- JavaScript 44.8%
- HTML 30.4%
- Shell 13%
- PowerShell 6.4%
- TypeScript 5.4%
An earlier commit (
|
||
|---|---|---|
| .claude | ||
| .claude-plugin | ||
| agents | ||
| commands | ||
| hooks | ||
| skills | ||
| templates/.claude | ||
| .gitignore | ||
| .mcp.json | ||
| bootstrap.ps1 | ||
| bootstrap.sh | ||
| CLAUDE.md | ||
| device-config.json.example | ||
| README.md | ||
Claude Code Workflow Bindings
Claude Code plugin for the opencode-workflow-core 7-phase software development workflow, ported from opencode.
This session drives the workflow directly — @conductor is a stateless
status/recovery-check subagent, not something you hand the whole session to.
See the plugin's CLAUDE.md (auto-loaded into every session) for the actual
phase-by-phase routing and gate protocol.
Install
Prerequisites
- Claude Code installed
- Git access to your Forgejo instance
One-liner
curl -fsSL https://git.firmanserver.com/firman-admin/claude-workflow-bindings/raw/branch/main/bootstrap.sh | bash
Or manual
# Clone to Claude plugins directory
git clone https://git.firmanserver.com/firman-admin/claude-workflow-bindings.git \
~/.claude/plugins/claude-workflow-plugin
# Install via Claude Code
claude plugin install claude-workflow-plugin@~/.claude/plugins/claude-workflow-plugin
Windows (PowerShell)
iex ((New-Object Net.WebClient).DownloadString('https://git.firmanserver.com/firman-admin/claude-workflow-bindings/raw/branch/main/bootstrap.ps1'))
Per-project setup
cp -r ~/.claude/plugins/claude-workflow-plugin/templates/.claude ./project/.claude
Contents
| Path | Purpose |
|---|---|
.claude-plugin/plugin.json |
Plugin manifest |
agents/*.md |
11 subagent definitions |
commands/*.md |
3 slash commands |
skills/*/SKILL.md |
10 skills |
hooks/hooks.json |
Lifecycle hooks |
.mcp.json |
Recommended MCP servers |
templates/.claude/ |
Per-project config templates |
bootstrap.sh |
macOS/Linux installer |
bootstrap.ps1 |
Windows installer |
Usage
Start Claude Code in any project and just describe the feature or bug — the
session follows the phase table in CLAUDE.md directly and performs every
[HALT] gate itself via AskUserQuestion. There's no single command that
"starts" the workflow; it starts the moment you describe work.
Use individual agents/commands as needed:
| Intent | Action |
|---|---|
| Status / recovery check | @conductor |
| Map codebase | @codebase-explorer |
| Design architecture | @architect |
| Plan tasks | @planner |
| Run TDD cycle | /tdd-runner |
| Review spec | @spec-reviewer |
| Review quality | @quality-reviewer |
| Create PR | /shipper |
| Debug bug | /debugger |
| Check status | /workflow-status |
| Verify completion | /verification-gate |
Forgejo Integration
Issues and PRs use curl + API only — no fj CLI dependency anywhere in this
plugin (skills that mentioned fj have been converted to the same curl/API
calls used elsewhere):
- Phase 3: After plan approval, planner creates one issue per task
- Phase 4: On task completion, orchestrator comments with commit SHA
- Phase 6: On PR merge, shipper closes all task issues
See ~/.claude/workflow-core/reference/forgejo-api.md for full API reference
(vendored by bootstrap.sh/bootstrap.ps1 — run bootstrap before relying on it).
Plugin Reference
For plugin development, see the Claude Code plugin documentation.