Pmo quality release

Skill witchwasin/Axiom-PMO/skills/pmo-quality-release

Use for QA evidence, release readiness, rollback review, and close-out decisions.From its SKILL.md

Install

npx -y skills add witchwasin/Axiom-PMO --skill pmo-quality-release

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, as published. Nobody here has run it

pmo-quality-release

Purpose

Verify release readiness, QA evidence, rollback planning, blocker status, and human release approval.

Trigger

Use for QA review, UAT/release gate, rollback review, or close-out summary.

Required Inputs

PROJECT.md, configured task source of truth, release notes if present, and any conditional artifacts required by pmo-config/context-map.json and pmo-config/artifact-policy.json.

Allowed Context

Use QA/release context only. Read source docs only when evidence conflicts with requirements.

Mode Behavior

Use pmo-config/artifact-policy.json for mode/gate artifact requirements and pmo-config/policy.json for approval gates and roles. Lite release requires PROJECT.md and DELIVERY.md (a prose "work item" mention is not parseable evidence); RELEASE.md stays optional unless the configured artifact policy or a real release/UAT trigger requires it. Never auto-create RTM.json or RELEASE.md for Lite without a trigger.

Execution Steps

Check open blockers.
Verify work-item evidence and status.
Confirm rollback table rows when RELEASE.md exists.
Confirm Release Approved human evidence for every mode.
Run release validation.

Output Contract

Return pass/fail summary, open blockers, release approval status, rollback status, and next action.

Approval Rules

AI must not approve production release, mark Release Approved for a human, deploy, tag, or push. Human Release Approved evidence is mandatory when required by the configured gate policy.

Validation Command

node cli/axiom.mjs validate --project <project> --mode <mode> --gate Release

Prohibited Actions

Do not release with missing human approval, unresolved blockers, missing configured guardrails, unverified rollback, or Lite artifacts created only to satisfy a hardcoded checklist.

Completion Criteria

Release gate passes with zero failures and required human approval evidence is present.