zenigame-implement

Automate the Alpha Factory TODO workflow with isolated worktrees, Codex reviews, and main-branch merges.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/kent013/zenigame-fx --skill zenigame-implement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zenigame-implement
Source: https://github.com/kent013/zenigame-fx/tree/main/.claude/skills/_archived/zenigame-implement
Command: npx skills add https://github.com/kent013/zenigame-fx --skill zenigame-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Alpha Factory TODO implementation workflow requires secure isolation, rigorous testing, Codex review, and careful merging into main. This skill provides a structured approach to manage these steps using worktrees and documented procedures.

Core Features & Use Cases

  • End-to-end workflow orchestration: from design extraction through implementation, testing, Codex review, and main-branch merge.
  • Worktree isolation: use git worktrees to keep todo work in an isolated environment without contaminating main.
  • Phase-driven process: enforce A/B/C phase checks, dependencies, and test coverage with clear documentation updates.

Quick Start

Provide a TODO ID to initialize the worktree workflow and perform the end-to-end steps from implementation to main merge.

Frequently Asked Questions about zenigame-implement

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

FAQPage Schema
How do I automate git worktree isolation for TODO implementation and code review?▼

You can automate git worktree isolation by providing a TODO ID to initialize the workflow, which enforces test-driven development and Codex review before merging changes into the main branch. This ensures the main branch remains uncontaminated.

What is the Alpha Factory TODO workflow and when do I need worktree isolation?▼

The Alpha Factory TODO workflow is an end-to-end process covering design extraction, implementation, Codex review, and main-branch merging. You need worktree isolation to keep todo work separate from main and enforce test-driven development protocols.

Can I skip the consensus check or Codex review during the TODO merge process?▼

Yes, you can skip the consensus check during the TODO merge process by using the optional --skip-consensus mode. The workflow also supports --skip-todo and --tmp_dir modes to customize the end-to-end automation pipeline.

How do I enforce test-driven development and dependency checks before a main-branch merge?▼

You enforce test-driven development and dependency checks before a main-branch merge by applying the Phase A-C protocol within the isolated worktree. This phase-driven process ensures test coverage and documentation updates are complete before merging.

Does the TODO implementation workflow support temporary directories for isolated testing?▼

Yes, the TODO implementation workflow supports temporary directories for isolated testing through the optional --tmp_dir mode. This allows custom directory paths for worktree isolation during the end-to-end automation process.