Skills
Use these skill folders with the tutorial.
MCAF lists only the skills bundled in this repository. .NET skills live in the dedicated Managed Code Skills catalog.
Write or update an architecture decision record with alternatives, consequences, approval, and an executable implementation contract. Use for material design decisions or an explicit ADR request.
Improve backlog readiness, delivery roles, team cadence, and feedback agreements around a concrete process problem. Use for team delivery policy, not an individual feature implementation plan.
Create or refresh docs/Architecture.md as a concise map of real modules, boundaries, contracts, slices, and entry points. Use for onboarding or architecture documentation changes.
Create or revise CI/CD workflows, required quality gates, versioned artifacts, release promotion, and rollback. Use for pipeline or delivery automation changes.
Review a diff for correctness, requirement coverage, test quality, and operational risk, or refine PR review policy and templates. Use for concrete findings and review readiness.
Fix local setup, run, debug, test, or onboarding friction using reproducible repository commands. Use when contributor workflows are missing, inconsistent, or slow.
Update durable engineering docs, navigation, and canonical source placement when they are stale, duplicated, or missing. Use for general docs work; feature specs and ADRs have dedicated skills.
Create or update an executable feature specification with stable requirements, acceptance criteria, real flows, ADR decisions, and test traceability. Use before non-trivial behavior changes or on an explicit spec request.
Prioritize human review of a large generated code area by tracing real flows and ranking risky files. Use when a reviewer cannot inspect every line and needs a practical review sequence.
Plan or improve data exploration, ML feasibility, experiments, evaluation, inference, and model operations. Use for training, inference, or data-science delivery, not generic AI coding.
Turn relevant quality goals into measurable requirements and verification for performance, reliability, accessibility, data integrity, or other system attributes.
Instrument or specify logs, metrics, traces, correlation, and actionable alerts for a concrete runtime flow. Use when detection or diagnosis is missing or a change affects operational visibility.
Review or implement scoped security controls for authentication, authorization, secrets, external inputs, data handling, and pipeline permissions. Use for a concrete security impact or baseline request.
Refactor coupled or oversized code by responsibility, apply repository maintainability limits, and document justified exceptions. Use for design quality changes or maintainability policy.
Create or update root and project-local AGENTS.md, repository boundaries, rule precedence, skill routing, and agent workflow policy. Use for MCAF bootstrap or governance changes.
Define or refine branch, merge, commit, release, and repository ownership policy. Use for source-control governance or secrets-in-history response, not routine Git commands.
Design or update regression tests for features, defects, and refactors using repository verification commands. Use for meaningful user or system flow coverage and test strategy.