Mcaf Solution Governance

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

Validate

• root and local responsibilities are not duplicated blindly
• local files do not weaken root policy
• maintainability keys are present and named consistently
• an agent can tell which AGENTS.md to read first for any path

Ralph Loop

Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

1. Plan first (mandatory):
   • analyze current state
   • define target outcome, constraints, and risks
   • write a detailed execution plan
   • list final validation skills to run at the end, with order and reason
2. Execute one planned step and produce a concrete delta.
3. Review the result and capture findings with actionable next fixes.
4. Apply fixes in small batches and rerun the relevant checks or review steps.
5. Update the plan after each iteration.
6. Repeat until outcomes are acceptable or only explicit exceptions remain.
7. If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.

Required Result Format

• status: complete | clean | improved | configured | not_applicable | blocked
• plan: concise plan and current iteration step
• actions_taken: concrete changes made
• validation_skills: final skills run, or skipped with reasons
• verification: commands, checks, or review evidence summary
• remaining: top unresolved items or none

For setup-only requests with no execution, return status: configured and exact next commands.

Load References

• read references/rule-precedence.md first
• use references/project-agents-template.md only when creating a local file
• use references/dotnet-agents-pattern.md when the solution stack is .NET

Example Requests

• "Set up AGENTS for this mono-repo."
• "Set up AGENTS for this .NET solution."
• "Split governance between the solution root and each service."
• "Move maintainability limits into AGENTS and make precedence explicit."