agentic-engineering-governance

Define authority, risk, budget, and approval boundaries for agent-driven projects.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill agentic-engineering-governance-dagimalemayehuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentic-engineering-governance
Source: https://github.com/DagimAlemayehuu/AgenticEngineering/tree/main/agentic-engineering/skills/agentic-engineering-governance
Command: npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill agentic-engineering-governance-dagimalemayehuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agentic workflows that touch production systems, budgets, sensitive data, or external providers need explicit human authority before execution. This Skill establishes the governance record that defines who can approve what, preventing uncontrolled autonomous actions. ## Core Features & Use Cases - Governance Record Creation: Produces an approved record covering roles, risk levels, autonomy limits, budgets, provider permissions, data classification, escalation paths, and acceptance gates. - Authority Gating: Stops setup or execution when required human authority is absent, keeping consequential decisions behind explicit approval. - Specialist Routing: Reads the core Agentic Engineering routing, security, profile, and contract references to select governance-relevant specialists. - Use Case: Before letting agents modify a production repository with paid API providers, run this Skill to define spending caps, data classification rules, and which actions require sign-off. ## Quick Start Use $agentic-engineering-governance to define the operating boundaries for this project before any setup begins.

Frequently Asked Questions about agentic-engineering-governance

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

FAQPage Schema
How do I set approval boundaries for AI agents working on my repository?▼

Run the governance phase before setup to produce an approved record defining roles, autonomy limits, and acceptance gates. Consequential actions like spending, sensitive-data use, and destructive operations stay behind explicit human authority.

When should I run the governance phase of agentic engineering?▼

Run it before project setup or consequential work, whenever autonomy changes, or when production systems, spending, sensitive data, external providers, or destructive actions enter scope. It must complete before execution begins.

What does the governance record include?▼

The record covers roles, risk levels, autonomy limits, budgets, provider permissions, data classification, escalation paths, and acceptance gates. It is derived from the core routing, security, profile, and contract references.

Can agents proceed if governance approval is missing?▼

No. The Skill explicitly stops before setup or execution when required authority is absent. Business intent, spending, sensitive-data use, destructive actions, and launch acceptance all require explicit human approval.

Does the governance skill work with other agentic engineering phases?▼

Yes. It reads the main agentic-engineering skill, resolves its bundled core references, and selects governance-relevant specialists from the core skill map. It is the first gate before setup and execution phases.