moai-workflow-project

Generates multilingual project documentation, optimizes templates, and audits SPEC drift for Claude Code projects.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/taewook486/Masters_degree --skill moai-workflow-project-taewook486
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-workflow-project
Source: https://github.com/taewook486/Masters_degree/tree/main/.claude/skills/moai-workflow-project
Command: npx skills add https://github.com/taewook486/Masters_degree --skill moai-workflow-project-taewook486

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Keeping project documentation (product.md, structure.md, tech.md), multilingual docs, and templates accurate and synchronized with the actual codebase is tedious and error-prone. This Skill automates documentation scaffolding, language initialization, template optimization, and design-vs-implementation drift auditing in Claude Code projects. ## Core Features & Use Cases - Documentation Management: Generates product/structure/tech documents from SPECs, supports Sphinx, MkDocs, TypeDoc, OpenAPI, and Nextra generators, and exports to Markdown, HTML, or PDF. - Multilingual Initialization: Auto-detects project language, creates per-language doc directories (docs/ko, docs/en), and localizes agent prompts with token cost analysis. - Template Optimization: Analyzes template size, complexity, and redundancy, then applies whitespace reduction and deduplication with automatic backups. - Navigator Audit: Diffs design-intent docs against the SPEC capability map to surface missing and orphan SPECs via deterministic bash scripts. - Use Case: After running /moai project on a repository, invoke the audit to see which features described in product.md never became SPECs and which SPECs drifted out of the design narrative before a release cut. ## Quick Start Ask the agent to initialize project documentation with Korean language support and then run the navigator audit to check for drift between design docs and SPECs.

Frequently Asked Questions about moai-workflow-project

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

FAQPage Schema
How do I generate project documentation from a SPEC file?▼

Provide a complete SPEC object with id, title, requirements, and api_endpoints, then run the documentation generation workflow. It produces structured Markdown with requirement checklists and API reference tables, and supports Sphinx, MkDocs, TypeDoc, OpenAPI, and Nextra generators.

How do I detect drift between design docs and SPECs?▼

Run the navigator audit via /moai project --audit after regenerating the capability map. It diffs product.md, structure.md, and tech.md against capability-map.md and reports Missing SPECs, Orphan SPECs, and Matched entries in audit-report.md and audit-report.json.

Does the documentation system support multiple languages?▼

Yes. It auto-detects project language from file content, config files, and locale, then creates per-language directories like docs/ko and docs/en with language negotiation. Agent prompts can stay in English to reduce token cost while conversation language is localized.

What happens if the capability map or design docs are missing during an audit?▼

The audit is fail-open: it exits 0, writes a minimal report naming the missing input, emits a valid empty audit-report.json, and logs a warning to navigator-warnings.log. It never aborts or modifies input files.

Is template optimization safe to run on existing files?▼

Yes, when backup_first is enabled the optimizer creates a timestamped backup before applying whitespace reduction, deduplication, and structure simplification. If optimization fails, templates can be restored from the backup directory.