🎯 Goal
To introduce multilingual support for OpenSpec's core workflow files, ensuring developers and AI assistants globally can seamlessly generate, understand, and utilize OpenSpec specification files in languages other than English.

💡 The Need
OpenSpec's core function is to standardize the workflow for AI coding assistants. Currently, the workflow and examples are primarily English-centric. To boost global adoption, we must ensure the core OpenSpec files themselves—especially those generated by the AI assistant—can be created and processed in non-English languages.

Since files like tasks.md and proposal.md are AI outputs, it is critical that the AI assistant follows the user/project's preferred language when generating these artifacts.

✨ Proposed Features
Core Artifact Multilingualism:

Ensure AI assistants can generate and process non-English versions of proposal.md, tasks.md, and spec.md files.

AI assistants should be able to read and understand project contexts and conventions defined in non-English within openspec/project.md.

The structure and headers of core files should remain consistent, but the content should be generated in the target language.

AI Assistant Integration & Configuration:

Consider adding a --lang option to openspec init to initialize project.md templates and update the AGENTS.md instructions accordingly.

Clearly instruct compatible AI assistants to use the user-specified language when generating new OpenSpec files.

Key Documentation Translation:

Translate core documentation, such as instructions in AGENTS.md, into major international languages.