mh-coo-quality-assurance

Evaluate deliverables against quality criteria and route to pass, rework, or escalate.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-coo-quality-assurance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mh-coo-quality-assurance
Source: https://github.com/Imad-Oute/MicroHard/tree/main/src/departments/coo/delivery-ops/mh-coo-quality-assurance
Command: npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-coo-quality-assurance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mh-coo-project-delivery-framework, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps maintain high-quality deliverables by facilitating an internal quality assurance process before they are submitted to the client.

Core Features & Use Cases

  • Internal QA Loop: Manages a self-evaluation loop for deliverables, including generate, evaluate, pass/rework/escalate stages.
  • Quality Criteria Adaptation: Adapts QA criteria to the type of deliverable (e.g., automation, AI agent, analysis, software, consulting).
  • Use Case: When a project team has completed a deliverable, this skill can be used to evaluate it for quality before final submission to the client.

Quick Start

Load the deliverable context, identify quality dimensions, run the self-evaluation loop, score against acceptance threshold, decide: submit / rework / escalate, prepare submission package, write QA record.

Frequently Asked Questions about mh-coo-quality-assurance

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

FAQPage Schema
How do I run internal quality assurance on project deliverables before client submission?

Internal quality assurance evaluates completed project deliverables against defined acceptance criteria, generating a quality score that routes the item to pass, rework, or escalate status for final client submission.

What is the deliverable review process for routing pass, rework, or escalate decisions?

The deliverable review process scores items against acceptance thresholds during a self-evaluation loop, using the resulting quality score to route the deliverable to either pass for submission, rework for changes, or escalate for review.

Can I adapt quality control criteria for different types of project deliverables?

Quality control criteria adapt automatically to the specific deliverable type, ensuring evaluation dimensions match the requirements of automation, AI agent, analysis, software, or consulting project outputs.

Do I need the project delivery framework to manage internal QA processes?

Yes, the internal QA process requires the project delivery framework as a dependency, utilizing its deliverable lifecycle states and acceptance criteria to properly evaluate and route project outputs.

How do I assemble a submission package and log QA records after a deliverable passes review?

After quality assurance review, assemble the submission package containing the approved deliverable and write a QA record to log the evaluation results, ensuring traceability before final client submission.