moai-meta-harness

# moai-meta-harness (DEPRECATED — redirect to v4)

> **DEPRECATION NOTICE** — This legacy 7-Phase meta-harness is
> **superseded by the v4 harness Builder** (`/moai:harness <natural-language
> request>`). The v4 design replaces the static 7-Phase workflow with:
>
> - An **orchestrator-direct 4-phase Builder** (ANALYZE -> PLAN -> GENERATE ->
>   ACTIVATE) that holds the plan in Claude's session context and can call
>   AskUserQuestion at the PLAN->GENERATE approval gate (first-class boundary).
> - A **manifest-driven dynamic-workflow Runner** (`harness-<name>-run.js`) that
>   reads `manifest.json` and dispatches specialists per their declared
>   `primitive` (sub-agent / dynamic-workflow / worktree / /goal /
>   adversarial-fan-out) — no heuristic re-derivation.
> - **Conditional sub-agent-granular worktree isolation** (no mandatory
>   top-level worktree; worktree only for conflict-prone parallel generation).
> - **Signal-driven phase synthesis** (not a fixed pipeline); the evaluator is
>   conditional (skipped for tasks within the model's solo reliable range).
>
> **To create a new harness**: issue `/moai:harness <natural-language request>`
> (e.g., `/moai:harness build a harness for my-project's API development`). The
> orchestrator runs Context-First Discovery on the request, derives a harness
> `<name>`, and enters the Builder. Do NOT use the 7-Phase workflow below for
> new harness creation.
>
> **What is preserved here**: the 7-Phase body below is retained as the
> **redirect source** for backward-compat — so existing invocation paths that
> reference the legacy workflow land on a deprecation notice + redirect rather
> than a dead link. The 7-Phase content is historical reference material, NOT
> active workflow. The revfactory 7-Phase residual grep excludes this body
> precisely because it IS the redirect source.

<!-- @MX:NOTE: [AUTO] V3R4 contract SUPERSEDED — the original V3R4 contract preserved this skill body unchanged per the harness foundation policy §10 exclusion #10 (text annotation only, no behavioral change). That contract is hereby EXPLICITLY SUPERSEDED by the v4 harness redesign: the body is converted to a v4 redirect. Rationale for supersession: (1) the V3R4 contract protected against behavioral change, but v4 IS a deliberate behavioral change — the 7-Phase workflow is retired in favor of the orchestrator-direct Builder + manifest-driven Runner; (2) preserving the body unchanged would leave a dead-path 7-Phase workflow that contradicts the v4 design; (3) the AskUserQuestion-only contract (REQ-HRN-FND-015) is itself preserved verbatim under v4 — any generated subagent under .claude/agents/harness/ still MUST NOT invoke AskUserQuestion (this is reaffirmed, not weakened). The supersession is narrow: the 7-Phase workflow is retired; the AskUserQuestion boundary + namespace separation + Apache-2.0 attribution are all preserved. Cross-reference: the v4 design's Migration Path (revfactory 7-Phase -> v4 mapping) in the companion harness-builder.md workflow. -->

<!-- ATTRIBUTION
Original work: revfactory/harness (https://github.com/revfactory/harness)
License: Apache License 2.0
Adaptations: 7-Phase workflow integrated with MoAI agent ecosystem (manager-*, expert-*, sync-auditor)
NOTICE: This file contains modifications. See the harness policy for derivation history. The 7-Phase workflow below is superseded by the v4 Builder; it is retained as the redirect source for backward-compat.
-->

> **Apache 2.0 Attribution**: Adapted from [revfactory/harness](https://github.com/revfactory/harness) (Apache License 2.0). The 7-Phase workflow below is a MoAI adaptation of the upstream 6-Phase + Evolution Mechanism. See `.claude/rules/moai/NOTICE.md` for the full third-party notices and the harness policy for derivation history. **The v4 Builder (the replacement) is documented in `.claude/skills/moai/workflows/harness-builder.md`.**

---

## v4 Redirect (the active path)

**New harness creation**: `/moai:harness <natural-language request>`

This routes to the v4 Builder (orchestrator-direct). The Builder:

1. **Context-First Discovery** on the request (extract domain / goal / constraints / scope).
2. **AskUserQuestion Socratic rounds** if clarity <100%; **derives** harness `<name>` from confirmed intent.
3. **Explicit approval gate** (AskUserQuestion, PLAN->GENERATE boundary).
4. **ANALYZE / PLAN / GENERATE / ACTIVATE** as orchestrator-direct phases.
5. Emits 5 artifact types: entry command, Runner Workflow, specialists, companion skills, `manifest.json`.

**Harness lifecycle** (list / edit / remove): `/moai:harness list|edit|remove <name>`.

**Harness execution**: `/harness:<name>` (auto-generated thin-wrapper command -> the harness's Runner Workflow).

See `harness-builder.md` (companion workflow under `moai/workflows/`) for the full Builder contract and `.claude/rules/moai/workflow/dynamic-workflows.md` for the Runner's dynamic-workflow primitive.

---

## Legacy 7-Phase Body (HISTORICAL REFERENCE — redirect source, NOT active)

> The content below this separator is the original 7-Phase workflow, preserved
> verbatim as the redirect source. It is NOT the active harness-creation path.
> New harness creation MUST use `/moai:harness <NL request>` (v4) above. The
> revfactory 7-Phase residual grep excludes this body because it IS the legacy
> source being redirected away from.

Meta-factory skill that architects and generates project-specific agent teams. Adapts the [revfactory/harness](https://github.com/revfactory/harness) 7-Phase workflow to MoAI's agent ecosystem. Produces `harness-*` skills and agent definitions tailored to each project's domain.

**Upstream**: revfactory/harness (Apache-2.0) — "A meta-skill that designs domain-specific agent teams, defines specialized agents, and generates the skills they use." (2905 stars, 420 forks, created 2026-03-26)

**Effectiveness data (design target)**: +60% avg quality score (49.5 → 79.3), 15/15 win rate, −32% variance (n=15, author-measu