MCPGateway: Skill for Codex

MCAF: Solution Governance

Trigger On

• bootstrap or rewrite a repo-wide AGENTS.md
• add project-local AGENTS.md files for a multi-project solution
• clarify rule precedence, skill routing, or maintainability policy placement

Value

• produce a concrete project delta: code, docs, config, tests, CI, or review artifact
• reduce ambiguity through explicit planning, verification, and final validation skills
• leave reusable project context so future tasks are faster and safer

Do Not Use For

• writing feature specs or ADR content
• code-level refactoring without a governance change

Inputs

• current repo topology and module roots
• existing root or local AGENTS.md files
• actual build, test, format, and analyze commands
• the active stack when commands or tooling are platform-specific

Quick Start

1. Read the nearest AGENTS.md and confirm scope and constraints.
2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

1. Identify the solution root and any project or module roots that need their own AGENTS.md.
2. Keep the root file global:
   • shared workflow
   • shared commands
   • rule precedence
   • global skill list
   • maintainability-limit keys
3. Keep local files narrow:
   • project purpose
   • entry points
   • boundaries
   • local commands
   • applicable skills
   • stricter local constraints
4. Resolve overlap explicitly. Local rules may be stricter or more specific, never silently weaker.
5. When the stack is .NET, record:
   • the test framework
   • the runner model (VSTest or Microsoft.Testing.Platform)
   • the repo-root .editorconfig as the analyzer config owner
6. Put numeric maintainability limits in AGENTS.md, not in framework prose or skill bodies.

Deliver

• one clear root AGENTS.md
• local AGENTS.md files only where boundaries justify them
• explicit precedence rules and skill-routing guidance