> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qredence.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# harness-engineering plugin

> Audit repository legibility, scaffold durable repo docs, and add validation lanes and drift controls so coding agents work with stronger guardrails.

Use **harness-engineering** when a repository needs clearer maps, validation lanes, and drift control. It audits repo legibility and scaffolds durable repo docs so agents can work with stronger guardrails.

Reach for [`meta-harness`](/qredence-plugins/plugins/meta-harness) instead when the goal is benchmarked `harness.py` optimization.

## Quick start

Run from the repo root:

```bash theme={null}
uv run python plugins/harness-engineering/scripts/audit_repo_harness.py --repo . --format markdown
uv run python plugins/harness-engineering/scripts/audit_repo_harness.py --repo . --format json
uv run python plugins/harness-engineering/scripts/scaffold_harness_docs.py --repo . --dry-run
uv run python plugins/harness-engineering/scripts/scaffold_harness_docs.py --repo . --write
```

In Claude Code:

```bash theme={null}
claude --plugin-dir ./plugins/harness-engineering
/harness-engineering:harness-engineering
```

## When to reach for meta-harness

* You are optimizing one benchmarked LLM task.
* The main artifact is a candidate `harness.py`.
* You need Pareto / frontier tracking across prompt or retrieval variants.
* The bottleneck is evaluation quality, not repo operating clarity.

## Validation

```bash theme={null}
uv run pytest plugins/harness-engineering/tests
uv run pytest tests/test_plugin_catalogue.py
uv run python plugins/harness-engineering/scripts/audit_repo_harness.py --repo . --format markdown
uv run python plugins/harness-engineering/scripts/scaffold_harness_docs.py --repo . --dry-run
```