moai-meta-harness

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? This Skill prevents dead-end invocations of the deprecated 7-Phase meta-harness workflow by intercepting backward-compatible calls and redirecting them to the v4 harness Builder, which generates project-specific agent teams and skills through an orchestrator-direct 4-phase process. ## Core Features & Use Cases - Deprecation Redirect: Surfaces a deprecation notice on any legacy 7-Phase invocation and routes the user to /moai:harness <natural-language request> for the v4 Builder. - Namespace Governance: Enforces the hns-* user-owned namespace contract so generated harness artifacts are never overwritten by moai update and never collide with template-managed moai-* skills. - Historical Reference: Preserves the original 7-Phase workflow (Discovery through Iteration) and 6 architectural patterns as reference documentation for understanding legacy harnesses. - Use Case: A user on an older MoAI project triggers the legacy harness generation path; this Skill intercepts the call, explains the v4 replacement, and directs them to issue /moai:harness build a harness for my-project's API development instead. ## Quick Start Ask the assistant to create a new project harness by issuing /moai:harness followed by a natural-language description of your project 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 v4?▼

Issue /moai:harness followed by a natural-language request describing your project domain and goals. The v4 Builder runs Context-First Discovery, then executes 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 process (ANALYZE, PLAN, GENERATE, ACTIVATE) plus a manifest-driven dynamic-workflow Runner. The legacy 7-Phase body is retained only as historical reference and redirect source.

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

The hns-* namespace holds user-generated harness skills that moai update never deletes or modifies, while moai-* skills are template-managed and get removed and reinstalled on every update. Emitting a moai-* prefixed artifact during harness generation is a contract violation.

Does moai update delete my generated harness agents?▼

No. Generated agents under .claude/agents/harness/ and hns-* skills are user-owned and are never deleted or modified by moai update; they are backed up before updates. Only template-managed moai-* assets are overwritten.

Why does a generated harness agent need a skills frontmatter field?▼

The skills field preloads the agent's companion hns-* skill so the domain skill loads deterministically when the agent is delegated. Agents missing this field fail the Phase-6 smoke gate because auto-discovery fails silently without it.