trackops 2.0.0 → 2.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/skills/trackops/SKILL.md +41 -44
- package/skills/trackops/agents/openai.yaml +5 -1
- package/skills/trackops/locales/en/SKILL.md +86 -0
- package/skills/trackops/locales/en/references/activation.md +73 -0
- package/skills/trackops/locales/en/references/troubleshooting.md +49 -0
- package/skills/trackops/locales/en/references/workflow.md +26 -0
- package/skills/trackops/references/activation.md +19 -19
- package/skills/trackops/references/troubleshooting.md +23 -23
- package/skills/trackops/references/workflow.md +19 -19
- package/skills/trackops/skill.json +2 -2
package/package.json
CHANGED
package/skills/trackops/SKILL.md
CHANGED
|
@@ -1,89 +1,86 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: "trackops"
|
|
3
|
-
description: "
|
|
4
|
-
metadata:
|
|
5
|
-
version: "2.0.0"
|
|
6
|
-
type: "global"
|
|
7
|
-
triggers:
|
|
8
|
-
- "install trackops"
|
|
9
|
-
- "skills.sh"
|
|
10
|
-
- "trackops init"
|
|
11
|
-
- "trackops opera install"
|
|
12
|
-
- "opera handoff"
|
|
3
|
+
description: "Skill global de TrackOps para instalar y activar la orquestacion local de proyectos con OPERA, entorno y handoff a agentes. Usala cuando el usuario quiera instalar TrackOps desde skills.sh, bootstrapear el runtime con `node scripts/bootstrap-trackops.js`, ejecutar `trackops init`, ejecutar `trackops opera install`, revisar `trackops opera handoff`, o trabajar sobre el flujo operativo de un repositorio."
|
|
13
4
|
---
|
|
14
5
|
|
|
15
6
|
# TrackOps
|
|
16
7
|
|
|
17
|
-
|
|
8
|
+
Si la conversacion y el proyecto deben trabajar en ingles, lee `locales/en/SKILL.md` antes de seguir.
|
|
18
9
|
|
|
19
|
-
##
|
|
10
|
+
## Capa global
|
|
20
11
|
|
|
21
|
-
|
|
12
|
+
Instala la skill del marketplace con:
|
|
22
13
|
|
|
23
14
|
```bash
|
|
24
15
|
npx skills add Baxahaun/trackops
|
|
25
16
|
```
|
|
26
17
|
|
|
27
|
-
|
|
18
|
+
Antes de depender del CLI, ejecuta el script empaquetado de la skill:
|
|
28
19
|
|
|
29
20
|
```bash
|
|
30
21
|
node scripts/bootstrap-trackops.js
|
|
31
22
|
```
|
|
32
23
|
|
|
33
|
-
|
|
24
|
+
Ese bootstrap:
|
|
34
25
|
|
|
35
|
-
|
|
26
|
+
- asegura el runtime npm de `trackops`
|
|
27
|
+
- valida que el binario global sea ejecutable
|
|
28
|
+
- registra estado en `~/.trackops/runtime.json`
|
|
36
29
|
|
|
37
|
-
|
|
30
|
+
No debe crear archivos dentro de un repositorio por si solo.
|
|
31
|
+
|
|
32
|
+
## Capa local del proyecto
|
|
33
|
+
|
|
34
|
+
Dentro del repositorio:
|
|
38
35
|
|
|
39
36
|
```bash
|
|
40
37
|
trackops init
|
|
41
38
|
trackops opera install
|
|
42
39
|
```
|
|
43
40
|
|
|
44
|
-
|
|
41
|
+
Reglas base:
|
|
45
42
|
|
|
46
|
-
-
|
|
47
|
-
-
|
|
48
|
-
-
|
|
49
|
-
-
|
|
50
|
-
-
|
|
51
|
-
-
|
|
52
|
-
-
|
|
43
|
+
- trata la instalacion global como no invasiva
|
|
44
|
+
- usa `ops/contract/operating-contract.json` como contrato de maquina cuando exista
|
|
45
|
+
- usa `ops/project_control.json` como fuente de verdad operativa
|
|
46
|
+
- usa `ops/policy/autonomy.json` antes de acciones sensibles
|
|
47
|
+
- usa `/.env` y `/.env.example` como contrato de entorno
|
|
48
|
+
- deja la documentacion operativa generada dentro de `ops/`
|
|
49
|
+
- usa `trackops locale get|set` y `trackops doctor locale` cuando el idioma importe
|
|
53
50
|
|
|
54
|
-
## OPERA
|
|
51
|
+
## Onboarding de OPERA
|
|
55
52
|
|
|
56
|
-
OPERA no
|
|
53
|
+
OPERA ya no asume que todo usuario es tecnico.
|
|
57
54
|
|
|
58
|
-
|
|
55
|
+
TrackOps clasifica:
|
|
59
56
|
|
|
60
|
-
-
|
|
61
|
-
-
|
|
62
|
-
-
|
|
57
|
+
- nivel tecnico del usuario
|
|
58
|
+
- estado actual del proyecto
|
|
59
|
+
- documentacion disponible
|
|
63
60
|
|
|
64
|
-
|
|
61
|
+
Luego elige una de dos rutas:
|
|
65
62
|
|
|
66
63
|
- `direct bootstrap`
|
|
67
|
-
|
|
64
|
+
para usuarios tecnicos y repos ya definidos
|
|
68
65
|
- `agent handoff`
|
|
69
|
-
|
|
66
|
+
para ideas tempranas, usuarios no tecnicos o documentacion debil
|
|
70
67
|
|
|
71
|
-
|
|
68
|
+
Si TrackOps deriva al agente:
|
|
72
69
|
|
|
73
|
-
-
|
|
74
|
-
-
|
|
75
|
-
-
|
|
70
|
+
- lee `ops/bootstrap/agent-handoff.md`
|
|
71
|
+
- o imprimelo con `trackops opera handoff --print`
|
|
72
|
+
- exige como salida:
|
|
76
73
|
- `ops/bootstrap/intake.json`
|
|
77
74
|
- `ops/bootstrap/spec-dossier.md`
|
|
78
|
-
- `ops/bootstrap/open-questions.md`
|
|
79
|
-
-
|
|
75
|
+
- `ops/bootstrap/open-questions.md` cuando queden huecos importantes
|
|
76
|
+
- reanuda con:
|
|
80
77
|
|
|
81
78
|
```bash
|
|
82
79
|
trackops opera bootstrap --resume
|
|
83
80
|
```
|
|
84
81
|
|
|
85
|
-
|
|
82
|
+
## Que referencia leer y cuando
|
|
86
83
|
|
|
87
|
-
- `references/activation.md`
|
|
88
|
-
- `references/workflow.md`
|
|
89
|
-
- `references/troubleshooting.md`
|
|
84
|
+
- lee `references/activation.md` solo para instalacion, primer uso, locale bootstrap y activacion de un repo
|
|
85
|
+
- lee `references/workflow.md` solo cuando TrackOps ya esta activo y haga falta operar el dia a dia del repositorio
|
|
86
|
+
- lee `references/troubleshooting.md` solo cuando fallen la instalacion, el bootstrap, el resume o el contrato de entorno
|
|
@@ -1,3 +1,7 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "TrackOps"
|
|
3
|
-
short_description: "
|
|
3
|
+
short_description: "Bootstrap TrackOps and activate OPERA"
|
|
4
|
+
default_prompt: "Use $trackops to bootstrap the TrackOps runtime and activate OPERA in this repository."
|
|
5
|
+
|
|
6
|
+
policy:
|
|
7
|
+
allow_implicit_invocation: true
|
|
@@ -0,0 +1,86 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: "trackops"
|
|
3
|
+
description: "Global TrackOps skill for installing and activating local project orchestration with OPERA, environment management, and agent handoff. Use it when the user wants to install TrackOps from skills.sh, bootstrap the runtime with `node scripts/bootstrap-trackops.js`, run `trackops init`, run `trackops opera install`, inspect `trackops opera handoff`, or work through the operational flow of a repository."
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# TrackOps
|
|
7
|
+
|
|
8
|
+
Use this localized file when the conversation and project should run in English.
|
|
9
|
+
|
|
10
|
+
## Global layer
|
|
11
|
+
|
|
12
|
+
Install the marketplace skill with:
|
|
13
|
+
|
|
14
|
+
```bash
|
|
15
|
+
npx skills add Baxahaun/trackops
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
Before relying on the CLI, run the bundled skill script:
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
node scripts/bootstrap-trackops.js
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
That bootstrap:
|
|
25
|
+
|
|
26
|
+
- ensures the npm `trackops` runtime
|
|
27
|
+
- verifies that the global binary can be executed
|
|
28
|
+
- records state in `~/.trackops/runtime.json`
|
|
29
|
+
|
|
30
|
+
It must not create repository files on its own.
|
|
31
|
+
|
|
32
|
+
## Local project layer
|
|
33
|
+
|
|
34
|
+
Inside the repository:
|
|
35
|
+
|
|
36
|
+
```bash
|
|
37
|
+
trackops init
|
|
38
|
+
trackops opera install
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
Core rules:
|
|
42
|
+
|
|
43
|
+
- treat the global install as non-invasive
|
|
44
|
+
- use `ops/contract/operating-contract.json` as the machine contract when it exists
|
|
45
|
+
- use `ops/project_control.json` as the operational source of truth
|
|
46
|
+
- use `ops/policy/autonomy.json` before approval-sensitive actions
|
|
47
|
+
- use `/.env` and `/.env.example` as the environment contract
|
|
48
|
+
- keep generated operational docs under `ops/`
|
|
49
|
+
- use `trackops locale get|set` and `trackops doctor locale` when language matters
|
|
50
|
+
|
|
51
|
+
## OPERA onboarding
|
|
52
|
+
|
|
53
|
+
OPERA no longer assumes every user is technical.
|
|
54
|
+
|
|
55
|
+
TrackOps classifies:
|
|
56
|
+
|
|
57
|
+
- user technical level
|
|
58
|
+
- current project state
|
|
59
|
+
- available documentation
|
|
60
|
+
|
|
61
|
+
Then it chooses one of two routes:
|
|
62
|
+
|
|
63
|
+
- `direct bootstrap`
|
|
64
|
+
for technical users and already-defined repositories
|
|
65
|
+
- `agent handoff`
|
|
66
|
+
for early ideas, non-technical users, or weak documentation
|
|
67
|
+
|
|
68
|
+
If TrackOps routes bootstrap to the agent:
|
|
69
|
+
|
|
70
|
+
- read `ops/bootstrap/agent-handoff.md`
|
|
71
|
+
- or print it with `trackops opera handoff --print`
|
|
72
|
+
- require these outputs:
|
|
73
|
+
- `ops/bootstrap/intake.json`
|
|
74
|
+
- `ops/bootstrap/spec-dossier.md`
|
|
75
|
+
- `ops/bootstrap/open-questions.md` when important gaps remain
|
|
76
|
+
- resume with:
|
|
77
|
+
|
|
78
|
+
```bash
|
|
79
|
+
trackops opera bootstrap --resume
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
## Which reference to read and when
|
|
83
|
+
|
|
84
|
+
- read `locales/en/references/activation.md` only for installation, first use, locale bootstrap, and repository activation
|
|
85
|
+
- read `locales/en/references/workflow.md` only when TrackOps is already active and you need day-to-day repository operations
|
|
86
|
+
- read `locales/en/references/troubleshooting.md` only when installation, bootstrap, resume, or environment contract handling fails
|
|
@@ -0,0 +1,73 @@
|
|
|
1
|
+
# Activation
|
|
2
|
+
|
|
3
|
+
## Global install
|
|
4
|
+
|
|
5
|
+
Install the marketplace skill:
|
|
6
|
+
|
|
7
|
+
```bash
|
|
8
|
+
npx skills add Baxahaun/trackops
|
|
9
|
+
```
|
|
10
|
+
|
|
11
|
+
On first use, ensure the runtime with the bundled skill script:
|
|
12
|
+
|
|
13
|
+
```bash
|
|
14
|
+
node scripts/bootstrap-trackops.js
|
|
15
|
+
```
|
|
16
|
+
|
|
17
|
+
The global skill must not create repository files on its own.
|
|
18
|
+
|
|
19
|
+
## Local activation
|
|
20
|
+
|
|
21
|
+
Inside a repository:
|
|
22
|
+
|
|
23
|
+
```bash
|
|
24
|
+
trackops init
|
|
25
|
+
trackops opera install
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
By default, `trackops init` creates a split workspace with:
|
|
29
|
+
|
|
30
|
+
- `app/`
|
|
31
|
+
- `ops/`
|
|
32
|
+
- `/.env`
|
|
33
|
+
- `/.env.example`
|
|
34
|
+
- `.trackops-workspace.json`
|
|
35
|
+
|
|
36
|
+
## OPERA routing
|
|
37
|
+
|
|
38
|
+
OPERA always starts by classifying:
|
|
39
|
+
|
|
40
|
+
- technical level
|
|
41
|
+
- project state
|
|
42
|
+
- documentation state
|
|
43
|
+
|
|
44
|
+
If the project is still early or the user is non-technical, TrackOps writes:
|
|
45
|
+
|
|
46
|
+
- `ops/bootstrap/agent-handoff.md`
|
|
47
|
+
- `ops/bootstrap/agent-handoff.json`
|
|
48
|
+
|
|
49
|
+
The agent must produce:
|
|
50
|
+
|
|
51
|
+
- `ops/bootstrap/intake.json`
|
|
52
|
+
- `ops/bootstrap/spec-dossier.md`
|
|
53
|
+
- `ops/bootstrap/open-questions.md` when needed
|
|
54
|
+
|
|
55
|
+
When the quality gate passes, OPERA compiles:
|
|
56
|
+
|
|
57
|
+
- `ops/contract/operating-contract.json`
|
|
58
|
+
- `ops/genesis.md`
|
|
59
|
+
- `ops/policy/autonomy.json`
|
|
60
|
+
|
|
61
|
+
Resume with:
|
|
62
|
+
|
|
63
|
+
```bash
|
|
64
|
+
trackops opera bootstrap --resume
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
Locale controls:
|
|
68
|
+
|
|
69
|
+
```bash
|
|
70
|
+
trackops locale get
|
|
71
|
+
trackops locale set en
|
|
72
|
+
trackops doctor locale
|
|
73
|
+
```
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# Troubleshooting
|
|
2
|
+
|
|
3
|
+
## Missing prerequisites
|
|
4
|
+
|
|
5
|
+
- Install Node 18+ if Node is missing or too old.
|
|
6
|
+
- Install a Node distribution that includes npm if npm is missing.
|
|
7
|
+
|
|
8
|
+
## Global install command failed
|
|
9
|
+
|
|
10
|
+
- Install from committed GitHub state:
|
|
11
|
+
`npx skills add Baxahaun/trackops`
|
|
12
|
+
- Then ensure the local runtime with:
|
|
13
|
+
`node scripts/bootstrap-trackops.js`
|
|
14
|
+
- If the install succeeded but the CLI still looks unavailable, confirm that `~/.trackops/runtime.json` exists.
|
|
15
|
+
|
|
16
|
+
## Runtime bootstrap failed
|
|
17
|
+
|
|
18
|
+
- Re-run `node scripts/bootstrap-trackops.js`.
|
|
19
|
+
- If npm global permissions fail, configure a user-writable npm prefix instead of using `sudo`.
|
|
20
|
+
|
|
21
|
+
## OPERA routed bootstrap to the agent
|
|
22
|
+
|
|
23
|
+
This is expected when:
|
|
24
|
+
|
|
25
|
+
- the user is non-technical
|
|
26
|
+
- the project is still in idea stage
|
|
27
|
+
- documentation is weak
|
|
28
|
+
|
|
29
|
+
Use:
|
|
30
|
+
|
|
31
|
+
```bash
|
|
32
|
+
trackops opera handoff --print
|
|
33
|
+
trackops opera bootstrap --resume
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
## Resume does not complete
|
|
37
|
+
|
|
38
|
+
TrackOps will not invent missing context.
|
|
39
|
+
|
|
40
|
+
Check that both files exist and contain usable data:
|
|
41
|
+
|
|
42
|
+
- `ops/bootstrap/intake.json`
|
|
43
|
+
- `ops/bootstrap/spec-dossier.md`
|
|
44
|
+
|
|
45
|
+
## Environment looks inconsistent
|
|
46
|
+
|
|
47
|
+
- Run `trackops env status`.
|
|
48
|
+
- Run `trackops env sync`.
|
|
49
|
+
- If bridge mode is `copy`, do not edit `app/.env` directly.
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
# Workflow
|
|
2
|
+
|
|
3
|
+
Once TrackOps is active in a repository:
|
|
4
|
+
|
|
5
|
+
1. Run `trackops status`.
|
|
6
|
+
2. Run `trackops next`.
|
|
7
|
+
3. Move task state with `trackops task ...`.
|
|
8
|
+
4. Run `trackops sync` after meaningful changes.
|
|
9
|
+
5. Run `trackops env status` when credentials matter.
|
|
10
|
+
|
|
11
|
+
Operational rules:
|
|
12
|
+
|
|
13
|
+
- In split workspaces, use `ops/project_control.json` as the source of truth.
|
|
14
|
+
- Generated operational docs live in `ops/`.
|
|
15
|
+
- Product code lives in `app/`.
|
|
16
|
+
- Real secrets live in `/.env`.
|
|
17
|
+
- Public environment contract lives in `/.env.example`.
|
|
18
|
+
- `app/.env` is only a compatibility bridge.
|
|
19
|
+
|
|
20
|
+
If OPERA is installed:
|
|
21
|
+
|
|
22
|
+
- `ops/contract/operating-contract.json` holds the machine contract.
|
|
23
|
+
- `ops/genesis.md` holds the compiled human view.
|
|
24
|
+
- `ops/policy/autonomy.json` holds the executable autonomy policy.
|
|
25
|
+
- `ops/bootstrap/` holds onboarding artifacts.
|
|
26
|
+
- `ops/.agent/hub/` and `ops/.agents/skills/` hold managed agent artifacts.
|
|
@@ -1,31 +1,31 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Activacion
|
|
2
2
|
|
|
3
|
-
##
|
|
3
|
+
## Instalacion global
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Instala la skill del marketplace:
|
|
6
6
|
|
|
7
7
|
```bash
|
|
8
8
|
npx skills add Baxahaun/trackops
|
|
9
9
|
```
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
En primer uso, asegura el runtime con el script empaquetado de la skill:
|
|
12
12
|
|
|
13
13
|
```bash
|
|
14
14
|
node scripts/bootstrap-trackops.js
|
|
15
15
|
```
|
|
16
16
|
|
|
17
|
-
|
|
17
|
+
La skill global no debe crear archivos dentro de repositorios por si sola.
|
|
18
18
|
|
|
19
|
-
##
|
|
19
|
+
## Activacion local
|
|
20
20
|
|
|
21
|
-
|
|
21
|
+
Dentro de un repositorio:
|
|
22
22
|
|
|
23
23
|
```bash
|
|
24
24
|
trackops init
|
|
25
25
|
trackops opera install
|
|
26
26
|
```
|
|
27
27
|
|
|
28
|
-
|
|
28
|
+
Por defecto, `trackops init` crea un workspace split con:
|
|
29
29
|
|
|
30
30
|
- `app/`
|
|
31
31
|
- `ops/`
|
|
@@ -33,38 +33,38 @@ By default, `trackops init` creates a split workspace with:
|
|
|
33
33
|
- `/.env.example`
|
|
34
34
|
- `.trackops-workspace.json`
|
|
35
35
|
|
|
36
|
-
## OPERA
|
|
36
|
+
## Routing de OPERA
|
|
37
37
|
|
|
38
|
-
OPERA
|
|
38
|
+
OPERA siempre empieza clasificando:
|
|
39
39
|
|
|
40
|
-
-
|
|
41
|
-
-
|
|
42
|
-
-
|
|
40
|
+
- nivel tecnico
|
|
41
|
+
- estado del proyecto
|
|
42
|
+
- estado de la documentacion
|
|
43
43
|
|
|
44
|
-
|
|
44
|
+
Si el proyecto aun esta verde o el usuario no es tecnico, TrackOps escribe:
|
|
45
45
|
|
|
46
46
|
- `ops/bootstrap/agent-handoff.md`
|
|
47
47
|
- `ops/bootstrap/agent-handoff.json`
|
|
48
48
|
|
|
49
|
-
|
|
49
|
+
El agente debe producir:
|
|
50
50
|
|
|
51
51
|
- `ops/bootstrap/intake.json`
|
|
52
52
|
- `ops/bootstrap/spec-dossier.md`
|
|
53
|
-
- `ops/bootstrap/open-questions.md`
|
|
53
|
+
- `ops/bootstrap/open-questions.md` cuando haga falta
|
|
54
54
|
|
|
55
|
-
|
|
55
|
+
Cuando el quality gate pasa, OPERA compila:
|
|
56
56
|
|
|
57
57
|
- `ops/contract/operating-contract.json`
|
|
58
58
|
- `ops/genesis.md`
|
|
59
59
|
- `ops/policy/autonomy.json`
|
|
60
60
|
|
|
61
|
-
|
|
61
|
+
Reanuda con:
|
|
62
62
|
|
|
63
63
|
```bash
|
|
64
64
|
trackops opera bootstrap --resume
|
|
65
65
|
```
|
|
66
66
|
|
|
67
|
-
|
|
67
|
+
Controles de idioma:
|
|
68
68
|
|
|
69
69
|
```bash
|
|
70
70
|
trackops locale get
|
|
@@ -1,49 +1,49 @@
|
|
|
1
1
|
# Troubleshooting
|
|
2
2
|
|
|
3
|
-
##
|
|
3
|
+
## Faltan prerequisitos
|
|
4
4
|
|
|
5
|
-
-
|
|
6
|
-
-
|
|
5
|
+
- Instala Node 18+ si Node falta o es demasiado antiguo.
|
|
6
|
+
- Instala una distribucion de Node que incluya npm si falta npm.
|
|
7
7
|
|
|
8
|
-
##
|
|
8
|
+
## Fallo al instalar la skill global
|
|
9
9
|
|
|
10
|
-
-
|
|
10
|
+
- Instala desde el estado committeado de GitHub:
|
|
11
11
|
`npx skills add Baxahaun/trackops`
|
|
12
|
-
-
|
|
12
|
+
- Luego asegura el runtime local con:
|
|
13
13
|
`node scripts/bootstrap-trackops.js`
|
|
14
|
-
-
|
|
14
|
+
- Si la instalacion salio bien pero el CLI sigue sin aparecer, confirma que `~/.trackops/runtime.json` exista.
|
|
15
15
|
|
|
16
|
-
##
|
|
16
|
+
## Fallo en el bootstrap del runtime
|
|
17
17
|
|
|
18
|
-
-
|
|
19
|
-
-
|
|
18
|
+
- Reejecuta `node scripts/bootstrap-trackops.js`.
|
|
19
|
+
- Si fallan los permisos globales de npm, configura un prefix de usuario en lugar de usar `sudo`.
|
|
20
20
|
|
|
21
|
-
## OPERA
|
|
21
|
+
## OPERA ha derivado el bootstrap al agente
|
|
22
22
|
|
|
23
|
-
|
|
23
|
+
Es el comportamiento esperado cuando:
|
|
24
24
|
|
|
25
|
-
-
|
|
26
|
-
-
|
|
27
|
-
-
|
|
25
|
+
- el usuario no es tecnico
|
|
26
|
+
- el proyecto sigue en fase idea
|
|
27
|
+
- la documentacion es debil
|
|
28
28
|
|
|
29
|
-
|
|
29
|
+
Usa:
|
|
30
30
|
|
|
31
31
|
```bash
|
|
32
32
|
trackops opera handoff --print
|
|
33
33
|
trackops opera bootstrap --resume
|
|
34
34
|
```
|
|
35
35
|
|
|
36
|
-
##
|
|
36
|
+
## El resume no completa
|
|
37
37
|
|
|
38
|
-
TrackOps
|
|
38
|
+
TrackOps no inventa contexto faltante.
|
|
39
39
|
|
|
40
|
-
|
|
40
|
+
Comprueba que ambos archivos existan y contengan datos utilizables:
|
|
41
41
|
|
|
42
42
|
- `ops/bootstrap/intake.json`
|
|
43
43
|
- `ops/bootstrap/spec-dossier.md`
|
|
44
44
|
|
|
45
|
-
##
|
|
45
|
+
## El entorno parece inconsistente
|
|
46
46
|
|
|
47
|
-
-
|
|
48
|
-
-
|
|
49
|
-
-
|
|
47
|
+
- Ejecuta `trackops env status`.
|
|
48
|
+
- Ejecuta `trackops env sync`.
|
|
49
|
+
- Si el bridge mode es `copy`, no edites `app/.env` directamente.
|
|
@@ -1,26 +1,26 @@
|
|
|
1
1
|
# Workflow
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Una vez que TrackOps esta activo en un repositorio:
|
|
4
4
|
|
|
5
|
-
1.
|
|
6
|
-
2.
|
|
7
|
-
3.
|
|
8
|
-
4.
|
|
9
|
-
5.
|
|
5
|
+
1. Ejecuta `trackops status`.
|
|
6
|
+
2. Ejecuta `trackops next`.
|
|
7
|
+
3. Mueve el estado de tareas con `trackops task ...`.
|
|
8
|
+
4. Ejecuta `trackops sync` tras cambios relevantes.
|
|
9
|
+
5. Ejecuta `trackops env status` cuando importen las credenciales.
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
Reglas operativas:
|
|
12
12
|
|
|
13
|
-
-
|
|
14
|
-
-
|
|
15
|
-
-
|
|
16
|
-
-
|
|
17
|
-
-
|
|
18
|
-
- `app/.env`
|
|
13
|
+
- En workspaces split, usa `ops/project_control.json` como fuente de verdad.
|
|
14
|
+
- La documentacion operativa generada vive en `ops/`.
|
|
15
|
+
- El codigo de producto vive en `app/`.
|
|
16
|
+
- Los secretos reales viven en `/.env`.
|
|
17
|
+
- El contrato publico de entorno vive en `/.env.example`.
|
|
18
|
+
- `app/.env` es solo un puente de compatibilidad.
|
|
19
19
|
|
|
20
|
-
|
|
20
|
+
Si OPERA esta instalado:
|
|
21
21
|
|
|
22
|
-
- `ops/contract/operating-contract.json`
|
|
23
|
-
- `ops/genesis.md`
|
|
24
|
-
- `ops/policy/autonomy.json`
|
|
25
|
-
- `ops/bootstrap/`
|
|
26
|
-
- `ops/.agent/hub/`
|
|
22
|
+
- `ops/contract/operating-contract.json` contiene el contrato de maquina.
|
|
23
|
+
- `ops/genesis.md` contiene la vista humana compilada.
|
|
24
|
+
- `ops/policy/autonomy.json` contiene la politica ejecutable.
|
|
25
|
+
- `ops/bootstrap/` contiene los artefactos de onboarding.
|
|
26
|
+
- `ops/.agent/hub/` y `ops/.agents/skills/` contienen artefactos gestionados de agentes.
|
|
@@ -2,8 +2,8 @@
|
|
|
2
2
|
"name": "trackops",
|
|
3
3
|
"shortDescription": "Global TrackOps skill for local project orchestration, agent coordination, bilingual onboarding, and operational automation.",
|
|
4
4
|
"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.",
|
|
5
|
-
"skillVersion": "2.0.
|
|
6
|
-
"trackopsVersion": "2.0.
|
|
5
|
+
"skillVersion": "2.0.1",
|
|
6
|
+
"trackopsVersion": "2.0.1",
|
|
7
7
|
"npmPackage": "trackops",
|
|
8
8
|
"bootstrapPolicy": "first_use",
|
|
9
9
|
"supportedAgentsV1": [
|