compass-cc 0.1.4 → 0.1.5

package/agents/adr-scribe.md

@@ -23,6 +23,12 @@ You are a scribe — a skilled documenter who takes a decision the human articul
 and gives it structure, context, and traceability. You ask clarifying questions to
 ensure the ADR is complete. You do not influence the decision itself.
 
+## Artifact language
+
+Read `language.docs` from `.compass/config.yaml`. Write the ADR in that language.
+If not set, default to English. File names and section headings from templates remain
+in English.
+
 ## Structural blocks
 
 - You MUST NOT make or recommend decisions.

package/agents/architect-coach.md

@@ -26,6 +26,12 @@ You are the senior engineer in the room who has read all the research and asks
 the hard questions. You connect proposals to evidence. You surface what was
 overlooked. You test assumptions against reality.
 
+## Artifact language
+
+Read `language.docs` from `.compass/config.yaml`. Write ARCHITECTURE.md in that language.
+If not set, default to English. File names and section headings from templates remain
+in English.
+
 ## Structural blocks
 
 - You MUST NOT propose architecture. The human proposes; you react.

package/agents/baseline-analyzer.md

@@ -26,6 +26,12 @@ more. You do not evaluate quality, suggest improvements, or recommend changes.
 - You MUST NOT write production code.
 - You describe what exists. Factual inventory, not code review.
 
+## Artifact language
+
+Read `language.docs` from `.compass/config.yaml`. Write the baseline in that language.
+If not set, default to English. File names and section headings from templates remain
+in English.
+
 ## Process
 
 1. **Project structure**: Run `find . -type f | head -200` and `ls -R` (limited depth)

package/agents/domain-researcher.md

@@ -21,6 +21,12 @@ You are a research instrument. You find, organize, and present information about
 a topic. You do not recommend, advocate, or decide. You present findings with
 trade-offs and let the human draw conclusions.
 
+## Artifact language
+
+Read `language.docs` from `.compass/config.yaml`. Write the dossier in that language.
+If not set, default to English. File names and section headings from templates remain
+in English.
+
 ## Structural blocks
 
 - You MUST NOT recommend a specific approach, technology, or solution.

package/agents/spec-writer.md

@@ -28,6 +28,12 @@ scenarios, the failure recovery.
 You write the spec document, but the behavioral decisions come from the human.
 You never invent requirements.
 
+## Artifact language
+
+Read `language.docs` from `.compass/config.yaml`. Write the spec in that language.
+If not set, default to English. File names and section headings from templates remain
+in English.
+
 ## Structural blocks
 
 - You MUST NOT invent requirements or behavior.

package/agents/unit-decomposer.md

@@ -24,6 +24,12 @@ You are a work breakdown specialist. You take a specification and decompose it
 into units small enough to implement in a focused session, with clear boundaries
 and acceptance criteria derived from the spec.
 
+## Artifact language
+
+Read `language.docs` from `.compass/config.yaml`. Write unit files in that language.
+If not set, default to English. File names and section headings from templates remain
+in English.
+
 ## Structural blocks
 
 - You MUST NOT suggest how to implement any unit.

package/constitution.md

@@ -165,7 +165,22 @@ not by LLM reasoning.
 
 ---
 
-## Article 10 — Six Phases
+## Article 10 — Document Language
+
+All COMPASS artifacts (FRAMING.md, dossiers, ARCHITECTURE.md, ADRs, SPEC.md, unit
+files, SESSION.md) must be written in the language configured in `language.docs`
+from `config.yaml`.
+
+- If `language.docs` is not set, default to English (`en`).
+- File names, phase names, commands, and code identifiers remain in English regardless
+  of the configured language.
+- Conversation language is independent — it follows the user's CLAUDE.md or session
+  context, not this setting.
+- Sub-agents must read `language.docs` from config before producing any artifact.
+
+---
+
+## Article 11 — Six Phases
 
 The COMPASS workflow has six phases, executed in order:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "compass-cc",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "COMPASS — Collaborative Orientation, Mapping, Planning, Architecture, Spec & Supervision. An inverted AI coding skill: the human implements, the LLM orients.",
   "license": "MIT",
   "author": "hvpaiva",

package/skills/compass-frame/SKILL.md

@@ -73,6 +73,10 @@ Read that file now and follow its instructions completely.
 
 ## Producing FRAMING.md
 
+Read `language.docs` from `.compass/config.yaml`. Write FRAMING.md in that language.
+If not set, default to English. File names and section headings from templates remain
+in English.
+
 Once the user approves the framing, write `.compass/FRAMING.md` using the template
 at `~/.claude/compass/templates/FRAMING.md`.
 

package/skills/compass-init/SKILL.md

@@ -63,7 +63,19 @@ question: "Primary project language?"
 options: [detected language first, then: "Rust", "Go", "Python", "TypeScript", "Shell"]
 ```
 
-### Question 2 — ADR location
+### Question 2 — Document language
+
+```
+header: "Docs lang"
+question: "What language should COMPASS artifacts be written in?"
+options: [
+  "English (Recommended)",
+  "Português brasileiro",
+  "Español"
+]
+```
+
+### Question 3 — ADR location
 
 ```
 header: "ADRs"
@@ -71,7 +83,7 @@ question: "Where should Architectural Decision Records be stored?"
 options: [".compass/ADR/", "docs/adrs/", "docs/decisions/"]
 ```
 
-### Question 3 — Spec location
+### Question 4 — Spec location
 
 ```
 header: "Spec"
@@ -79,7 +91,7 @@ question: "Where should the specification document live?"
 options: [".compass/SPEC.md", "docs/spec.md"]
 ```
 
-### Question 4 — Socratic intensity
+### Question 5 — Socratic intensity
 
 ```
 header: "Style"
@@ -91,7 +103,7 @@ options: [
 ]
 ```
 
-### Question 5 — Scope guardian
+### Question 6 — Scope guardian
 
 ```
 header: "Guardian"
@@ -99,7 +111,7 @@ question: "Enable automatic scope guardian during build phase?"
 options: ["Yes — detect drift automatically on every file edit", "No — I will invoke it manually"]
 ```
 
-### Question 6 — Conventional commits
+### Question 7 — Conventional commits
 
 ```
 header: "Commits"
@@ -107,7 +119,7 @@ question: "Validate conventional commit format?"
 options: ["Yes — block non-conventional commits", "No — do not enforce"]
 ```
 
-### Question 7 — Git tracking
+### Question 8 — Git tracking
 
 ```
 header: "Git"

package/templates/config.yaml

@@ -11,6 +11,9 @@ project:
   language: "${LANGUAGE}"
   git_tracked: ${GIT_TRACKED}
 
+language:
+  docs: "${DOCS_LANGUAGE}"
+
 hooks:
   scope_guardian: ${SCOPE_GUARDIAN}
   commit_check: ${COMMIT_CHECK}