skills.rest
managedcode
managedcodeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dotnet-mcaf

Integrate MCAF governance, documentation, and verification workflows into .NET repositories.

42|10|Updated Mar 27, 2026
Search Tags:#workflow#documentation#verification#governance#dotnet
One-click install
npx skills add https://github.com/managedcode/PrompterOne --skill dotnet-mcaf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-mcaf
Source: https://github.com/managedcode/PrompterOne/tree/main/.codex/skills/dotnet-mcaf
Command: npx skills add https://github.com/managedcode/PrompterOne --skill dotnet-mcaf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It consolidates the adoption of MCAF governance practices within .NET repositories, ensuring consistent process documentation, verification, and delivery workflows.

Core Features & Use Cases

  • Repository Governance: Sets up root and project-specific AGENTS.md files to define rules and policies.
  • Documentation Structuring: Guides the creation of durable docs/ folders like Architecture, Features, ADRs, Testing, Development, and Operations.
  • Workflow Enforcement: Advises on the proper sequence for non-trivial task planning, validation, and verification, including TDD, static analysis, and coverage.

Quick Start

Create a root AGENTS.md, setup the docs/ directory, and align your verification tools with the guidance to ensure your repository follows MCAF standards.

Frequently Asked Questions about dotnet-mcaf

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

FAQPage Schema
How do I enforce consistent governance and documentation workflows in a .NET repository?▼

You can enforce .NET governance workflows by integrating MCAF principles directly into your repository, using root and project-specific AGENTS.md files to define rules, policies, and documentation structures for code review and delivery.

What is the best way to structure documentation for .NET project governance and verification?▼

The best way to structure .NET governance documentation is by creating durable docs/ folders for Architecture, Features, ADRs, Testing, Development, and Operations, ensuring consistent process documentation and verification alignment across projects.

Can I apply different governance rules to individual projects within a multi-project .NET solution?▼

Yes, you can apply varied governance rules to individual projects in a .NET solution by setting up local AGENTS.md files within each project directory, allowing customized policies alongside the root repository rules.

How do I set up TDD and static analysis verification workflows for .NET projects?▼

You set up .NET verification workflows by aligning your static analysis and coverage tools with MCAF guidance, advising on the proper sequence for non-trivial task planning, validation, and test-driven development execution.

Does MCAF governance support multi-project .NET solutions with varied delivery management policies?▼

Yes, MCAF governance supports multi-project .NET solutions by allowing local AGENTS.md files that define varied rules and policies, ensuring alignment with best practices for code review, testing, and delivery management across distinct projects.

Related Skills

Explore More Software Engineering Skills→
Postpartum-genushyacinthus29Postpartum-genushyacinthus29
8

dotnet-mcaf

Bootstrap MCAF governance in .NET repositories with AGENTS.md and docs scaffolding.

Community
Advanced
arcasilesgrouparcasilesgroup
54

guard

Check staged changes against governance standards in advise, gate, and drift modes.

Official
Advanced
aivos-xieaivos-xie
1

requesting-code-review

Automate pre-commit code review with security scans and quality checks.

Community
Advanced
elsa-workflowselsa-workflows
7.9k

speckit-constitution

Automates project constitution updates from user input and repository context.

Official
Intermediate