moai-meta-harness

Redirects legacy 7-Phase harness generation requests to the v4 harness Builder workflow.

1.2k|222|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/modu-ai/moai-adk --skill moai-meta-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-meta-harness
Source: https://github.com/modu-ai/moai-adk/tree/main/internal/template/templates/.claude/skills/moai-meta-harness
Command: npx skills add https://github.com/modu-ai/moai-adk --skill moai-meta-harness

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 hit a dead end; this Skill intercepts those calls, surfaces a deprecation notice, and redirects users to the v4 harness Builder so backward-compatible invocations still resolve correctly.

Core Features & Use Cases

  • Deprecation Redirect: Routes any legacy 7-Phase invocation to /moai:harness <natural-language request>, which runs Context-First Discovery and the orchestrator-direct 4-phase Builder (ANALYZE / PLAN / GENERATE / ACTIVATE).
  • Historical Reference Preservation: Retains the full 7-Phase workflow body, agent cross-references, and hierarchical scoring documentation as reference material for understanding prior harness generations.
  • Namespace Contract Documentation: Defines the hns-* user-generated namespace versus the template-managed moai-* namespace, including update-safety guarantees for user-owned harness artifacts.
  • Use Case: A user on an older MoAI-ADK setup triggers the legacy meta-harness path; instead of failing, they receive a clear deprecation notice and the exact v4 command to create their project harness.

Quick Start

Ask the AI to create a new project 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 harness in MoAI-ADK?

Issue /moai:harness followed by a natural-language request describing your project. The v4 Builder runs Context-First Discovery, asks clarifying questions, then executes the ANALYZE, PLAN, GENERATE, and ACTIVATE phases to produce 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 legacy 7-Phase body is kept only as historical reference and as the redirect source for old invocation paths.

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

The moai-* namespace is template-managed and overwritten by moai update, while hns-* skills and .claude/agents/harness/ files are user-owned and never deleted or modified by updates. New generated artifacts must use the hns- prefix.

Will moai update delete my generated harness files?

No. User-owned hns-* skills, .claude/agents/harness/ agent definitions, and .moai/harness/ configuration are never deleted or modified by moai update; they are backed up instead. Only template-managed moai-* files are reinstalled.

When should I not use this legacy meta-harness skill?

Never use it for new harness creation; it is deprecated and user-invocable is false. It exists only to catch backward-compatible invocation paths and redirect them to the v4 Builder at /moai:harness.