pmo-governance

Define PMO governance rules and department registry templates for ACHIEVEMOR workforce.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BoomerAng9/foai --skill pmo-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmo-governance
Source: https://github.com/BoomerAng9/foai/tree/main/acheevy/.claude/skills/pmo-governance
Command: npx skills add https://github.com/BoomerAng9/foai --skill pmo-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PMO governance and department-dispatch rules are often inconsistently applied, leading to unclear ownership, misaligned workflows, and ad-hoc task routing. This skill standardizes the PMO structure, defines department codes, leads, and required governance steps to ensure compliant, auditable operations.

Core Features & Use Cases

  • Department registry: defines Engineering (PMO-ECHO), Security (PMO-SHIELD), Data Ops (PMO-PULSE), Deployment (PMO-LAUNCH), and QA / Review (PMO-LENS) with leads, members, and Lil_Hawk support.
  • Governance rules: enforces task classification, cross-department coordination, and review gates through PMO-LENS.
  • Onboarding & changes: provides a clear process for adding new departments, Boomer_Angs, and updating dispatch tables and references.

Quick Start

Map the PMO department structure and governance rules for ACHIEVEMOR workforce.

Frequently Asked Questions about pmo-governance

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

FAQPage Schema
How do I define a PMO governance structure for engineering and security departments?

To define PMO governance, establish a department registry mapping units like Engineering (PMO-ECHO) and Security (PMO-SHIELD) with designated leads, members, and required governance steps to ensure compliant and auditable operations.

What is the best way to standardize workflow compliance and task routing across multiple departments?

Standardizing workflow compliance requires enforcing task classification, cross-department coordination, and review gates through a QA unit like PMO-LENS to eliminate ad-hoc task routing and unclear ownership.

How do I onboard new departments and workforce members into an existing PMO governance framework?

Onboard new departments and members by following documented change-management procedures to update the dispatch table, add entries to the department registry, and align workflows with existing governance rules.

Does this PMO governance approach support both data ops and deployment workflows?

Yes, the PMO governance framework explicitly supports data ops and deployment workflows by defining dedicated departments (PMO-PULSE and PMO-LAUNCH) with structured leads, members, and governance rules.

Why does ad-hoc task routing cause compliance issues in department workflows?

Ad-hoc task routing causes compliance issues because it bypasses standardized PMO structure, leading to unclear ownership, misaligned workflows, and unauditable operations across engineering and QA departments.

Can I use this PMO structure to enforce review gates before deployment?

Yes, you can enforce review gates before deployment by routing tasks through the PMO-LENS QA department, which ensures cross-department coordination and compliance before final deployment operations.