mcaf-devex

The mcaf-devex skill is designed to improve the engineering velocity of complex, multi-component repositories by addressing friction in local development workflows. It acts as a bridge between the repository's current state and a frictionless 'F5-ready' development environment. It is intended for software engineers and technical leads who encounter difficulties with complex build pipelines, undocumented environment configurations, or inconsistent cross-platform setups. By applying a structured 'Ralph Loop' workflow, the agent helps standardize tasks, document implicit assumptions, and ensure that new contributors can reach their first successful result without requiring tribal knowledge or manual intervention.

• Standardizes build, run, debug, and test commands to create a single, predictable path for local development.

• Automates the identification and resolution of slow or fragile inner-loop bottlenecks, such as slow container spin-up or complex prerequisite management.

• Generates and maintains high-quality onboarding documentation that ensures new engineers can navigate the repository independently.

• Produces concrete project deltas, including configuration scripts, updated build definitions, cross-platform compatibility fixes, and local environment sandboxing.

• Enforces strict validation via clear verification commands to ensure that local development matches CI/CD expectations, reducing 'it works on my machine' syndrome.

• Always start by reading the repository's AGENTS.md and related development documentation to respect existing constraints.

• Use this skill to solve concrete workflow issues, not for generic cleanup or pipeline policy enforcement.

• Always prioritize the 'Ralph Loop'—plan, execute, review, and iterate—to ensure changes are safe, documented, and verifiable.

• Deliverables should include explicit verification commands that allow any team member to confirm the fix independently.

• If a repository setup is blocked by missing dependencies, use the skill to bootstrap those dependencies or document the exact reason for the failure path.

• Ideal for .NET solutions, containerized microservices, or any repository suffering from configuration drift or high onboarding overhead.