moai-meta-harness

Redirects legacy 7-Phase harness invocations to the v4 orchestrator-direct harness Builder.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/jjjh7401/AI-Lighting_Console --skill moai-meta-harness-jjjh7401
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-meta-harness
Source: https://github.com/jjjh7401/AI-Lighting_Console/tree/main/.claude/skills/moai-meta-harness
Command: npx skills add https://github.com/jjjh7401/AI-Lighting_Console --skill moai-meta-harness-jjjh7401

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Legacy invocation paths referencing the retired 7-Phase meta-harness workflow would otherwise hit a dead end; this Skill intercepts them, surfaces a deprecation notice, and routes users to the v4 harness Builder (/moai:harness) that generates project-specific agent teams and hns-* skills. ## Core Features & Use Cases - Deprecation Redirect: Converts any backward-compat invocation of the 7-Phase workflow into a pointer to the v4 Builder with its ANALYZE / PLAN / GENERATE / ACTIVATE phases. - Historical Reference: Preserves the original 7-Phase workflow body (Discovery through Iteration) plus reference docs on agent cross-references, architectural patterns, and hierarchical scoring for audit purposes. - Namespace Contract Documentation: Defines the HARD rules separating template-managed moai-* skills from user-generated hns-* harness artifacts. - Use Case: A user on an older MoAI setup triggers the legacy harness-generation path; instead of failing, they receive the deprecation notice and the exact /moai:harness command to create their harness with the v4 Builder. ## Quick Start Ask the AI to create a new harness by issuing /moai:harness followed by a natural-language description of your project's domain and goals.

Frequently Asked Questions about moai-meta-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new agent-team harness in MoAI?▼

Issue /moai:harness followed by a natural-language request describing your project domain. The v4 Builder runs Context-First Discovery, an approval gate, then the ANALYZE, PLAN, GENERATE, and ACTIVATE phases to emit the harness artifacts.

What replaced the 7-Phase meta-harness workflow?▼

The v4 harness Builder replaced it with an orchestrator-direct 4-phase flow plus a manifest-driven dynamic-workflow Runner. The 7-Phase body is retained only as historical reference and as the redirect source for legacy invocations.

What is the difference between moai-* and hns-* skill namespaces?▼

moai-* skills are template-managed and overwritten by moai update, while hns-* skills and .claude/agents/harness/ files are user-generated and never modified by updates. Emitting a moai-* artifact during harness generation is a contract violation.

Can I still use the legacy 7-Phase workflow for harness generation?▼

No. The 7-Phase workflow is retired and must not be used for new harness creation. Any invocation of it surfaces a deprecation notice and redirects to the v4 Builder via /moai:harness.

How are generated harnesses evaluated for quality?▼

The sync-auditor runs a 4-dimension Sprint Contract assessment covering Functionality, Security, Craft, and Consistency. The default pass threshold is 0.75 with a frozen floor of 0.60, and an optional hierarchical scoring mode adds per-sub-criterion anchors.