trackops 2.0.0 → 2.0.2

package/skills/trackops/SKILL.md

@@ -1,89 +1,87 @@
 ---
 name: "trackops"
-description: "Global TrackOps skill that prepares your agent for local project orchestration and operational automation, ensures the runtime on first use, and guides per-project activation with optional OPERA."
-metadata:
-  version: "2.0.0"
-  type: "global"
-  triggers:
-    - "install trackops"
-    - "skills.sh"
-    - "trackops init"
-    - "trackops opera install"
-    - "opera handoff"
+description: "Skill global de TrackOps para preparar al agente, exigir la instalacion explicita del runtime con npm y guiar la activacion local de TrackOps y OPERA dentro de cada repositorio."
 ---
 
 # TrackOps
 
-Use this skill in two layers.
+Si la conversacion y el proyecto deben trabajar en ingles, lee `locales/en/SKILL.md` antes de seguir.
 
-## 1. Global skill layer
+## Capa global
 
-Install it with:
+Instala la skill del marketplace con:
 
 ```bash
 npx skills add Baxahaun/trackops
 ```
 
-Before relying on the CLI, run:
+Despues, confirma que el runtime `trackops` existe. Si no esta disponible, pide al usuario que lo instale de forma explicita:
 
 ```bash
-node scripts/bootstrap-trackops.js
+npm install -g trackops
+trackops --version
 ```
 
-That bootstrap ensures the `trackops` runtime and records state in `~/.trackops/runtime.json`.
+Reglas:
 
-## 2. Local project layer
+- la skill no debe instalar paquetes ni ejecutar codigo remoto por si sola
+- el runtime se instala con un paso visible y auditable
+- la skill puede verificar `trackops --version`, pero no debe encadenar instalaciones silenciosas
+- la skill no debe crear archivos dentro de un repositorio por si sola
 
-Inside a repository:
+## Capa local del proyecto
+
+Dentro del repositorio:
 
 ```bash
 trackops init
 trackops opera install
 ```
 
-Core rules:
+Reglas base:
 
-- treat the global skill install as non-invasive
-- use `ops/contract/operating-contract.json` as the machine contract when it exists
-- use `ops/project_control.json` as the operational source of truth for backlog and state
-- use `ops/policy/autonomy.json` before approval-sensitive actions
-- use `/.env` and `/.env.example` as the environment contract
-- keep generated operational docs under `ops/`
-- support `trackops locale get|set` and `trackops doctor locale` when language matters
+- trata la skill global como capa de instrucciones
+- trata la instalacion del runtime como explicita y separada
+- usa `ops/contract/operating-contract.json` como contrato de maquina cuando exista
+- usa `ops/project_control.json` como fuente de verdad operativa
+- usa `ops/policy/autonomy.json` antes de acciones sensibles
+- usa `/.env` y `/.env.example` como contrato de entorno
+- deja la documentacion operativa generada dentro de `ops/`
+- usa `trackops locale get|set` y `trackops doctor locale` cuando el idioma importe
 
-## OPERA onboarding
+## Onboarding de OPERA
 
-OPERA no longer assumes every user is technical.
+OPERA ya no asume que todo usuario es tecnico.
 
-When OPERA starts, TrackOps classifies:
+TrackOps clasifica:
 
-- user technical level
-- current project state
-- available documentation
+- nivel tecnico del usuario
+- estado actual del proyecto
+- documentacion disponible
 
-Then it chooses one of two routes:
+Luego elige una de dos rutas:
 
 - `direct bootstrap`
-  for technical users and already-defined repositories
+  para usuarios tecnicos y repos ya definidos
 - `agent handoff`
-  for early ideas, non-technical users, or weak documentation
+  para ideas tempranas, usuarios no tecnicos o documentacion debil
 
-If TrackOps routes bootstrap to the agent:
+Si TrackOps deriva al agente:
 
-- read `ops/bootstrap/agent-handoff.md`
-- or print it with `trackops opera handoff --print`
-- the agent must produce:
+- lee `ops/bootstrap/agent-handoff.md`
+- o imprimelo con `trackops opera handoff --print`
+- exige como salida:
   - `ops/bootstrap/intake.json`
   - `ops/bootstrap/spec-dossier.md`
-  - `ops/bootstrap/open-questions.md` when important gaps remain
-- then resume with:
+  - `ops/bootstrap/open-questions.md` cuando queden huecos importantes
+- reanuda con:
 
 ```bash
 trackops opera bootstrap --resume
 ```
 
-Read references only when needed:
+## Que referencia leer y cuando
 
-- `references/activation.md`
-- `references/workflow.md`
-- `references/troubleshooting.md`
+- lee `references/activation.md` solo para instalacion, verificacion del runtime, locale bootstrap y activacion de un repo
+- lee `references/workflow.md` solo cuando TrackOps ya esta activo y haga falta operar el dia a dia del repositorio
+- lee `references/troubleshooting.md` solo cuando fallen la instalacion explicita, la deteccion de `trackops`, el resume o el contrato de entorno

package/skills/trackops/agents/openai.yaml

@@ -1,3 +1,7 @@
 interface:
   display_name: "TrackOps"
-  short_description: "Global TrackOps skill for local project orchestration, bilingual onboarding, agent coordination, and operational automation"
+  short_description: "Guide explicit TrackOps install and activate OPERA"
+  default_prompt: "Use $trackops to install the global skill, require explicit npm installation of the TrackOps runtime, and then activate TrackOps and OPERA in this repository."
+
+policy:
+  allow_implicit_invocation: true

package/skills/trackops/locales/en/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: "trackops"
+description: "Global TrackOps skill for preparing the agent, requiring explicit npm runtime installation, and guiding local TrackOps and OPERA activation inside each repository."
+---
+
+# TrackOps
+
+Use this localized file when the conversation and project should run in English.
+
+## Global layer
+
+Install the marketplace skill with:
+
+```bash
+npx skills add Baxahaun/trackops
+```
+
+Then confirm that the `trackops` runtime exists. If it is missing, ask the user to install it explicitly:
+
+```bash
+npm install -g trackops
+trackops --version
+```
+
+Rules:
+
+- the skill must not install packages or execute remote code by itself
+- the runtime is installed through a visible and auditable npm step
+- the skill may verify `trackops --version`, but it must not chain silent installs
+- the skill must not create repository files by itself
+
+## Local project layer
+
+Inside the repository:
+
+```bash
+trackops init
+trackops opera install
+```
+
+Core rules:
+
+- treat the global skill as an instruction layer
+- treat runtime installation as explicit and separate
+- use `ops/contract/operating-contract.json` as the machine contract when it exists
+- use `ops/project_control.json` as the operational source of truth
+- use `ops/policy/autonomy.json` before approval-sensitive actions
+- use `/.env` and `/.env.example` as the environment contract
+- keep generated operational docs under `ops/`
+- use `trackops locale get|set` and `trackops doctor locale` when language matters
+
+## OPERA onboarding
+
+OPERA no longer assumes every user is technical.
+
+TrackOps classifies:
+
+- user technical level
+- current project state
+- available documentation
+
+Then it chooses one of two routes:
+
+- `direct bootstrap`
+  for technical users and already-defined repositories
+- `agent handoff`
+  for early ideas, non-technical users, or weak documentation
+
+If TrackOps routes bootstrap to the agent:
+
+- read `ops/bootstrap/agent-handoff.md`
+- or print it with `trackops opera handoff --print`
+- require these outputs:
+  - `ops/bootstrap/intake.json`
+  - `ops/bootstrap/spec-dossier.md`
+  - `ops/bootstrap/open-questions.md` when important gaps remain
+- resume with:
+
+```bash
+trackops opera bootstrap --resume
+```
+
+## Which reference to read and when
+
+- read `locales/en/references/activation.md` only for installation, runtime verification, locale bootstrap, and repository activation
+- read `locales/en/references/workflow.md` only when TrackOps is already active and you need day-to-day repository operations
+- read `locales/en/references/troubleshooting.md` only when explicit installation, `trackops` detection, resume, or environment contract handling fails

package/skills/trackops/locales/en/references/activation.md

@@ -0,0 +1,75 @@
+# Activation
+
+## Global install
+
+```bash
+npx skills add Baxahaun/trackops
+npm install -g trackops
+trackops --version
+```
+
+The global skill installs instructions for the agent.
+
+The `trackops` runtime is installed separately through npm so the step stays visible, auditable, and easy to verify.
+
+Before continuing:
+
+- confirm that `trackops --version` returns a valid version
+- if it does not, fix PATH or reinstall `trackops`
+- the skill must not try to install the runtime by itself
+
+## Local activation
+
+Inside a repository:
+
+```bash
+trackops init
+trackops opera install
+```
+
+By default, `trackops init` creates a split workspace with:
+
+- `app/`
+- `ops/`
+- `/.env`
+- `/.env.example`
+- `.trackops-workspace.json`
+
+## OPERA routing
+
+OPERA always starts by classifying:
+
+- technical level
+- project state
+- documentation state
+
+If the project is still early or the user is non-technical, TrackOps writes:
+
+- `ops/bootstrap/agent-handoff.md`
+- `ops/bootstrap/agent-handoff.json`
+
+The agent must produce:
+
+- `ops/bootstrap/intake.json`
+- `ops/bootstrap/spec-dossier.md`
+- `ops/bootstrap/open-questions.md` when needed
+
+When the quality gate passes, OPERA compiles:
+
+- `ops/contract/operating-contract.json`
+- `ops/genesis.md`
+- `ops/policy/autonomy.json`
+
+Resume with:
+
+```bash
+trackops opera bootstrap --resume
+```
+
+Locale controls:
+
+```bash
+trackops locale get
+trackops locale set en
+trackops doctor locale
+```

package/skills/trackops/locales/en/references/troubleshooting.md

@@ -0,0 +1,55 @@
+# Troubleshooting
+
+## Missing prerequisites
+
+- Install Node 18+ if Node is missing or too old.
+- Install a Node distribution that includes npm if npm is missing.
+
+## The skill is installed, but `trackops` does not start
+
+- Confirm that the global skill exists:
+  `npx skills add Baxahaun/trackops`
+- Install or reinstall the runtime explicitly:
+  `npm install -g trackops`
+- Verify:
+  `trackops --version`
+- If the binary still does not respond:
+  - check Node.js (`>= 18`)
+  - check that `npm` exists and works
+  - check PATH and reopen the terminal
+
+## Explicit runtime installation fails
+
+- Re-run `npm install -g trackops`.
+- If `npm` errors, fix that first; the skill cannot continue without the CLI.
+- If the issue is global permissions, use the recommended method for your system or a user-controlled npm prefix.
+
+## OPERA routed bootstrap to the agent
+
+This is expected when:
+
+- the user is non-technical
+- the project is still in idea stage
+- documentation is weak
+
+Use:
+
+```bash
+trackops opera handoff --print
+trackops opera bootstrap --resume
+```
+
+## Resume does not complete
+
+TrackOps will not invent missing context.
+
+Check that both files exist and contain usable data:
+
+- `ops/bootstrap/intake.json`
+- `ops/bootstrap/spec-dossier.md`
+
+## Environment looks inconsistent
+
+- Run `trackops env status`.
+- Run `trackops env sync`.
+- If bridge mode is `copy`, do not edit `app/.env` directly.

package/skills/trackops/locales/en/references/workflow.md

@@ -0,0 +1,32 @@
+# Workflow
+
+Precondition:
+
+- the global skill is already installed
+- `trackops --version` responds correctly
+- the repository was already activated with `trackops init`
+
+Use TrackOps when the repository is already managed and you need day-to-day operations.
+
+1. Run `trackops status`.
+2. Run `trackops next`.
+3. Move task state with `trackops task ...`.
+4. Run `trackops sync` after meaningful changes.
+5. Run `trackops env status` when credentials matter.
+
+Operational rules:
+
+- in split workspaces, use `ops/project_control.json` as the source of truth
+- generated operational docs live in `ops/`
+- product code lives in `app/`
+- real secrets live in `/.env`
+- public environment contract lives in `/.env.example`
+- `app/.env` is only a compatibility bridge
+
+If OPERA is installed:
+
+- `ops/contract/operating-contract.json` holds the machine contract
+- `ops/genesis.md` holds the compiled human view
+- `ops/policy/autonomy.json` holds the executable autonomy policy
+- `ops/bootstrap/` holds onboarding artifacts
+- `ops/.agent/hub/` and `ops/.agents/skills/` hold managed agent artifacts

package/skills/trackops/references/activation.md

@@ -1,31 +1,33 @@
-# Activation
+# Activacion
 
-## Global install
-
-Install the marketplace skill:
+## Instalacion global
 
 ```bash
 npx skills add Baxahaun/trackops
+npm install -g trackops
+trackops --version
 ```
 
-On first use, ensure the runtime with:
+La skill global instala instrucciones para el agente.
 
-```bash
-node scripts/bootstrap-trackops.js
-```
+El runtime `trackops` se instala aparte con npm para que el paso sea visible, auditable y facil de verificar.
+
+Antes de seguir:
 
-The global skill must not create repository files by itself.
+- confirma que `trackops --version` devuelve una version valida
+- si no aparece, resuelve PATH o reinstala `trackops`
+- la skill no debe intentar instalar el runtime por su cuenta
 
-## Local activation
+## Activacion local
 
-Inside a repository:
+Dentro del repo:
 
 ```bash
 trackops init
 trackops opera install
 ```
 
-By default, `trackops init` creates a split workspace with:
+Por defecto, `trackops init` crea un workspace split con:
 
 - `app/`
 - `ops/`
@@ -33,41 +35,41 @@ By default, `trackops init` creates a split workspace with:
 - `/.env.example`
 - `.trackops-workspace.json`
 
-## OPERA routing
+## Routing de OPERA
 
-OPERA always starts by classifying:
+OPERA siempre empieza clasificando:
 
-- technical level
-- project state
-- documentation state
+- nivel tecnico
+- estado del proyecto
+- estado de documentacion
 
-If the project is still early or the user is non-technical, TrackOps writes:
+Si el proyecto esta en fase temprana o el usuario es no tecnico, TrackOps escribe:
 
 - `ops/bootstrap/agent-handoff.md`
 - `ops/bootstrap/agent-handoff.json`
 
-The agent then produces:
+El agente debe producir:
 
 - `ops/bootstrap/intake.json`
 - `ops/bootstrap/spec-dossier.md`
-- `ops/bootstrap/open-questions.md` when needed
+- `ops/bootstrap/open-questions.md` cuando haga falta
 
-When the quality gate passes, OPERA compiles:
+Cuando pasa el quality gate, OPERA compila:
 
 - `ops/contract/operating-contract.json`
 - `ops/genesis.md`
 - `ops/policy/autonomy.json`
 
-Resume with:
+Reanuda con:
 
 ```bash
 trackops opera bootstrap --resume
 ```
 
-Locale controls:
+Controles de idioma:
 
 ```bash
 trackops locale get
-trackops locale set en
+trackops locale set es
 trackops doctor locale
 ```

package/skills/trackops/references/troubleshooting.md

@@ -1,49 +1,55 @@
 # Troubleshooting
 
-## Missing prerequisites
+## Faltan prerequisitos
 
-- Install Node 18+ if Node is missing or too old.
-- Install a Node distribution that includes npm if npm is missing.
+- Instala Node 18+ si Node no existe o es demasiado antiguo.
+- Instala una distribucion de Node que incluya npm si npm no existe.
 
-## Global install command failed
+## La skill se instalo, pero `trackops` no arranca
 
-- Install from committed GitHub state:
+- Confirma que la skill global existe:
   `npx skills add Baxahaun/trackops`
-- Then ensure the local runtime with:
-  `node scripts/bootstrap-trackops.js`
-- If the install succeeded but the CLI still looks unavailable, confirm that `~/.trackops/runtime.json` exists.
+- Instala o reinstala el runtime de forma explicita:
+  `npm install -g trackops`
+- Verifica:
+  `trackops --version`
+- Si el binario sigue sin responder:
+  - revisa Node.js (`>= 18`)
+  - revisa que `npm` exista y funcione
+  - revisa PATH y reabre la terminal
 
-## Runtime bootstrap failed
+## La instalacion explicita del runtime falla
 
-- Re-run `node scripts/bootstrap-trackops.js`.
-- If npm global permissions fail, configure a user-writable npm prefix instead of using `sudo`.
+- Reejecuta `npm install -g trackops`.
+- Si `npm` devuelve error, resuelvelo primero; la skill no puede continuar sin el CLI.
+- Si el problema es de permisos globales, usa el metodo recomendado para tu sistema o un prefijo npm controlado por el usuario.
 
-## OPERA routed bootstrap to the agent
+## OPERA derivo el bootstrap al agente
 
-This is expected when:
+Esto es esperado cuando:
 
-- the user is non-technical
-- the project is still in idea stage
-- documentation is weak
+- el usuario no es tecnico
+- el proyecto esta en fase idea
+- la documentacion es debil
 
-Use:
+Usa:
 
 ```bash
 trackops opera handoff --print
 trackops opera bootstrap --resume
 ```
 
-## Resume does not complete
+## `trackops opera bootstrap --resume` no avanza
 
-TrackOps will not invent missing context.
+TrackOps no inventa contexto faltante.
 
-Check that both files exist and contain usable data:
+Comprueba que existan ambos archivos y contengan datos utiles:
 
 - `ops/bootstrap/intake.json`
 - `ops/bootstrap/spec-dossier.md`
 
-## Environment looks inconsistent
+## El entorno parece inconsistente
 
-- Run `trackops env status`.
-- Run `trackops env sync`.
-- If bridge mode is `copy`, do not edit `app/.env` directly.
+- Ejecuta `trackops env status`.
+- Ejecuta `trackops env sync`.
+- Si el modo bridge es `copy`, no edites `app/.env` directamente.

package/skills/trackops/references/workflow.md

@@ -1,26 +1,32 @@
-# Workflow
+# Flujo diario
 
-Once TrackOps is active in a repository:
+Precondicion:
 
-1. Run `trackops status`.
-2. Run `trackops next`.
-3. Move task state with `trackops task ...`.
-4. Run `trackops sync` after meaningful changes.
-5. Run `trackops env status` when credentials matter.
+- la skill global ya esta instalada
+- `trackops --version` responde correctamente
+- el repo ya fue activado con `trackops init`
 
-Operational rules:
+Usa TrackOps cuando el repositorio ya esta gestionado y necesites operar el dia a dia.
 
-- In split workspaces, use `ops/project_control.json` as the source of truth.
-- Generated operational docs live in `ops/`.
-- Product code lives in `app/`.
-- Real secrets live in `/.env`.
-- Public environment contract lives in `/.env.example`.
-- `app/.env` is only a compatibility bridge.
+1. Ejecuta `trackops status`.
+2. Ejecuta `trackops next`.
+3. Mueve el estado de tareas con `trackops task ...`.
+4. Ejecuta `trackops sync` despues de cambios relevantes.
+5. Ejecuta `trackops env status` cuando las credenciales importen.
 
-If OPERA is installed:
+Reglas operativas:
 
-- `ops/contract/operating-contract.json` holds the machine contract.
-- `ops/genesis.md` holds the compiled human view.
-- `ops/policy/autonomy.json` holds the executable autonomy policy.
-- `ops/bootstrap/` holds onboarding artifacts.
-- `ops/.agent/hub/` and `ops/.agents/skills/` hold managed agent artifacts.
+- en workspaces split, usa `ops/project_control.json` como fuente de verdad
+- la documentacion operativa generada vive en `ops/`
+- el codigo de producto vive en `app/`
+- los secretos reales viven en `/.env`
+- el contrato publico de entorno vive en `/.env.example`
+- `app/.env` solo es un puente de compatibilidad
+
+Si OPERA esta instalado:
+
+- `ops/contract/operating-contract.json` guarda el contrato de maquina
+- `ops/genesis.md` guarda la vista humana compilada
+- `ops/policy/autonomy.json` guarda la politica ejecutable
+- `ops/bootstrap/` guarda artefactos de onboarding
+- `ops/.agent/hub/` y `ops/.agents/skills/` guardan artefactos gestionados de agente

package/skills/trackops/skill.json

@@ -1,11 +1,11 @@
 {
   "name": "trackops",
-  "shortDescription": "Global TrackOps skill for local project orchestration, agent coordination, bilingual onboarding, and operational automation.",
-  "description": "Installs TrackOps as a global skill, ensures the runtime on first use, lets users choose Spanish or English, activates local project orchestration, and routes OPERA onboarding into either direct bootstrap or agent-led discovery.",
-  "skillVersion": "2.0.0",
-  "trackopsVersion": "2.0.0",
+  "shortDescription": "Global TrackOps skill for secure agent guidance, explicit runtime install, bilingual onboarding, and local project orchestration.",
+  "description": "Installs TrackOps as a global skill, requires explicit runtime installation with npm, lets users choose Spanish or English, activates local project orchestration, and routes OPERA onboarding into either direct bootstrap or agent-led discovery.",
+  "skillVersion": "2.0.2",
+  "trackopsVersion": "2.0.2",
   "npmPackage": "trackops",
-  "bootstrapPolicy": "first_use",
+  "bootstrapPolicy": "explicit_install",
   "supportedAgentsV1": [
     "antigravity",
     "claude-code",

package/templates/opera/architecture/dependency-graph.md

@@ -2,7 +2,7 @@
 
 ```mermaid
 flowchart TD
-    A[Global runtime bootstrap] --> B[trackops init]
+    A[Explicit global runtime install] --> B[trackops init]
     B --> C[trackops opera install]
     C --> D{Routing}
     D -->|direct_cli| E[Direct intake]