Pmo build review

Skill witchwasin/Axiom-PMO/skills/pmo-build-review

Use for build completion evidence, code review readiness, and ready-for-QA checks.From its SKILL.md

Install

npx -y skills add witchwasin/Axiom-PMO --skill pmo-build-review

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.1 KB, as published. Nobody here has run it

pmo-build-review

Purpose

Confirm that implementation evidence is ready for review or QA.

Trigger

Use after build work, before review/test, or when checking a PR or patch against requirements.

Required Inputs

Task source of truth, changed-file summary, relevant requirement/design references, test evidence, and configured contracts from pmo-config/context-map.json, pmo-config/policy.json, and pmo-config/reference-types.json.

Allowed Context

Read only work items and code/design artifacts relevant to the change. Use source docs only for disputed requirements.

Mode Behavior

Use pmo-config/policy.json for valid statuses, review stages, evidence statuses, and strict triggers. Use pmo-config/reference-types.json for reference shape; do not accept free-text evidence where a configured reference is required.

Execution Steps

Map changed work to delivery item IDs.
Check acceptance criteria and test checklist evidence.
Compare implementation reality with approved Scope, BUILD-SPEC, acceptance cases, Mode, and execution-contract boundaries. Record a candidate Change Request when they differ; do not silently edit a contract to absorb the deviation.
Identify possibly omitted affected artifacts as candidate findings; do not claim automated impact discovery is exhaustive.
Identify missing review stage or unresolved blocker.
Recommend the next gate or corrective action without approving any human-owned gate.

Output Contract

Return review findings, missing tests, risk flags, and ready/not-ready status.

Approval Rules

AI can recommend ready-for-review but cannot approve production release.

Validation Command

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

Prohibited Actions

Do not hide failing checks, skip risk escalation, hardcode release requirements, or mutate git state without human approval.

Completion Criteria

Work items are traceable, review stage is valid, and unresolved issues are documented.