moai-workflow-worktree

Provision isolated MoAI worktrees per SPEC with registry tracking.

Updated Apr 26, 2026

Search Tags:#automation #registry #git-worktree #parallel-development #spec-management #moai-adk #moai-worktree

Ready to run

npx skills add https://github.com/gkswls5006-web/last-todo --skill moai-workflow-worktree-gkswls5006-web

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: moai-workflow-worktree
Source: https://github.com/gkswls5006-web/last-todo/tree/main/.claude/skills/moai-workflow-worktree
Command: npx skills add https://github.com/gkswls5006-web/last-todo --skill moai-workflow-worktree-gkswls5006-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

MoAI-ADK-based SPEC development often requires developers to switch contexts and manage multiple branches, which leads to conflicts, wasted time, and unstable environments. This Skill automates provisioning of isolated MoAI worktrees per SPEC, centralizes tracking, and ensures clean integration with Plan-Run-Sync workflows.

Core Features & Use Cases

Isolated SPEC Worktrees: each SPEC gets its own worktree with independent Git state and file system.
Automatic Registry & Tracking: centralized registry records status, last_sync, created_at, and ownership for auditability.
MoAI-ADK Workflow Integration: seamless alignment with /moai:1-plan, /moai:2-run, and /moai:3-sync for end-to-end SPEC development.
Team Collaboration & Cleanup: supports multi-developer usage with auto-cleanup of merged worktrees and registry integrity checks.

Quick Start

Create a SPEC with /moai:1-plan and immediately switch to its dedicated worktree to start /moai:2-run.

Frequently Asked Questions about moai-workflow-worktree

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

FAQPage Schema

How do I manage parallel SPEC development without branch switching conflicts?▼

Parallel SPEC development requires isolated Git worktrees to provide each task with an independent file system state. This approach prevents branch switching conflicts and unstable environments by provisioning separate workspaces for concurrent development tracks.

What is the best way to track Git worktree status for multiple SPECs?▼

Tracking Git worktree status requires a centralized registry that records state, last_sync, created_at, and ownership metadata. This provides auditability and concurrency protection for multiple worktrees through atomic registry updates.

How does MoAI-ADK integrate with parallel worktree workflows?▼

MoAI-ADK workflow integration connects isolated worktrees directly to plan, run, and sync phases. This allows developers to create a SPEC with the plan command, execute it in the dedicated worktree, and seamlessly sync changes back.

Can I use automated worktree provisioning for team-based parallel development?▼

Automated worktree provisioning supports multi-developer usage by managing team collaboration and registry integrity. It handles auto-cleanup of merged worktrees and applies templates to ensure safe, repeatable workflows across the team.

Do I need a specific Git setup to enable isolated worktrees for SPEC management?▼

Isolated worktree provisioning relies on standard Git worktree functionality to create independent file systems and branch states. No specific external dependencies are required beyond the MoAI-ADK environment to enable automatic creation and registry tracking.