Multi-Language Guide

Configure OpenSpec to generate artifacts in languages other than English.

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.js

That’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

Portuguese (Brazil)

context: |
  Language: Portuguese (pt-BR)
  All artifacts must be written in Brazilian Portuguese.

Spanish

context: |
  Idioma: Español
  Todos los artefactos deben escribirse en español.

Chinese (Simplified)

context: |
  语言：中文（简体）
  所有产出物必须用简体中文撰写。

Japanese

context: |
  言語：日本語
  すべての成果物は日本語で作成してください。

French

context: |
  Langue : Français
  Tous les artefacts doivent être rédigés en français.

German

context: |
  Sprache: Deutsch
  Alle Artefakte müssen auf Deutsch verfasst werden.

Tips

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 English

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 ORM

Verification

To verify your language config is working:

# Check the instructions - should show your language context
openspec instructions proposal --change my-change

# Output will include your language context

Customization Guide - Project configuration options
Workflows Guide - Full workflow documentation

HagiCode

HagiCode is an agentic coding workspace. Rich, convenient UI interactions make planning, agent execution, and project work approachable and easy to navigate, creating an engaging development experience.

Explore an engaging development experience through rich, convenient UI interactions.

Visit HagiCode Read the documentation

SmartOpenSpec workflows turn intent into an executable path, from proposal to design, tasks, and a shipped change.
EfficientMulti-agent execution keeps research, implementation, and review moving in parallel, across several repositories and the Agent CLIs you already use.
InterestingRich, convenient UI interactions make planning, agent execution, and project work approachable and easy to navigate.

Download for Windows

Get it from Microsoft Store

All downloads

HagiCode makes planning, agent execution, and project work approachable through rich, convenient UI interactions: https://www.hagicode.com/

Turn ideas into shipped software.

HagiCode is an agentic coding workspace. OpenSpec workflows plan the change, multi-agent execution carries it out, and Hero Scenario makes the long run visible, so ideas become shipped software.

Download HagiCode Product Docs

Smart: OpenSpec workflows turn intent into a path from proposal to shipped change.
Efficient: Multi-agent execution runs research, build, and review in parallel.
Fun: Rich UI interactions make planning, agent work, and projects easier to follow.