/validate

name: validate
description: >-
  Run MCS quality validation on products in workspace/. Three-tier system: MCS-1
  structure, MCS-2 quality + anti-commodity, MCS-3 deep review. Returns scored reports
  with fix instructions. Use when: 'validate', 'check quality', or before publishing.
argument-hint: "[--level=1|2|3] [--fix] [--batch] [--express]"
allowed-tools:
  - Read
  - Edit
  - Glob
  - Grep
  - Bash(myclaude *)

Validator

Run MCS quality checks on any product in `workspace/` and return actionable, scored reports.

**When to use:** After building or modifying a product, before publishing, or anytime you want a quality snapshot.

**When NOT to use:** On products outside `workspace/`. Do not use to validate the Engine itself.

---

Activation Protocol

0. **Shared preamble:** Load `references/quality/activation-preamble.md` — context assembly, persona adaptation, deterministic routing rules. 1. Detect product type: read `.meta.yaml` → `product.type` and `state.phase`

• Missing → infer from file structure (SKILL.md, AGENT.md, SQUAD.md, hooks.json, etc.)
• Cannot determine → ask: "What product type is this?"

1b. **Mode selection (Express vs Guided).** Read `creator.yaml → preferences.workflow_style`. Resolve the flow mode:

• `--express` flag OR `workflow_style == "autonomous"` → **Express mode**. Skip the coaching explanations after each stage, suppress the remediation menu, and deliver a single verdict block at the end (pass/warn/fail + fix instructions in a compact list). Persona tone still holds; only the conversational scaffolding is trimmed.
• `workflow_style == "guided"` or missing → **Guided mode** (default). Walk each stage with the full coaching voice and propose remediation interactively after failing stages.

2. **Maintain creator persona**: Read `creator.yaml` → adapt to `profile.type` and `technical_level` 3. **Load voice identity**: Load `references/quality/engine-voice-core.md`. Load the full `references/quality/engine-voice.md` only for peak moments (first-pass milestone celebration, confronting failure verdict) — see UX Stack below. 3b. **Exemplar load:** Load `references/quality/exemplar-outputs.md` sections E6 and E7 only — the validation pass and failure exemplars. Your verdict MUST carry the same visual structure: Frame for pass (with tier badge), rail format for failure (with numbered fixes + estimated score after). Adapt to creator context — never copy verbatim. 4. Load DNA requirements: `product-dna/{type}.yaml` 4b. **Load architectural DNA:** Read `structural-dna.md`. The 10 architectural principles and the Tier 1 DNA patterns (D1-D4, D13, D14) are the canonical audit baseline — Stages 3 and 5 grep the product against them, and any violation surfaces as coaching. 5. Load product spec: `references/product-specs/{type}-spec.md` 5b. **Load entity ontology (squad/system/agent/workflow/minds):** If type ∈ {squad, system, agent, minds, workflow}, read `references/entity-ontology.md`. This substrate drives semantic validation:

• §HERITAGE: verify the product inherits correct DNA from its lineage (squad must pass all agent DNA + D9/D10/D12/D18)
• §COMPOSITION: verify only allowed compositions (squad→agents+minds+skills+workflows; system→everything; workflow→skills only)
• §AGENT_ROLES: if `.meta.yaml` has `agent_role`, verify tool boundaries match the role
• §SQUAD_ANATOMY: verify all 8 mandatory components exist and have content
• §WORKFLOW_VS_SQUAD: verify workflows don't contain agents and squads don't use fixed-sequence-only routing
• §HEURISTICS: surface coaching if product shows signs of wrong type (skill >800 lines → suggest agent)
• For type=system ONLY: §SYSTEM_ENGINES — verify declared gears have concrete implementations (not just prose), verify counterpart couplings are declared, verify critical chain (E4→E5→E6→E7) is complete if perception gear is active
• §INTELLIGENCE_PIPELINE — verify baseline delta (is this better than Claude vanilla?), verify substance (does this carry domain intelligence or is it just formatted instructions?)

6. Load config: `config.yaml` → scoring weights, thresholds, placeholder patterns 7. Load gates: `quality-gates.yaml` → state transition rules 7b. **Load proactives:** Load `references/engine-proactive.md` — wire #1 (pipeline guidance: after validate passes, guide to /test then /package), #19 (error recovery: on validation failure, propose specific fixes), #20 (test mandate: if MCS-2+ and not tested, block /package suggestion). 8. **CLI contract:** Load `references/cli-contract.md` for Stage 6 (CLI Preflight). Severity map:

• **Warning:** `validate --json` — CLI validation is advisory during /validate (blocking only during /publish)
• **Warning:** `doctor --json` — health check is advisory, score < 8.0 triggers suggestion
• Stage 6 detail protocol: `references/validation-stages/stage-6-cli-preflight.md`

---

Commands

/validate                    → Auto-detect, run MCS-1
/validate --level=2          → MCS-2 (includes MCS-1)
/validate --level=3          → MCS-3 (includes MCS-1+2, PRO only)
/validate --fix              → MCS-1 + auto-remediate fixable issues
/validate --report           → MCS-1 + output detailed report file
/validate --batch            → Validate ALL products sequentially

---

Core Instructions

STAGE EXECUTION

Execute stages in order. Blocking stages stop on failure. Non-blocking stages report but continue.

**Load detailed stage protocols from references/ on demand. Each stage is a separate file — load only the stage(s) you need for the current `--level`.**

| Stage | Name | Blocking | Reference | |-------|------|----------|-----------| | **0** | **Intent Coherence** (W3.7) | **advisory** | Read `${CLAUDE_SKILL_DIR}/references/validation-stages/stage-0-intent-coherence.md` | | 1 | Structural | YES | Read `${CLAUDE_SKILL_DIR}/references/validation-stages/stage-1-structural.md` | | 2 | Integrity | YES | Read `${CLAUDE_SKILL_DIR}/