okf-harness-bootstrap
SolidBootstrap OKF Harness from Hermes Agent before a workspace-local OKF skill exists. Use when the user asks Hermes to create, find, select, repair, or enter an OKF Harness workspace. If okfh is missing, point to Universal setup. Do not use for daily workspace answers, generic Markdown editing, or non-OKF knowledge-base work.
Install
Quality Score: 79/100
Skill Content
Details
- Author
- pumblus
- Repository
- pumblus/okf-harness
- Created
- 1 months ago
- Last Updated
- 2 days ago
- Language
- TypeScript
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
okf-harness
One Door workflow for OKF Harness workspaces. Use when the user asks to set up, check, ingest into, reconcile revisions in, answer from, or graph an OKF Harness workspace. Do not use for generic Markdown editing, ordinary repository maintenance, knowledge-base tasks outside an OKF Harness workspace, repository dependency graphs, old workflow-specific skill names, or an `okfh query` command.
implementation-harness-evaluate-fit
Use when the user wants to check whether an already-installed harness is well-tuned to THIS project and fix any mismatches — phrases like "evaluate the harness fit", "does the harness suit this project", "check in on the harness", "tune the harness to the project", "the facets/floor look wrong for this repo", "/evaluate-fit". Runs a full multi-agent DEEP DIVE of the project (stack, module structure, risk profile, deploy/notify story, secret + visual surfaces), reads the CURRENT harness config, then produces ranked, evidence-backed recommendations across the ONLY customizable surfaces — the `custom/` overlay, `harness.env` knobs, and `facets.json` (`layer` vocabulary + `policy`) — and, on your approval, applies them. It NEVER edits harness mechanism (scripts/docs/dashboard) — an install stays fork-free and upgrade-clean. Ideal after a harness was scaffolded against an empty/young repo, or after the project has grown. Requires a scaffolded `.harness/`.
init-harness
One-shot initialization of a parallel-terminal Claude Code build harness in a project - a git worktree and branch per terminal, phase checkboxes as the task queue, pinned model/effort per agent, mechanical git-tag gates, hardened read/gate/log hooks, and a SQLite agent-memory shard per terminal. Use when the user says "/init-harness", "init-harness", "initialize the harness", "set up the build harness", "scaffold this project's harness", "bootstrap the agent harness", or drops in a project-context.yml and asks to initialize. Also use when a project needs multi-terminal agent orchestration with gates, or when an existing harness must be verified or repaired (hooks not firing, guards not blocking, .agents drift). Do NOT use for adding a single agent or skill to an existing project.