agentic-engineering-governance

Maps and audits AI coding workflows into Codex-native governance plans.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/moonzff/Codex_up --skill agentic-engineering-governance-moonzff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentic-engineering-governance
Source: https://github.com/moonzff/Codex_up/tree/main/skills/global-installed/agentic-engineering-governance
Command: npx skills add https://github.com/moonzff/Codex_up --skill agentic-engineering-governance-moonzff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams adopting AI coding assistants accumulate scattered practices across AGENTS files, skills, MCP tools, hooks, and automations with no clear ownership, risk level, or verification. This Skill turns that sprawl into a structured governance map and translates external best practices (such as Claude Code patterns) into Codex-native primitives instead of copying tool-specific configurations blindly. ## Core Features & Use Cases - Capability Mapping: Inventory AGENTS.md, skills, MCP tools, connector policies, automations, templates, and verification commands into a capability map with owner, risk, and verification fields. - Practice Translation: Convert external tool concepts (Claude CLAUDE.md, skills, commands, hooks, MCP) into Codex-native equivalents with explicit adopt/adapt/research/reject classification. - Governance Output: Produce a governance map plus an implementation queue with verification commands required before any practice is marked adopted. - Use Case: A team migrating from Claude Code to Codex uses this Skill to audit their existing AI workflows, translate each practice into Codex primitives, and generate a prioritized adoption queue with risk levels. ## Quick Start Ask the agent to audit this project's AI coding practices and translate external best practices into a Codex-native governance map with an adoption queue.

Frequently Asked Questions about agentic-engineering-governance

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

FAQPage Schema
How do I translate Claude Code best practices to Codex?▼

Map each Claude concept to a Codex primitive: CLAUDE.md becomes AGENTS.md and project docs, skills become Codex skills with SKILL.md, commands become templates or CLI workflows, and hooks become safe scripts or automations with explicit approval. Never copy .claude directories directly.

How do I audit AI coding workflows in a project?▼

Inventory AGENTS.md, skills, MCP tools, connector policies, automations, templates, verification commands, and memory locations. Then fill a capability map recording capability, path, owner, risk, and verification for each asset.

What is a capability map for agentic engineering?▼

A capability map is a table that records each AI coding capability alongside its file path, owner, risk level, and verification command. It turns scattered practices into a reviewable governance artifact that survives without the original research source.

Can I copy Claude hooks and settings directly into Codex?▼

No. Hooks, settings, commands, and agents must be translated into Codex-native equivalents such as safe scripts, verification commands, or automations with explicit approval. External writes stay behind target, preview/diff, and one-time confirmation.

When should a practice be marked as adopted?▼

Only after a verification command exists for it. Each practice is classified as adopt-now, adapt-first, research-more, or reject, and nothing is marked adopted without an explicit risk level and a working verification command.