Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge…
MCAF: Agile Delivery
Apply MCAF agile-delivery guidance for backlog quality, roles, ceremonies, and engineering feedback. Use when defining how the team plans, tracks work, and turns feedback into durable improvements.
Trigger On
- the team needs backlog, ceremony, role, or feedback-loop rules
- delivery process is vague, too heavy, or living only in chat
- recurring team pain needs to become durable repo guidance
Workflow
- Keep delivery artefacts concrete:
- backlog - roles - ceremonies - engineering feedback
- Prefer lightweight agreements over process theatre.
- When a pain point repeats, turn it into a rule, doc, or skill update.
- Pull only the references that match the current process problem.
Deliver
- concrete delivery guidance
- durable team agreements
- feedback loops that update docs, skills, and rules
Validate
- the process guidance fixes a real delivery problem
- roles and rituals are explicit enough to use
- recurring pain is converted into a durable artifact, not more chat
Load References
- read
references/agile-delivery.mdfirst - open
references/roles.mdonly for a narrower topic
Related skills
Adopt MCAF governance in a .NET repository with the right AGENTS.md layout, repo-native docs, skill installation, verification rules, and non-trivial task workflow.
Apply MCAF developer-experience guidance for onboarding, F5 contract, cross-platform tasks, local inner loop, and reproducible setup.