stage6-rubric

Evaluate Architect Review deliverables against Stage 6 PASS/FAIL criteria.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill stage6-rubric
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stage6-rubric
Source: https://github.com/yiwei79/azoth/tree/main/.opencode/skills/stage6-rubric
Command: npx skills add https://github.com/yiwei79/azoth --skill stage6-rubric

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage 6 Quality Rubric provides concrete PASS/FAIL criteria to gate structured content at the Architect Review stage, preventing shallow first-pass outputs from reaching human approval. It enforces three axes—Depth, Governance, and Patterns—and blocks approval on any axis failure that would escalate to Stage 7.

Core Features & Use Cases

  • Defines Axis 1 (Depth) criteria for agent archetypes and skills, including required sections and content depth.
  • Defines Axis 2 (Governance) criteria with governance_anchor, gate type declarations, and HITL considerations.
  • Defines Axis 3 (Interaction Pattern) criteria ensuring complete integration points and usage patterns.

Quick Start

Run the Stage 6 rubric to evaluate Architect Review deliverables before final approval.

Frequently Asked Questions about stage6-rubric

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

FAQPage Schema
How do I enforce quality gates for agent archetypes and skills during an architect review?

To enforce quality gates during an architect review, apply a Stage 6 rubric to evaluate structured content like AGENT.md and SKILL.md files against Depth, Governance, and Pattern axes before human approval.

What is a Stage 6 quality rubric in software architecture governance?

A Stage 6 quality rubric is a formal evaluation mechanism that provides concrete PASS/FAIL criteria to gate structured content, preventing shallow first-pass pipeline outputs from reaching human approval by enforcing depth, governance, and interaction patterns.

How do I standardize gate decisions for pipeline YAML artifacts?

Standardize gate decisions for pipeline YAML artifacts by applying rubric criteria that check for minimum depth, governance anchors, and explicit integration points, escalating any axis failure to Stage 7.

When should I escalate a structured content review to Stage 7?

Escalate a structured content review to Stage 7 when the quality rubric identifies a failure in any of the three axes—Depth, Governance, or Interaction Patterns—during the architect review stage.

What governance criteria are required to pass an architect review gate?

To pass an architect review gate, governance criteria require a declared governance anchor, explicit gate type declarations, and documented human-in-the-loop considerations within the structured content.

Does the quality rubric apply to both agent archetypes and pipeline YAML artifacts?

Yes, the quality rubric applies to both agent archetypes like AGENT.md and pipeline YAML artifacts, enforcing Axis 1-3 criteria across all structured content evaluated during the architect review.