harness-kit

claude-workflow

My personal Claude Code workflow — a reusable closed-loop engineering harness, packaged as a plugin and distributed through this repo's own marketplace. The plugin ships a bootstrapper that stamps a self-contained workflow into any repo, so each project ends up owning its own engine — no rebuilding it by hand each time.

Architecture: the engine lives in each project

plugin: harness-kit  (install once, available globally)
├── harness-init      ← bootstrapper: explore repo → stamp the workflow into it
├── dev-init          ← directory / Docker / devlog scaffold
├── coding-standards  ← engineering operating principles
└── git-commit        ← commit-message style

each project  (generated by harness-init — self-contained, no global dependency)
├── .claude/skills/harness-engineering/  ← the closed-loop ENGINE, local to this repo
├── CLAUDE.md                             ← thin: hard rules + routing table
└── .claude/skills/<prefix>-<surface>/    ← domain skills, loaded on demand

Design point: the engine is per-project, not global. The plugin ships the generator (harness-init) and the template for the engine; running it drops a tailored harness-engineering into the repo. Every project is then self-contained — clone it and the whole loop is right there, the same way a mature project keeps its own orchestrator.

The loop (run by each project's local harness-engineering, reusing the shared skills):

Intake (guardrails) → Plan (sprint contract) → Dispatch (load domain skill on demand) → Ground (verify against live code — map vs territory; the code wins) → Implement → Verify (separate generation from evaluation) → Gate (/code-review + /security-review) → Report & per-action approval

Install (marketplace + plugin)

/plugin marketplace add jacksen-ng/claude-workflow      # register the marketplace
/plugin install harness-kit@jack-workflow               # install the bootstrapper + utilities

After install, the skills are user-global (stored under ~/.claude/plugins/cache/).

Using it in a new project

1. (Optional, greenfield) dev-init — lay down the directory / Docker / devlog scaffold.
2. harness-init — explores the repo and stamps in: a local harness-engineering orchestrator, a thin CLAUDE.md, and one domain skill per surface — for your review.
3. From then on, any non-trivial task in that repo flows through its own harness-engineering.

Update loop (how edits take effect)

Plugin installs are copied to a cache, so editing this repo does not take effect automatically:

# 1. edit a skill / template
# 2. bump "version" in plugins/harness-kit/.claude-plugin/plugin.json
# 3. push to GitHub
/plugin marketplace update jack-workflow
/reload-plugins

Note: bumping the plugin updates the bootstrapper, not orchestrators already stamped into existing projects. Those are self-contained copies — re-run harness-init (or hand-edit) to refresh a project's local harness-engineering.

Layout

Path	Purpose
.claude-plugin/marketplace.json	marketplace manifest (name: jack-workflow)
plugins/harness-kit/.claude-plugin/plugin.json	plugin manifest (name: harness-kit, semver)
plugins/harness-kit/skills/*	the 4 bundled skills (harness-init, dev-init, coding-standards, git-commit)
plugins/harness-kit/skills/harness-init/SKILL.md	embeds Template A (engine) / B (CLAUDE.md) / C (domain skill) — the single source the bootstrapper stamps from