Multi-Language Guide
Configure OpenSpec to generate artifacts in languages other than English.
Quick Setup
Section titled “Quick Setup”For a new project, set the language during initialization:
openspec init --language "Portuguese (pt-BR)"This writes the language instruction to openspec/config.yaml. If the project
already has a config, edit its context field directly so existing project
guidance is preserved.
You can also configure the same behavior manually:
Add a language instruction to your openspec/config.yaml:
schema: spec-driven
context: | Language: Portuguese (pt-BR) All artifacts must be written in Brazilian Portuguese. Keep OpenSpec structural headings and SHALL/MUST keywords in English.
# Your other project context below... Tech stack: TypeScript, React, Node.jsThat’s it. All generated artifacts will now be in Portuguese.
OpenSpec’s document structure and normative SHALL/MUST keywords remain in
English because validation relies on them. The surrounding requirement and
scenario prose can use your selected language.
Language Examples
Section titled “Language Examples”Portuguese (Brazil)
Section titled “Portuguese (Brazil)”context: | Language: Portuguese (pt-BR) All artifacts must be written in Brazilian Portuguese.Spanish
Section titled “Spanish”context: | Idioma: Español Todos los artefactos deben escribirse en español.Chinese (Simplified)
Section titled “Chinese (Simplified)”context: | 语言:中文(简体) 所有产出物必须用简体中文撰写。Japanese
Section titled “Japanese”context: | 言語:日本語 すべての成果物は日本語で作成してください。French
Section titled “French”context: | Langue : Français Tous les artefacts doivent être rédigés en français.German
Section titled “German”context: | Sprache: Deutsch Alle Artefakte müssen auf Deutsch verfasst werden.Handle Technical Terms
Section titled “Handle Technical Terms”Decide how to handle technical terminology:
context: | Language: Japanese Write in Japanese, but: - Keep technical terms like "API", "REST", "GraphQL" in English - Code examples and file paths remain in EnglishCombine with Other Context
Section titled “Combine with Other Context”Language settings work alongside your other project context:
schema: spec-driven
context: | Language: Portuguese (pt-BR) All artifacts must be written in Brazilian Portuguese.
Tech stack: TypeScript, React 18, Node.js 20 Database: PostgreSQL with Prisma ORMVerification
Section titled “Verification”To verify your language config is working:
# Check the instructions - should show your language contextopenspec instructions proposal --change my-change
# Output will include your language contextRelated Documentation
Section titled “Related Documentation”- Customization Guide - Project configuration options
- Workflows Guide - Full workflow documentation
HagiCode
HagiCode is an agentic coding workspace: structured workflows, multi-agent execution, and Hero Dungeon views turn ideas into shipped software.
Turn ideas into polished, usable software with a smarter, faster, and more enjoyable agentic coding workflow.

- SmartStructured workflows turn intent into an executable path from idea to shipped change.
- EfficientMulti-agent workflows keep research, implementation, and review moving in parallel.
- FunHero Dungeon interfaces make long coding sessions visual, collaborative, and rewarding.
Ecosystem Sites
Quick Links
Community
© 2026 HagiCode