What is the zero-warnings policy in this skill?

The zero-warnings policy dictates that any output from the compiler or linter is considered a failure. All warnings must be resolved before the code can be committed or merged.

Is this skill specific to the Mojo programming language?

Yes, while the coordination logic is broad, the implementation standards, memory management patterns, and build tools (pixi, mojo) are optimized for Mojo v0.26.1+.

How does the delegation matrix assign tasks?

It assigns high-complexity tasks like SIMD optimizations and memory management to Senior Engineers, standard logic to Engineers, and boilerplate or helpers to Junior Engineers.

How does it track implementation progress?

The skill utilizes the GitHub CLI (gh) to view issue specifications and post progress updates, blockers, and completions directly to issue comments.

Implementation Phase Coordinator

Name: Implementation Phase Coordinator
Author: mvillmow

bymvillmow

•

Collaboration Tools

Coordinates software implementation phases by delegating granular tasks to specialized engineering roles while enforcing strict Mojo code quality standards.

About

The Implementation Phase Coordinator skill manages the transition from architectural planning to active development. It automates the breakdown of complex deliverables into actionable tasks, assigning them based on technical complexity to Senior, Standard, or Junior engineer profiles. Specifically tailored for Mojo development within the ProjectOdyssey framework, it enforces a 'zero-warnings' policy and integrates directly with GitHub CLI to track progress, ensure 80% test coverage, and verify high-performance memory management patterns before code approval.

Key Features

Strict 'zero-warnings' policy enforcement for Mojo compilation and linting
Hierarchical task delegation based on algorithmic complexity and memory management requirements
Automated quality checklists including 80% minimum test coverage and SIMD optimization checks
12 GitHub stars
Deep integration with GitHub CLI for issue tracking and progress commenting
Standardized patterns for Mojo v0.26.1+ ownership, borrowing, and mutation

Use Cases

Managing complex refactoring tasks that require SIMD or memory ownership adjustments
Standardizing code review processes across distributed engineering roles
Transitioning from a completed Plan phase to active implementation of a Mojo module

About

Key Features

Strict 'zero-warnings' policy enforcement for Mojo compilation and linting
Hierarchical task delegation based on algorithmic complexity and memory management requirements
Automated quality checklists including 80% minimum test coverage and SIMD optimization checks
12 GitHub stars
Deep integration with GitHub CLI for issue tracking and progress commenting
Standardized patterns for Mojo v0.26.1+ ownership, borrowing, and mutation

Use Cases

Managing complex refactoring tasks that require SIMD or memory ownership adjustments
Standardizing code review processes across distributed engineering roles
Transitioning from a completed Plan phase to active implementation of a Mojo module