harness-init

To bootstrap a docs-driven orchestration workflow, run this skill once in your repo to stamp a self-contained harness layer. It generates a project-local orchestrator, CLAUDE.md, domain skills, and docs/specs scaffolds under .claude and docs/specs.

A harness orchestrator is a project-local engine that drives a docs-driven loop with recall, intake, decomposition, a five-doc spec gate, and retrospective. It manages repo automation by reconciling live code with existing context to produce deploy-ready scaffolds.

Bootstrapping a harness will not overwrite existing files. If the repo already has skills, CLAUDE.md, or docs, the bootstrap process inventories and reconciles them with the new harness context instead of overwriting your current configurations.

Yes, you can scaffold domain skills per surface. The bootstrap process generates specific domain skills for frontend, backend, infra, data, and db surfaces using ground-truth anchors to ensure accurate routing and execution across your project.

Setting up a repo orchestration harness adds enforcement hooks like install-guard and retrospect-guard. These hooks ensure compliance with the generated CLAUDE.md rules and maintain the integrity of the five-doc spec gate workflow.

You do not need a five-doc spec gate beforehand. The bootstrap generates the docs/specs templates required for the mandatory five-doc gate, creating the complete scaffold structure needed to start your docs-driven development loop immediately.