reins-method 0.1.2 → 0.1.3

package/README.md

@@ -38,6 +38,31 @@ your company's or project's specific conventions and skills.
 
 ---
 
+## What it looks like
+
+```
+you:    Add a password reset endpoint to the API
+
+agent:  Detected stack: ruby (Gemfile) + node (package.json)
+        Loading adapter: acme-rails (matches `ruby`)
+
+        This looks like a new feature. Proposed breakdown:
+          1. POST /password_resets        — request a reset token
+          2. POST /password_resets/:token — consume token, set new password
+          3. Wire up email delivery via existing Mailer
+
+        Architecture decision needed: store reset tokens in the DB or Redis
+        with a TTL? Flagging this before we proceed.
+
+        Create a context file and start on step 1?
+```
+
+The orchestrator instructions live in your AI agent's global config — every
+project you open gets this behavior automatically, with no REINS files added to
+the repo.
+
+---
+
 ## Quick start
 
 ```bash
@@ -50,6 +75,8 @@ menus for:
 - optionally fill in your company/personal coding standards
 - optionally enable Historic Mode (performance tracking)
 - optionally install an adapter pack
+- choose your interaction language (default: English)
+- choose your documentation language (default: English)
 
 Then restart your terminal/agent and run:
 
@@ -160,7 +187,7 @@ proactively. Use the built-in meta-skill to create one:
 reins new-skill my-skill
 ```
 
-or invoke `skill-creator` for guided creation. See [SKILLS.md](SKILLS.md).
+or invoke `reins-skill-creator` for guided creation. See [SKILLS.md](SKILLS.md).
 
 ---
 
@@ -179,10 +206,10 @@ external install:
 | `reins-senior-engineer` | Test-first (red/green/refactor), 100% passing before review, no shortcuts |
 
 Each is callable individually (e.g. "give me the system architect's take on
-this"). Before a breakdown, ask for **`party-mode`** — a facilitator picks the
+this"). Before a breakdown, ask for **`reins-party-mode`** — a facilitator picks the
 relevant personas (always the business analyst) and announces the lineup, each
 speaks in turn, then a synthesizer distills it into what matters for the
-breakdown. Before proposing a commit message, ask for **`code-review`** — it
+breakdown. Before proposing a commit message, ask for **`reins-code-review`** — it
 launches independent subagents (logic, security, and requirements if a SPEC
 exists) for adversarial, parallel review, then closes with a plain-language
 summary of what needs fixing before merge.
@@ -214,6 +241,13 @@ these tools if you choose to install them separately:
   pip install "headroom-ai[all]"
   headroom wrap <agent>
   ```
+  Every session must be started through the wrapper (`headroom wrap claude`
+  instead of `claude`). To avoid typing that every time, alias it in your shell
+  rc file (e.g. `~/.zshrc`):
+  ```bash
+  alias claude="headroom wrap claude"
+  ```
+  This is fully optional — REINS works the same with or without headroom.
 - **[graphify](https://github.com/safishamsi/graphify)** — generates a knowledge
   graph of your codebase (code, docs, SQL, PDFs, images) at `graphify-out/`. REINS's
   orchestrator (`1_orchestrator.md` §2.5) automatically reads
@@ -274,7 +308,7 @@ reins-method/
 │   ├── workflow/        ← 1_orchestrator, 2_new_task, 3_implement, 4_close_task
 │   ├── templates/        ← context, current_task, adapter, skill, spec, plan templates
 │   ├── evaluation/        ← historic mode docs + templates
-│   └── skills/            ← skill-creator, party-mode, code-review,
+│   └── skills/            ← reins-skill-creator, reins-party-mode, reins-code-review,
 │                              reins-business-analyst, reins-technical-writer,
 │                              reins-product-manager, reins-ux-designer,
 │                              reins-system-architect, reins-senior-engineer
@@ -301,7 +335,7 @@ authors — nothing here is a fork or a dependency):
   `specs/<type>_<slug>/step-NN-{spec,plan}.md` and `core/templates/{spec,plan}.md`.
 - **[BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD)** — the
   multi-persona "Party Mode" discussion and the adversarial, parallel code-review
-  pattern, reimplemented natively as `party-mode`, `code-review`, and the six
+  pattern, reimplemented natively as `reins-party-mode`, `reins-code-review`, and the six
   `reins-business-analyst`/`reins-technical-writer`/`reins-product-manager`/
   `reins-ux-designer`/`reins-system-architect`/`reins-senior-engineer` persona skills.
 - **[headroom](https://github.com/chopratejas/headroom)** — token-efficient context
@@ -312,8 +346,8 @@ authors — nothing here is a fork or a dependency):
   `graphify-out/GRAPH_REPORT.md` output if present (see "Companion tools" above).
 - **[ruflo](https://github.com/ruvnet/ruflo)** — informed thinking on fluid
   interlinking of workflow phases; no dedicated subsystem was added, but it shaped
-  how `1_orchestrator.md` surfaces optional steps (project map, party-mode,
-  code-review) inline in the workflow diagram.
+  how `1_orchestrator.md` surfaces optional steps (project map, reins-party-mode,
+  reins-code-review) inline in the workflow diagram.
 
 ---
 

package/SKILLS.md

@@ -26,8 +26,8 @@ reins new-skill my-skill
 ```
 
 This scaffolds `~/.reins/user/skills/my-skill/SKILL.md`. Or, for guided creation, ask
-your agent to use the **skill-creator** meta-skill
-(`~/.reins/core/skills/skill-creator/SKILL.md`) — it will ask what the skill should do,
+your agent to use the **reins-skill-creator** meta-skill
+(`~/.reins/core/skills/reins-skill-creator/SKILL.md`) — it will ask what the skill should do,
 when it should trigger, whether it's read-only, and where it belongs (user vs.
 adapter), then draft the file for your review before writing it.
 

package/bin/reins

@@ -287,6 +287,9 @@ generate_bridges() {
   active_adapters="$(config_adapters | tr '\n' ' ')"
   local historic
   historic="$(config_get historic_mode)"
+  local language doc_language
+  language="$(config_get language)"
+  doc_language="$(config_get doc_language)"
 
   local skills_md=""
   while IFS=$'\t' read -r dir reins_name; do
@@ -318,6 +321,10 @@ ${active_adapters:-(none configured — generic conventions only)}
 ## Historic mode
 ${historic:-off}
 
+## Language
+- Interaction language: ${language:-english}
+- Documentation language: ${doc_language:-english}
+
 ## Available skills
 On-demand only — never load proactively (see \`1_orchestrator.md\` §5).
 ${skills_md:-(none)}
@@ -342,6 +349,7 @@ cmd_install() {
   print_banner
   local non_interactive=0
   local arg_agent="" arg_standards="" arg_historic="" arg_adapter=""
+  local arg_language="" arg_doc_language=""
   for arg in "$@"; do
     case "$arg" in
       --non-interactive) non_interactive=1 ;;
@@ -349,6 +357,8 @@ cmd_install() {
       --standards=*)     arg_standards="${arg#--standards=}" ;;
       --historic=*)      arg_historic="${arg#--historic=}" ;;
       --adapter=*)       arg_adapter="${arg#--adapter=}" ;;
+      --language=*)      arg_language="${arg#--language=}" ;;
+      --doc-language=*)  arg_doc_language="${arg#--doc-language=}" ;;
     esac
   done
 
@@ -394,6 +404,19 @@ cmd_install() {
   fi
   config_set agent "$agent"
 
+  local language doc_language
+  if [ "$non_interactive" -eq 1 ]; then
+    language="${arg_language:-english}"
+    doc_language="${arg_doc_language:-english}"
+  else
+    read -r -p "? Language to interact in (agent replies, skill/persona output)? [english] " language
+    language="${language:-english}"
+    read -r -p "? Language for documentation (code comments, docstrings, READMEs, etc.)? [english] " doc_language
+    doc_language="${doc_language:-english}"
+  fi
+  config_set language "$language"
+  config_set doc_language "$doc_language"
+
   touch "$USER_DIR/standards/company.md" "$USER_DIR/standards/personal.md"
   if [ ! -s "$USER_DIR/standards/company.md" ]; then
     cat > "$USER_DIR/standards/company.md" <<'EOF'
@@ -623,6 +646,8 @@ cmd_status() {
   fi
   log "Agent: $(config_get agent || echo 'not configured')"
   log "Historic mode: $(config_get historic_mode || echo 'off')"
+  log "Interaction language: $(config_get language || echo 'english')"
+  log "Documentation language: $(config_get doc_language || echo 'english')"
   local adapters
   adapters="$(config_adapters | tr '\n' ' ')"
   log "Adapters: ${adapters:-none}"
@@ -763,6 +788,7 @@ Usage:
   reins install              First-time setup (interactive wizard)
   reins install --non-interactive --agent=<id> [--standards=yes|no]
                               [--historic=on|off] [--adapter=<path>]
+                              [--language=<lang>] [--doc-language=<lang>]
                              Non-interactive setup, driven by flags
                              (used by `npx reins-method install`)
   reins update                Pull latest core, regenerate agent bridge files

package/core/skills/reins-business-analyst/SKILL.md

@@ -16,7 +16,7 @@ tags: [persona, party-mode, strategy]
 - The user asks for a "business analyst" or "strategic" perspective on a task
 - A task touches multiple stakeholders, competing priorities, or "why are we doing
   this" is unclear
-- Invoked as part of `core/skills/party-mode/SKILL.md`
+- Invoked as part of `core/skills/reins-party-mode/SKILL.md`
 
 ## Context
 

package/core/skills/{code-review → reins-code-review}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: code-review
+name: reins-code-review
 description: >
   Adversarial, parallel code review using independent subagents — not role-play.
   Michael (Facilitator) announces the session and calls in Dwight (logic/edge-case

package/core/skills/{party-mode → reins-party-mode}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: party-mode
+name: reins-party-mode
 description: >
   Run a multi-perspective discussion over a task description before proposing a
   breakdown. Michael (Facilitator) picks the relevant persona lenses (always

package/core/skills/reins-product-manager/SKILL.md

@@ -14,7 +14,7 @@ tags: [persona, party-mode, product]
 
 - The user asks for a "PM" or "product" perspective on a task
 - A new task is being defined and its user value/purpose isn't yet explicit
-- Invoked as part of `core/skills/party-mode/SKILL.md` (always included), or
+- Invoked as part of `core/skills/reins-party-mode/SKILL.md` (always included), or
   alongside `core/workflow/2_new_task.md` Step 1
 
 ## Context

package/core/skills/reins-senior-engineer/SKILL.md

@@ -15,7 +15,7 @@ tags: [persona, party-mode, implementation]
 - The user asks for a "senior engineer" or "implementation" perspective
 - `core/workflow/3_implement.md` Step 3 (Implement) is reached and no adapter
   override defines a TDD/SDD process for this stack
-- Invoked as part of `core/skills/party-mode/SKILL.md` when the implementation
+- Invoked as part of `core/skills/reins-party-mode/SKILL.md` when the implementation
   approach itself is in question
 
 ## Context

package/core/skills/{skill-creator → reins-skill-creator}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: skill-creator
+name: reins-skill-creator
 description: Guides the user through creating a new REINS skill (or adapter pack skill) — asks the right questions, drafts a SKILL.md following the contract in core/templates/skill.md, and writes it to the right location.
 tags: [meta, authoring]
 ---

package/core/skills/reins-system-architect/SKILL.md

@@ -15,7 +15,7 @@ tags: [persona, party-mode, architecture]
 - The user asks for an "architect" or "architecture" perspective
 - A task has a step that requires choosing between two or more valid technical
   approaches with different trade-offs
-- Invoked as part of `core/skills/party-mode/SKILL.md` when an architecture decision
+- Invoked as part of `core/skills/reins-party-mode/SKILL.md` when an architecture decision
   is likely, or as part of `core/workflow/2_new_task.md` Step 4
 
 ## Context

package/core/skills/reins-technical-writer/SKILL.md

@@ -15,7 +15,7 @@ tags: [persona, party-mode, docs]
 - The user asks for a "technical writer" perspective, or to review/restructure a
   SPEC, README, ADR, or API doc for clarity
 - A piece of documentation has grown into a wall of text and needs structure
-- Invoked as part of `core/skills/party-mode/SKILL.md` when docs/spec clarity is the
+- Invoked as part of `core/skills/reins-party-mode/SKILL.md` when docs/spec clarity is the
   concern
 
 ## Context

package/core/skills/reins-ux-designer/SKILL.md

@@ -14,7 +14,7 @@ tags: [persona, party-mode, ux]
 
 - The user asks for a "UX" or "design" perspective on a task
 - A task involves a UI, user-facing flow, form, or interaction change
-- Invoked as part of `core/skills/party-mode/SKILL.md` when the task is user-facing
+- Invoked as part of `core/skills/reins-party-mode/SKILL.md` when the task is user-facing
 
 ## Context
 

package/core/templates/skill.md

@@ -8,7 +8,7 @@ Scaffold a new one with:
 ```
 reins new-skill <name>
 ```
-or invoke the `skill-creator` meta-skill (`~/.reins/core/skills/skill-creator/SKILL.md`)
+or invoke the `reins-skill-creator` meta-skill (`~/.reins/core/skills/reins-skill-creator/SKILL.md`)
 for guided creation.
 
 ---

package/core/workflow/1_orchestrator.md

@@ -21,9 +21,9 @@ REINS Method is installed once, globally, at `~/.reins/`. **No REINS files ever
 │   ├── workflow/             ← phase files (this file + 2/3/4)
 │   ├── templates/            ← context, current_task, adapter, skill templates
 │   ├── evaluation/           ← historic mode templates
-│   └── skills/               ← meta-skills (e.g. skill-creator)
+│   └── skills/               ← meta-skills (e.g. reins-skill-creator)
 ├── user/                     ← user-owned, never touched by `reins update`
-│   ├── config.yaml           ← name, agent, active adapter, historic mode
+│   ├── config.yaml           ← name, agent, active adapter, historic mode, language, doc_language
 │   ├── standards/            ← company.md (floor) + personal.md
 │   ├── adapters/             ← installed adapter packs
 │   ├── skills/               ← user's custom skills
@@ -41,6 +41,24 @@ REINS Method is installed once, globally, at `~/.reins/`. **No REINS files ever
 
 ---
 
+## 0.5 — Language
+
+Your agent bridge file's "Language" section (generated from `~/.reins/user/config.yaml`'s
+`language` and `doc_language`, both default `english`) sets two independent things for
+this entire session:
+
+- **Interaction language** (`language`) — the language you use to talk to the user:
+  chat replies, questions, breakdowns, and all output from REINS skills/personas
+  (party-mode, code-review, etc.).
+- **Documentation language** (`doc_language`) — the language used when *writing*:
+  code comments, docstrings, commit messages, READMEs, SPECs, and other generated docs.
+
+If a project's existing code/docs are already consistently written in a different
+language than `doc_language`, follow the project's existing convention instead —
+don't introduce a second language into an established codebase. When in doubt, ask.
+
+---
+
 ## 1 — Identify the project
 
 1. Determine the project root (nearest ancestor directory containing `.git`, or the current working directory if none).
@@ -150,6 +168,7 @@ When `branches` has more than one entry, before proceeding:
 | File | When |
 |---|---|
 | `core/workflow/1_orchestrator.md` | Session start (this file) |
+| Language settings (§0.5) | Session start |
 | Active context file (§4) | Session start |
 | Adapter standards (§3), or `~/.reins/user/standards/*.md` | Session start |
 | `graphify-out/GRAPH_REPORT.md` (§2.5) | Session start, only if present |
@@ -178,7 +197,7 @@ New task arrives
   → load project map if present (§2.5)
   → load adapter standards, or generic standards (§3)
   → understand task + epic
-  → optional: party-mode discussion (core/skills/party-mode/SKILL.md)
+  → optional: party-mode discussion (core/skills/reins-party-mode/SKILL.md)
   → propose breakdown (per component if multi-stack)
   → flag architecture decisions
   → wait for confirmation
@@ -194,7 +213,7 @@ User gives close order:
   → summarize what was done
   → assess epic impact
   → identify next step
-  → optional: code review (core/skills/code-review/SKILL.md)
+  → optional: code review (core/skills/reins-code-review/SKILL.md)
   → review PR comments
   → propose commit message(s)
   → record historic entry (if historic mode is on)
@@ -207,6 +226,7 @@ User gives close order:
 ## 7 — General rules (permanent — never override)
 
 - Never write or modify a SPEC — that step belongs to the user
+- Apply the configured interaction and documentation languages (§0.5) at all times
 - Never implement before the SPEC is provided and confirmed
 - Never make architecture decisions silently — surface trade-offs and wait for input
 - Never modify approved tests

package/core/workflow/2_new_task.md

@@ -39,7 +39,7 @@ This context shapes every decision we make — architecture, naming, scope.
 
 If the user asks for a multi-perspective discussion ("party mode", "discuss this
 first", or the task has real ambiguity, multiple stakeholders, or an unclear "why"),
-invoke `core/skills/party-mode/SKILL.md` now, before proposing the breakdown. Its
+invoke `core/skills/reins-party-mode/SKILL.md` now, before proposing the breakdown. Its
 synthesis informs Step 3 and Step 4 below — it does not replace them.
 
 ---

package/core/workflow/4_close_task.md

@@ -61,7 +61,7 @@ If there is no clear next step, say so explicitly.
 
 ## Optional — Code review
 
-On request, invoke `core/skills/code-review/SKILL.md` against the full diff for this
+On request, invoke `core/skills/reins-code-review/SKILL.md` against the full diff for this
 task before proposing the commit message in Step 5. Its findings are presented to
 the user, who decides whether to address anything before proceeding.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "reins-method",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "REINS Method — agent-agnostic AI pair-programming workflow. Interactive installer.",
   "license": "MIT",
   "homepage": "https://github.com/gustavodiasp/reins-method",

package/tools/installer/cli.js

@@ -137,12 +137,34 @@ async function runInstall() {
     process.exit(0);
   }
 
+  const language = await clack.text({
+    message: 'Language to interact in (agent replies, skill/persona output)?',
+    placeholder: 'english',
+    defaultValue: 'english',
+  });
+  if (clack.isCancel(language)) {
+    clack.cancel('Install cancelled.');
+    process.exit(0);
+  }
+
+  const docLanguage = await clack.text({
+    message: 'Language for documentation (code comments, docstrings, READMEs, etc.)?',
+    placeholder: 'english',
+    defaultValue: 'english',
+  });
+  if (clack.isCancel(docLanguage)) {
+    clack.cancel('Install cancelled.');
+    process.exit(0);
+  }
+
   const args = [
     'install',
     '--non-interactive',
     `--agent=${agent}`,
     `--standards=${wantsStandards ? 'yes' : 'no'}`,
     `--historic=${wantsHistoric ? 'on' : 'off'}`,
+    `--language=${language || 'english'}`,
+    `--doc-language=${docLanguage || 'english'}`,
   ];
   if (adapterPath) args.push(`--adapter=${adapterPath}`);