CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading.
Install Moai Workflow Project
$ npx skills add modu-ai/moai-adk --skill moai-workflow-project -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install modu-ai/moai-adk moai-workflow-project --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/moai-workflow-project .claude/skills/moai-workflow-project && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "moai-workflow-project" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-workflow-project into .claude/skills/moai-workflow-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-workflow-project", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-workflow-projectType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add modu-ai/moai-adk --skill moai-workflow-project -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install modu-ai/moai-adk moai-workflow-project --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/moai-workflow-project .agents/skills/moai-workflow-project && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "moai-workflow-project" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-workflow-project into .agents/skills/moai-workflow-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-workflow-project", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add modu-ai/moai-adk --skill moai-workflow-project -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install modu-ai/moai-adk moai-workflow-project --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/moai-workflow-project .cursor/skills/moai-workflow-project && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "moai-workflow-project" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-workflow-project into .cursor/skills/moai-workflow-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-workflow-project", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/modu-ai/moai-adk.git --path .claude/skills/moai-workflow-project--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add modu-ai/moai-adk --skill moai-workflow-project -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install modu-ai/moai-adk moai-workflow-project --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/moai-workflow-project .gemini/skills/moai-workflow-project && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "moai-workflow-project" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-workflow-project into .gemini/skills/moai-workflow-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-workflow-project", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install modu-ai/moai-adk moai-workflow-projectInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add modu-ai/moai-adk --skill moai-workflow-project -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/moai-workflow-project .github/skills/moai-workflow-project && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "moai-workflow-project" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-workflow-project into .github/skills/moai-workflow-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-workflow-project", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add modu-ai/moai-adk --skill moai-workflow-project -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install modu-ai/moai-adk moai-workflow-project --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/moai-workflow-project .opencode/skills/moai-workflow-project && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "moai-workflow-project" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-workflow-project into .opencode/skills/moai-workflow-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-workflow-project", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
moai-workflow-project- GitHub stars
- 1.2k
- Token cost
- ~2.8k tokens
- SKILL.md length
- 1,050 words
- Files
- 26 (incl. scripts, references)
- Skills in repo
- 48
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading.
- Works in 5 steps: Identify template category: code… → Select template variant matching the… → Apply customization variables (project… → …
- Tasks that involve Project management
- SKILL.md covers Quick Reference, Implementation Guide, Advanced Implementation and Resources, plus 7 more sections
- Runs Shell scripts from its folder
What it does
Moai Workflow Project is an agent skill from modu-ai/moai-adk. Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 29 other files, including scripts and reference files (for example `references/configuration.md`, `references/examples.md` and `references/language-localization.md`). Compatibility notes: Designed for Claude Code
It sits in Product & Project Management, covering Project management. The repository describes itself as: Agentic development harness for Claude Code — SPEC-driven plan/run/sync, TRUST 5 quality gates, model+effort routing, and Claude×GLM multi-LLM cost control. Single Go binary, 16… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Project management
Example prompts
- “/moai-workflow-project”
Requirements
- Python 3
- A Bash shell
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(git:*), Bash(npm:*), Bash(npx:*), Bash(uv:*), Bash(pip:*), Bash(ls:*), Bash(mkdir:*), Grep, Glob, WebFetch, WebSearch
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Identify template category: code boilerplate, feedback template, or project scaffold
- Select template variant matching the project stack and language
- Apply customization variables (project name, author, license, framework version)
- Validate rendered output against schema or existing conventions
- Optionally run template optimizer to reduce redundancy
What it can do on your machine
Read from SKILL.md and the folder at commit a2a184a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash(git:*)Bash(npm:*)Bash(npx:*)Bash(uv:*)Bash(pip:*)Bash(ls:*)Bash(mkdir:*)
…and 4 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Shell, from the files we listed), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Moai Workflow Project loads about 2.8k tokens when it runs, and up to ~18k if it reads all its reference files. Until then it costs about 66 tokens; SKILL.md has 1,050 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from modu-ai/moai-adk at commit a2a184a, republished under its Apache-2.0 licence (© modu-ai). 1,050 words, ~2,753 tokens.
Download SKILL.mdSave it as
.claude/skills/moai-workflow-project/SKILL.md (or your agent's skills folder). This skill also uses 25 other files; get the full folder from GitHub.- name
- moai-workflow-project
- description
- Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
- allowed-tools
- Read, Write, Edit, Bash(git:*), Bash(npm:*), Bash(npx:*), Bash(uv:*), Bash(pip:*), Bash(ls:*), Bash(mkdir:*), Grep, Glob, WebFetch, WebSearch
- compatibility
- Designed for Claude Code
- when_to_use
- Use for integrated project management: documentation scaffolding (product/structure/tech.md), multilingual language initialization, template and boilerplate…
- license
- Apache-2.0
- user-invocable
- false
- metadata.version
- 3.0.0
- metadata.category
- workflow
- metadata.status
- active
- metadata.updated
- 2026-04-25
- metadata.modularized
- true
- metadata.tags
- workflow, project, documentation, initialization, templates, boilerplate, scaffolding, jit-docs, docs-generation
- metadata.aliases
- moai-workflow-project
MoAI Workflow Project - Integrated Project Management System
Comprehensive project management system integrating documentation generation, multilingual support, and template optimization into a unified architecture with intelligent automation and Claude Code integration.
Scope: Consolidates documentation management, language initialization, and template optimization into a single cohesive system supporting complete project lifecycle from initialization to maintenance.
Target: Claude Code agents for project setup, documentation generation, multilingual support, and performance optimization.
Quick Reference
Core Capabilities:
- Documentation Management: Template-based generation with multilingual support
- Language Initialization: Detection, configuration, localization
- Template Optimization: Analysis with performance optimization
- Unified Interface: Single entry point for all capabilities
Key Features:
- Automatic project type detection and template selection
- Multilingual documentation (English, Korean, Japanese, Chinese)
- Intelligent template optimization with benchmarking
- SPEC-driven documentation updates
- Multi-format export (Markdown, HTML, PDF)
Supported Project Types: web applications, mobile applications, CLI tools, libraries, ML projects.
Implementation Guide
Module Architecture
Three capability areas:
- Documentation Management: template-based generation, project type detection, multilingual support, SPEC integration, multi-format export
- Language Initialization: automatic detection, configuration management, agent prompt localization, locale management
- Template Optimization: complexity analysis, performance optimization, backup/recovery, benchmarking
Core Workflows
Three workflows: project initialization, documentation generation from SPEC, template performance optimization. Each follows a 3-step pattern (configure → execute → review results). The initialization and settings interviews walk the question structure defined in schemas/tab_schema.json.
See core workflow walkthroughs for detailed step-by-step procedures.
Language and Localization
Automatic Language Detection: analyzes file content, configuration files, system locale, and directory structure.
Multilingual Documentation: language-specific directories (e.g., docs/ko, docs/en), language negotiation, automatic redirection.
Agent Prompt Localization: language-specific instructions, cultural context, token cost optimization.
See language and localization detail for token cost analysis and locale configuration.
Template Optimization
Performance Analysis: file size, complexity, performance bottlenecks, optimization opportunities, resource usage, backup recommendations.
Optimization Techniques: whitespace reduction, structure optimization, complexity reduction, performance caching.
Configuration Management
Integrated configuration covers project metadata, language settings + costs, documentation status, template optimization results, module initialization states.
Language Settings: conversation_language (user-facing), agent_prompt_language (internal, often English for cost), documentation language (per language).
Updates trigger configuration file modifications, documentation structure updates, template localization.
See configuration schema and language fields for full field reference and supported language metadata.
Advanced Implementation
For advanced patterns (custom templates, performance caching, batch processing, integration workflows), see references/reference.md and references/examples.md.
Resources
Performance Metrics
| Operation | Typical Duration |
|---|---|
| Complete documentation generation | 2-5 seconds |
| Language detection analysis | ~500 ms |
| Template optimization | 10-30 seconds |
| Configuration updates | ~100 ms |
Memory: base ~50MB, large projects +10-50MB, optimization cache 5-20MB.
File sizes: documentation 50-200KB per project, optimization backups match originals, configuration 5-10KB.
Works Well With
- moai-foundation-core: Core execution patterns and SPEC-driven workflows
- moai-foundation-cc: Claude Code integration and configuration
- moai-workflow-docs: Unified documentation management
- moai-workflow-templates: Template optimization strategies
- moai-library-nextra: Documentation architecture
<!-- moai:evolvable-start id="rationalizations" -->Common Rationalizations
| Rationalization | Reality |
|---|---|
| "project docs are a one-time setup, no need to keep them current" | Stale product.md and tech.md mislead every SPEC written against them. They are living documents. |
| "structure.md will stay accurate since the codebase does not change much" | Every PR that adds a directory invalidates structure.md. Sync on every /moai project invocation. |
| "I know the tech stack, I do not need tech.md" | tech.md is not for you. It is for every agent that consults the project context before acting. |
| "codemaps take too long to generate" | codemaps are the only artifact that gives agents file-level awareness without reading every file. The cost pays for itself. |
| "I will write project docs after the feature is done" | Post-hoc docs capture what was built, not what was intended. Pre-feature docs guide the build. |
<!-- moai:evolvable-end --><!-- moai:evolvable-start id="red-flags" -->Red Flags
- product.md references features that do not exist in the codebase
- tech.md lists a framework version that differs from the actual dependency file
- structure.md missing directories that exist on disk
- codemaps/ directory is empty or missing while the project has 10+ source files
- /moai project last ran more than 30 days ago (check file modification dates)
<!-- moai:evolvable-end --><!-- moai:evolvable-start id="verification" -->Show full SKILL.md (426 more words)Show less
Verification
- product.md exists and describes the current product scope (compare with README)
- tech.md lists dependencies that match the actual lock file (package.json, go.mod, etc.)
- structure.md top-level directories match
lsoutput of the project root - codemaps/ contains at least one codemap file per major package or module
- All three docs updated within the current session or since last structural change
- No placeholder text ("TODO", "TBD") remains in generated documents
<!-- moai:evolvable-end -->Template Optimization (absorbed from moai-workflow-templates)
Code boilerplates, feedback templates, scaffolding, and project template optimization.
Core Capabilities
- Code template library: FastAPI, React, Vue, Next.js boilerplates
- GitHub issue feedback templates: 6 types (bug, feature, question, docs, perf, security)
- Project template optimization: size reduction, complexity analysis, smart merging
- Template version management, backup discovery and restoration
Template Application Workflow
- Identify template category: code boilerplate, feedback template, or project scaffold
- Select template variant matching the project stack and language
- Apply customization variables (project name, author, license, framework version)
- Validate rendered output against schema or existing conventions
- Optionally run template optimizer to reduce redundancy
Template Optimization Process
Analysis metrics: file size, complexity score, redundancy ratio, load performance.
Optimization techniques: whitespace reduction, deduplication, structure simplification.
Always create backup before applying optimization (backup: true).
Documentation Generation (absorbed from moai-docs-generation)
Technical docs generation using Sphinx, MkDocs, TypeDoc, OpenAPI, and Nextra. Covers project configuration discovery, how to integrate with existing docs sites, and best practices for keeping framework documentation and technology guide content current.
Supported Generators
| Generator | Use Case | Primary Format |
|---|---|---|
| Sphinx | Python projects, API docs | RST / Markdown |
| MkDocs | General projects | Markdown |
| TypeDoc | TypeScript libraries | TypeScript JSDoc |
| OpenAPI / Swagger | REST APIs | YAML / JSON |
| Nextra | Next.js docs sites | MDX |
Generation Workflow
- Detect project type and select appropriate generator
- Extract documentation sources: docstrings, JSDoc, OpenAPI specs, SPEC documents
- Apply project language and branding from
.moai/config/sections/language.yaml - Generate output in configured format (Markdown, HTML, PDF)
- Update
/moai syncartifacts: README, CHANGELOG, API reference
JIT Document Loading (absorbed from moai-workflow-jit-docs)
JIT docs (just in time docs) — on-demand documentation discovery and loading based on user intent and conversation context.
Primary Tools
- WebSearch/WebFetch (
,): Official library docs - WebFetch / WebSearch: Latest online documentation
- Read, Grep, Glob: Local project documentation
Trigger Patterns
- User asks specific technical questions about a library or framework
- Technology keyword detected (library name, framework name, API name)
- Domain expertise required (authentication, database, deployment)
- Implementation guidance needed during run phase
Loading Priority
- Local project docs (
.moai/, README, SPEC documents) - WebSearch/WebFetch (official, version-matched library docs)
- WebSearch + WebFetch (latest online resources)
Token budget: 5000 tokens per JIT load. Summarize if source exceeds budget.
© modu-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 25 other files (scripts, references) in .claude/skills/moai-workflow-project of modu-ai/moai-adk.
- SKILL.md
- references/configuration.md
- references/examples.md
- references/language-localization.md
- references/navigator-astx.md
- references/navigator-audit.md
- references/navigator.md
- references/overview.md
- references/reference.md
- references/workflows.md
- schemas/config-schema.json
- schemas/tab_schema.json
- scripts/navigator-audit.sh
- scripts/navigator-enrich.sh
- scripts/navigator-regen.sh
- templates/config-template.json
- templates/doc-templates
- … and 9 more
Open the folder on GitHubat commit a2a184a
Compare with similar skills
Moai Workflow Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Moai Workflow Project this skillmodu-ai/moai-adk | 1.2k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ichartjswanghetommy/ichartjs | 352 | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Shep Workstreamsshep-ai/shep | 264 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Version Bound Cleanuppdparchitect/noodle | 151 | — | ~650 | Automated safety check: Pass | Apache-2.0 | |
| Vc Review Situationwithkynam/vibecode-pro-max-kit | 1.1k | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Ichartjs
wanghetommy/ichartjs
Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.
Shep Workstreams
shep-ai/shep
A skill your agent uses when a large body of work (a version milestone, an epic, a roadmap, a set of PRDs/design docs) needs to be broken into parallel workstreams and executed with the shep CLI.
Version Bound Cleanup
pdparchitect/noodle
Gating migrations and clean-up code behind an update milestone.
Vc Review Situation
withkynam/vibecode-pro-max-kit
A skill your agent uses when you need a read-only situation review and handoff summary of current branch state, local/remote refs, worktrees, active project plans, selected-plan hints, and suggested…
Roadmap
cloudposse/atmos
Maintain and update the Atmos roadmap page (website/src/data/roadmap.js): milestone/initiative/quarter schema, progress-percentage math, the curated featured[] cap (max 6, never auto-modified), and…
More from modu-ai/moai-adk
All 48 skills in this repoSVG Technical Infographic Author
modu-ai/moai-adk
Builds hand-editable SVG diagrams from computed layout coordinates, lints the source and renders a 2x PNG, with rules for when mermaid is the better choice.
MoAI Foundation Core
modu-ai/moai-adk
Reference for MoAI-ADK's core development principles: TRUST 5 quality gates, SPEC-first domain-driven workflow, agent delegation and token budgeting.
MoAI SPEC Workflow
modu-ai/moai-adk
Manages SPEC documents for MoAI-ADK development, with GEARS or EARS requirement notation, acceptance criteria and a link into the Plan-Run-Sync workflow.
MoAI TDD Workflow
modu-ai/moai-adk
Drives test-first development through the RED, GREEN, REFACTOR cycle, with a config switch that selects between TDD and a DDD workflow for existing code.
MoAI Worktree Management
modu-ai/moai-adk
Gives each SPEC its own Git worktree with a registry of active workspaces, base-branch sync and cleanup of merged ones, inside the MoAI-ADK workflow.
CI Watch and Auto-Fix Loop
modu-ai/moai-adk
Watches a pull request's CI checks after creation, separates required from auxiliary failures, applies limited safe fixes and escalates anything semantic to you.
Related
Categories
Questions about Moai Workflow Project
What does Moai Workflow Project do?
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Moai Workflow Project is an agent skill from modu-ai/moai-adk. Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading.
When should I use Moai Workflow Project?
Moai Workflow Project fits situations like: tasks that involve Project management.
How do I install Moai Workflow Project in Claude Code?
Run `npx skills add modu-ai/moai-adk --skill moai-workflow-project -a claude-code`. Or copy the skill folder (.claude/skills/moai-workflow-project in modu-ai/moai-adk) into .claude/skills/moai-workflow-project in your project. Claude Code loads it when a task matches its description.
How do I install Moai Workflow Project in Codex?
Run `npx skills add modu-ai/moai-adk --skill moai-workflow-project -a codex`. Or copy the skill folder (.claude/skills/moai-workflow-project in modu-ai/moai-adk) into .agents/skills/moai-workflow-project in your project. Codex loads it when a task matches its description.
Can I use Moai Workflow Project in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add modu-ai/moai-adk --skill moai-workflow-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/moai-workflow-project, .gemini/skills/moai-workflow-project, .github/skills/moai-workflow-project and .opencode/skills/moai-workflow-project in your project.
What does Moai Workflow Project need to run?
Going by SKILL.md and its folder, Moai Workflow Project needs a shell for the scripts in its folder. Our summary lists: Python 3; A Bash shell. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(git:*), Bash(npm:*), Bash(npx:*), Bash(uv:*), Bash(pip:*), Bash(ls:*), Bash(mkdir:*), Grep, Glob, WebFetch, WebSearch. Compatibility (from SKILL.md): Designed for Claude Code.
Does Moai Workflow Project access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Moai Workflow Project safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Moai Workflow Project use?
Moai Workflow Project is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Moai Workflow Project use?
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15k tokens, read only when the agent opens those files.
What are the alternatives to Moai Workflow Project?
Skills that share tags, products or a category with Moai Workflow Project: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ichartjs (wanghetommy/ichartjs, 352 stars), Shep Workstreams (shep-ai/shep, 264 stars) and Version Bound Cleanup (pdparchitect/noodle, 151 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Moai Workflow Project?
modu-ai (a GitHub organization) maintains it in modu-ai/moai-adk, which has 1,230 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 8, 2026.
Source: modu-ai/moai-adk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.