A config-driven Claude Code harness for agentic project delivery. Oskr (from Ratatoskr, the squirrel-courier of Yggdrasil) lets Claude Code skills and subagents drive a project's full workflow — research → planning → implementation → review — against a project board.
oskr ships as a Claude Code plugin. Add the marketplace, install, and reload:
/plugin marketplace add WillyDallas/oskr
/plugin install oskr@oskr-marketplace
/reload-plugins
To pull later changes: /plugin marketplace update oskr-marketplace →
/plugin update oskr@oskr-marketplace → /reload-plugins. Updates are manual:
Claude Code does not notify you of a new oskr version, and a release only shows
up once version in plugin.json is bumped. For local development
against a checkout, launch with claude --plugin-dir <path-to-repo> instead.
Starting from zero — creating the workspace, wiring secrets, onboarding your first project — is walked through in docs/getting-started.md.
Work flows across eight board states — Backlog → Scoping → Planning → Plan
Approval → Ready → In Progress → In Review → Done — with one skill at each and
three human gates (scope, plan-approval, the merge). The per-state runbook is
docs/board-flow.md; the design rationale is
docs/design/pipeline-redesign.md.
Board operations run behind one interface — the blacksmith — so the same
workflow runs on GitHub Projects v2 or self-hosted Forgejo, selected per
project by a forge key in harness-config.json. See
docs/design/blacksmith.md.
Each managed project has a harness-config.json at its root (or under
.claude/). See docs/harness-config.schema.md.
skills/,agents/— the Claude Code skills and subagents the harness ships.bin/— the shell glue skills shell out to (the blacksmith adapter and the board dispatcher live here).docs/design/,docs/research/— architecture decisions and grounding.
MIT. See LICENSE.