sdtk-ops-kit 0.2.1 → 0.2.2
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/README.md +182 -127
- package/assets/manifest/toolkit-bundle.manifest.json +66 -66
- package/assets/manifest/toolkit-bundle.sha256.txt +32 -32
- package/assets/toolkit/toolkit/AGENTS.md +29 -1
- package/assets/toolkit/toolkit/SDTKOPS_TOOLKIT.md +49 -13
- package/assets/toolkit/toolkit/install.ps1 +1 -8
- package/assets/toolkit/toolkit/scripts/install-codex-skills.ps1 +30 -7
- package/assets/toolkit/toolkit/scripts/uninstall-codex-skills.ps1 +31 -2
- package/assets/toolkit/toolkit/sdtk-spec.config.profiles.example.json +12 -12
- package/assets/toolkit/toolkit/skills/ops-backup/SKILL.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-backup/references/backup-script-patterns.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-ci-cd/SKILL.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-ci-cd/references/pipeline-examples.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-container/SKILL.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-container/references/k8s-manifest-patterns.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-cost/SKILL.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-debug/SKILL.md +0 -1
- package/assets/toolkit/toolkit/skills/ops-debug/references/root-cause-tracing.md +0 -1
- package/assets/toolkit/toolkit/skills/ops-deploy/SKILL.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-discover/SKILL.md +21 -0
- package/assets/toolkit/toolkit/skills/ops-incident/SKILL.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-incident/references/communication-templates.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-incident/references/postmortem-template.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-incident/references/runbook-template.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-infra-plan/SKILL.md +1 -3
- package/assets/toolkit/toolkit/skills/ops-infra-plan/references/iac-patterns.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-monitor/SKILL.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-monitor/references/alert-rules.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-monitor/references/slo-templates.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-parallel/SKILL.md +22 -5
- package/assets/toolkit/toolkit/skills/ops-plan/SKILL.md +33 -1
- package/assets/toolkit/toolkit/skills/ops-security-infra/SKILL.md +1 -3
- package/assets/toolkit/toolkit/skills/ops-security-infra/references/cicd-security-pipeline.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-security-infra/references/security-headers.md +0 -2
- package/assets/toolkit/toolkit/skills/ops-verify/SKILL.md +16 -1
- package/package.json +1 -1
- package/src/commands/help.js +59 -38
- package/src/commands/init.js +10 -1
- package/src/commands/runtime.js +29 -7
- package/src/lib/scope.js +19 -2
|
@@ -1,36 +1,36 @@
|
|
|
1
|
-
|
|
2
|
-
|
|
1
|
+
a0fa279e32a8b311606867ed162cc33b371bffc5b1ce2922995903a2dbff3561 toolkit/AGENTS.md
|
|
2
|
+
ac041e80d0771b13fc1dc94c6a572debaddba223ff4d029695a6953f35ebaa92 toolkit/install.ps1
|
|
3
3
|
5eae77f4d14b81d56c3c109f563fefafd1967d85093ff1b192293fe438aeabe5 toolkit/scripts/install-claude-skills.ps1
|
|
4
|
-
|
|
4
|
+
68eb662bc9b8906882d32f6cd1247238f6ae663137a489f18054a75724cd1e81 toolkit/scripts/install-codex-skills.ps1
|
|
5
5
|
2c629d8316b205c6a7cd0d95959b80801b281ef62e205c10a92e3a2568eb8b41 toolkit/scripts/uninstall-claude-skills.ps1
|
|
6
|
-
|
|
7
|
-
|
|
6
|
+
fdb9631a80ecfb0d986a52a2833e88bf15c5303ab654d35bad6d64cca43046e8 toolkit/scripts/uninstall-codex-skills.ps1
|
|
7
|
+
a7cfca05138e8b9831ea03bd0622a4fd64d77924b69d5c0faff5c279a20091d1 toolkit/SDTKOPS_TOOLKIT.md
|
|
8
8
|
8247ddf24502ce285bee213eefc801ce6b0b83afe00efd828468ac9130f53b09 toolkit/sdtk-spec.config.json
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
9
|
+
de0310b0c69f77d1c1601b94b0ea72b2c83c92cb8ee94d2f4a1759ceb58f2fd4 toolkit/sdtk-spec.config.profiles.example.json
|
|
10
|
+
1cd81e12cebdb2be528803e2d8afe43959aab1493e55499af529b99ec566a56c toolkit/skills/ops-backup/references/backup-script-patterns.md
|
|
11
|
+
76e8385190d967bf98b3cafbbf8925d9b9c656ee7a7ed66ff51285b6459ebff1 toolkit/skills/ops-backup/SKILL.md
|
|
12
|
+
d27e47b0c832656c2835e3d3e32dae7c86419014199439b10fc6823956324716 toolkit/skills/ops-ci-cd/references/pipeline-examples.md
|
|
13
|
+
c9bf8e6f602d6201ccd54a78a9a7f850028924b460d60495d144bd5ec473c5e6 toolkit/skills/ops-ci-cd/SKILL.md
|
|
14
14
|
a0bb24484cba68a7201e6b7f614c8b5ada8b2dff540a4e4390661a0ced112e8d toolkit/skills/ops-compliance/SKILL.md
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
15
|
+
070ebcad0d0cb71cd3815de6e4c78d22517a28f825d65ea3677215e57112d1df toolkit/skills/ops-container/references/k8s-manifest-patterns.md
|
|
16
|
+
7eb1113162af029886974d2dba6553fec6ba9b002adc31a18c427a5e471d48a3 toolkit/skills/ops-container/SKILL.md
|
|
17
|
+
3000b78ad911d667b056efdc01c639d8e069c1df1b157c6a6721ba2c61cce678 toolkit/skills/ops-cost/SKILL.md
|
|
18
|
+
d70b59d276edf5c6c8aebb5fc669b8f6d04673fc8e8561cbaf4d7e5fb9f4e2f2 toolkit/skills/ops-debug/references/root-cause-tracing.md
|
|
19
|
+
d5f58322afebcf5c3a110b02de0d2eec4494f9ed9d358b113b6717275c3524af toolkit/skills/ops-debug/SKILL.md
|
|
20
|
+
c2cacc94ffba4d7ef84e635c2078e08abb8d52f79afbbb1534661c0e0cf9bda6 toolkit/skills/ops-deploy/SKILL.md
|
|
21
|
+
6f38c9b2ab972f272fb86e17926585a9a254a1c48c8454459a61315d4bd81d81 toolkit/skills/ops-discover/SKILL.md
|
|
22
|
+
f6102d127e47861068b285ebbbb2045e4c3dc8cd9af73b3c975f285f2141639e toolkit/skills/ops-incident/references/communication-templates.md
|
|
23
|
+
fda6d9cadc5a3757e5559798a67716a6356809735b076d47d6bd99a993b71b99 toolkit/skills/ops-incident/references/postmortem-template.md
|
|
24
|
+
358644dcd477fe32d3368ced5c9da30663ae3d54fdd5e825ae3e56327f7f6f2d toolkit/skills/ops-incident/references/runbook-template.md
|
|
25
|
+
df03ad86862020941e69b90ea1f2ccf8cd69762e53f0a539936c16fb433e61c8 toolkit/skills/ops-incident/SKILL.md
|
|
26
|
+
14f02a1921cb58e2c54c355c0b24ffdf5a9bdb91a7be6921f22da5974787efee toolkit/skills/ops-infra-plan/references/iac-patterns.md
|
|
27
|
+
35eec623e41603dae0a1a328c1e6d822d2e1dc79a471f06bab3c1f3e2d552e53 toolkit/skills/ops-infra-plan/SKILL.md
|
|
28
|
+
28be1bd1babdaa3de9fc58f859060697c31b9249cc684c9c4272a9c3bc159db9 toolkit/skills/ops-monitor/references/alert-rules.md
|
|
29
|
+
af28797b442fb94fa96dc0182881847e50b5fe9e68ecf7a71471502030f4bd27 toolkit/skills/ops-monitor/references/slo-templates.md
|
|
30
|
+
2d09968790ed63dd8e0969f59023c0ced71dd182d56475689a2d3bfc3f889002 toolkit/skills/ops-monitor/SKILL.md
|
|
31
|
+
8c83a7f267b7222cf9765a4328dd6945e30f3629dfca21cd85f7439f501b8ee0 toolkit/skills/ops-parallel/SKILL.md
|
|
32
|
+
db75109542354b70a9502231f6c66803642c013958eedb93a26770f28b9e7fad toolkit/skills/ops-plan/SKILL.md
|
|
33
|
+
1a2d6c5ab225af2abc2591cc897808ebcce16bf0478ed55daea61000aa7652ee toolkit/skills/ops-security-infra/references/cicd-security-pipeline.md
|
|
34
|
+
796ebd48e399aedc59b0a1e9bbbe2363813d3b74be38721bec330cec683ecc69 toolkit/skills/ops-security-infra/references/security-headers.md
|
|
35
|
+
81d19ee0002c70788295a6a7e93ae8b0ff0e97af5e71c0a3591548e5bbd5bab6 toolkit/skills/ops-security-infra/SKILL.md
|
|
36
|
+
497bcb22ccb191dbb77d7db46cd96801b56cf9b1ec630c834d3a947b90a6169e toolkit/skills/ops-verify/SKILL.md
|
|
@@ -14,11 +14,39 @@ Document role:
|
|
|
14
14
|
- If the correct entry point is unclear, start with `ops-discover`.
|
|
15
15
|
- Use `ops-verify` before marking any operational task complete.
|
|
16
16
|
- Use `ops-debug` for evidence-first diagnosis before proposing speculative fixes.
|
|
17
|
+
- Use `ops-parallel` only for truly independent slices. If collab or subagent dispatch is unavailable in the active runtime, keep the same slice boundaries but execute them sequentially in one controller session.
|
|
17
18
|
- Keep guidance cloud-agnostic unless the task explicitly requires a platform-specific example.
|
|
18
19
|
- Do not drift into application specification or coding workflows. Those belong to SDTK-SPEC or SDTK-CODE.
|
|
19
20
|
- `ops-discover` is a skill, not a CLI command.
|
|
20
21
|
- `generate` remains unsupported and deferred in the current SDTK-OPS CLI surface.
|
|
21
22
|
|
|
23
|
+
## DEV-Run Intake
|
|
24
|
+
|
|
25
|
+
When `DEV-Run` begins from `SDTK-CODE`, the only canonical bridge artifact is:
|
|
26
|
+
- `docs/dev/OPS_HANDOFF_[FEATURE_KEY].json`
|
|
27
|
+
|
|
28
|
+
Treat that file as the frozen suite contract input.
|
|
29
|
+
`SDTK-OPS` consumes it, but does not redefine the schema, rename fields, or move the canonical path.
|
|
30
|
+
|
|
31
|
+
Ready-path intake:
|
|
32
|
+
- inspect `handoff_status` first
|
|
33
|
+
- if status is `READY_FOR_SDTK_OPS`, default to `suggested_next_ops_path.start_with`
|
|
34
|
+
- treat `suggested_next_ops_path.suggested_chain` as the default route unless fresh evidence requires a bounded reroute
|
|
35
|
+
- close with `suggested_next_ops_path.close_with`, which should normally be `ops-verify`
|
|
36
|
+
|
|
37
|
+
Blocked-path intake:
|
|
38
|
+
- if status is `BLOCKED_FOR_SDTK_OPS`, the handoff is still inspectable
|
|
39
|
+
- inspect `open_blockers`, `code_evidence_refs`, and prerequisite fields before choosing a next step
|
|
40
|
+
- do not treat a blocked handoff as normal ready-path execution
|
|
41
|
+
- use `ops-discover` only to select bounded triage or clarification, not to silently reinterpret blocked scope as deployment-ready
|
|
42
|
+
|
|
43
|
+
Minimum OPS evidence expectations:
|
|
44
|
+
- record the consumed handoff path and `handoff_status`
|
|
45
|
+
- record whether the chosen first skill followed or overrode `suggested_next_ops_path`, and why
|
|
46
|
+
- record which prerequisites, assumptions, dependencies, observability, and rollback items were checked
|
|
47
|
+
- record journey-specific operational evidence for the scoped OPS work
|
|
48
|
+
- record final `ops-verify` closeout evidence
|
|
49
|
+
|
|
22
50
|
## Primary Routing Journeys
|
|
23
51
|
|
|
24
52
|
| Journey | Start With | Suggested Chain | Close With |
|
|
@@ -58,7 +86,7 @@ Document role:
|
|
|
58
86
|
| Runtime | Project Scope | User Scope | Default Scope | Notes |
|
|
59
87
|
|---------|:-------------:|:----------:|---------------|-------|
|
|
60
88
|
| Claude | true | true | project | project-local toolkit supported |
|
|
61
|
-
| Codex | false | true | user | Gate C0:
|
|
89
|
+
| Codex | false | true | user | Gate C0: current shipped product blocks project-local skill runtime; future support remains unverified until code and bounded validation change. |
|
|
62
90
|
|
|
63
91
|
## Verification Policy
|
|
64
92
|
|
|
@@ -27,6 +27,11 @@ The truthful current CLI surface is:
|
|
|
27
27
|
- `sdtk-ops runtime status`
|
|
28
28
|
- `sdtk-ops runtime uninstall`
|
|
29
29
|
|
|
30
|
+
The current public package is:
|
|
31
|
+
- `sdtk-ops-kit`
|
|
32
|
+
- CLI command: `sdtk-ops`
|
|
33
|
+
- Latest published version lookup: `npm view sdtk-ops-kit version`
|
|
34
|
+
|
|
30
35
|
The truthful current operational surface after `init` is skill-driven:
|
|
31
36
|
- the 15 `ops-*` skills remain the real operating surface
|
|
32
37
|
- `ops-discover` remains a skill, not a CLI command
|
|
@@ -57,9 +62,40 @@ The truthful current operational surface after `init` is skill-driven:
|
|
|
57
62
|
- upstream requirements or architecture generation
|
|
58
63
|
- coding workflow execution
|
|
59
64
|
- provider-specific platform packs in the current wave
|
|
60
|
-
-
|
|
65
|
+
- broader launch marketing claims beyond the current public package
|
|
66
|
+
|
|
67
|
+
## 3. DEV-Run Intake Contract
|
|
68
|
+
|
|
69
|
+
`DEV-Run` is executed via `SDTK-OPS`.
|
|
70
|
+
|
|
71
|
+
When `DEV-Run` begins from coded scope, the only canonical `CODE -> OPS` bridge artifact is:
|
|
72
|
+
- `docs/dev/OPS_HANDOFF_[FEATURE_KEY].json`
|
|
73
|
+
|
|
74
|
+
`SDTK-OPS` reads that frozen contract as input.
|
|
75
|
+
It does not redefine the schema, rename fields, move the file, or silently normalize producer output into a different contract.
|
|
76
|
+
|
|
77
|
+
Ready-path intake rules:
|
|
78
|
+
- inspect `handoff_status` first
|
|
79
|
+
- if `handoff_status` is `READY_FOR_SDTK_OPS`, start with `suggested_next_ops_path.start_with` unless fresh evidence requires a bounded reroute
|
|
80
|
+
- treat `suggested_next_ops_path.suggested_chain` as the default first routing sequence
|
|
81
|
+
- close with `suggested_next_ops_path.close_with`, which should normally be `ops-verify`
|
|
82
|
+
|
|
83
|
+
Blocked-path intake rules:
|
|
84
|
+
- if `handoff_status` is `BLOCKED_FOR_SDTK_OPS`, the handoff is still inspectable
|
|
85
|
+
- inspect `open_blockers`, `code_evidence_refs`, and the prerequisite fields before choosing any action
|
|
86
|
+
- do not treat blocked handoff state as normal ready-path execution
|
|
87
|
+
- use `ops-discover` to select bounded triage or clarification only when blocker text supports that path
|
|
88
|
+
|
|
89
|
+
Bounded OPS evidence expectations in this wave:
|
|
90
|
+
- record the consumed handoff path and `handoff_status`
|
|
91
|
+
- record the selected first OPS step and whether it followed or overrode `suggested_next_ops_path`
|
|
92
|
+
- record checked prerequisites, assumptions, dependencies, observability requirements, and rollback or recovery expectations
|
|
93
|
+
- record journey-specific operational evidence for the scoped OPS work
|
|
94
|
+
- record final `ops-verify` closeout evidence
|
|
95
|
+
|
|
96
|
+
This wave does not define a final OPS evidence schema and does not implement QA bridge logic.
|
|
61
97
|
|
|
62
|
-
##
|
|
98
|
+
## 4. Entry And Routing Model
|
|
63
99
|
|
|
64
100
|
After `sdtk-ops init`, choose a journey directly when the goal is clear.
|
|
65
101
|
|
|
@@ -83,9 +119,9 @@ Other valid but non-primary routed skills in this wave:
|
|
|
83
119
|
- `ops-cost`
|
|
84
120
|
- `ops-parallel`
|
|
85
121
|
|
|
86
|
-
##
|
|
122
|
+
## 5. Skill Catalog
|
|
87
123
|
|
|
88
|
-
###
|
|
124
|
+
### 5.1 Core Process
|
|
89
125
|
|
|
90
126
|
| Skill | Purpose |
|
|
91
127
|
|-------|---------|
|
|
@@ -94,7 +130,7 @@ Other valid but non-primary routed skills in this wave:
|
|
|
94
130
|
| `ops-plan` | write reviewable operational plans with rollback and verification steps |
|
|
95
131
|
| `ops-parallel` | split truly independent operations tasks into parallel workstreams |
|
|
96
132
|
|
|
97
|
-
###
|
|
133
|
+
### 5.2 Deployment
|
|
98
134
|
|
|
99
135
|
| Skill | Purpose |
|
|
100
136
|
|-------|---------|
|
|
@@ -103,7 +139,7 @@ Other valid but non-primary routed skills in this wave:
|
|
|
103
139
|
| `ops-container` | define secure image build and container orchestration patterns |
|
|
104
140
|
| `ops-ci-cd` | build and manage pipelines, promotion flow, artifact handling, and secret controls |
|
|
105
141
|
|
|
106
|
-
###
|
|
142
|
+
### 5.3 Operations
|
|
107
143
|
|
|
108
144
|
| Skill | Purpose |
|
|
109
145
|
|-------|---------|
|
|
@@ -112,20 +148,20 @@ Other valid but non-primary routed skills in this wave:
|
|
|
112
148
|
| `ops-backup` | design backup, restore, and disaster recovery procedures |
|
|
113
149
|
| `ops-cost` | review spend, identify waste, and plan safe right-sizing |
|
|
114
150
|
|
|
115
|
-
###
|
|
151
|
+
### 5.4 Security And Compliance
|
|
116
152
|
|
|
117
153
|
| Skill | Purpose |
|
|
118
154
|
|-------|---------|
|
|
119
155
|
| `ops-security-infra` | harden infrastructure, secrets, network policy, and security scanning |
|
|
120
156
|
| `ops-compliance` | automate audit readiness, evidence collection, retention, and policy enforcement |
|
|
121
157
|
|
|
122
|
-
###
|
|
158
|
+
### 5.5 Discovery
|
|
123
159
|
|
|
124
160
|
| Skill | Purpose |
|
|
125
161
|
|-------|---------|
|
|
126
162
|
| `ops-discover` | choose the correct SDTK-OPS entry point and sequencing |
|
|
127
163
|
|
|
128
|
-
##
|
|
164
|
+
## 6. Runtime Truth
|
|
129
165
|
|
|
130
166
|
### Claude
|
|
131
167
|
- supports project and user scope
|
|
@@ -138,7 +174,7 @@ Other valid but non-primary routed skills in this wave:
|
|
|
138
174
|
- uses collision-avoiding `sdtk-ops-*` skill directory names
|
|
139
175
|
- project scope remains blocked by Gate C0
|
|
140
176
|
|
|
141
|
-
##
|
|
177
|
+
## 7. Documentation Map
|
|
142
178
|
|
|
143
179
|
Use these documents by role:
|
|
144
180
|
|
|
@@ -152,15 +188,15 @@ Use these documents by role:
|
|
|
152
188
|
- `products/sdtk-ops/distribution/sdtk-ops-kit/README.md`
|
|
153
189
|
- Runtime routing inventory:
|
|
154
190
|
- `products/sdtk-ops/toolkit/AGENTS.md`
|
|
155
|
-
-
|
|
191
|
+
- Release docs:
|
|
156
192
|
- `products/sdtk-ops/governance/release-packaging.md`
|
|
157
193
|
- `products/sdtk-ops/governance/release-evidence.md`
|
|
158
194
|
|
|
159
|
-
##
|
|
195
|
+
## 8. Scope
|
|
160
196
|
|
|
161
197
|
`SDTK-OPS` v1 contains 15 core skills and stays cloud-agnostic.
|
|
162
198
|
|
|
163
199
|
Not part of the current supported wave:
|
|
164
200
|
- provider-specific packs such as AWS, GCP, or Azure variants
|
|
165
201
|
- a workflow-first CLI command suite such as `sdtk-ops deploy`
|
|
166
|
-
-
|
|
202
|
+
- cloud, Kubernetes, or production-topology guarantees beyond the current validated local Docker proof
|
|
@@ -65,11 +65,6 @@ if (-not $Scope) {
|
|
|
65
65
|
$Scope = if ($Runtime -eq 'claude') { 'project' } else { 'user' }
|
|
66
66
|
}
|
|
67
67
|
|
|
68
|
-
if ($Runtime -eq 'codex' -and $Scope -eq 'project') {
|
|
69
|
-
Write-Error "Codex does not support project-local skills. Use -Scope user instead."
|
|
70
|
-
exit 1
|
|
71
|
-
}
|
|
72
|
-
|
|
73
68
|
if ($SkipSkills) {
|
|
74
69
|
if (-not $Quiet) {
|
|
75
70
|
Write-Warning "-SkipSkills is deprecated. Use -SkipRuntimeAssets instead."
|
|
@@ -120,11 +115,9 @@ if (-not $SkipRuntimeAssets) {
|
|
|
120
115
|
|
|
121
116
|
$params = @{
|
|
122
117
|
Scope = $Scope
|
|
118
|
+
ProjectPath = $projectRoot
|
|
123
119
|
Quiet = [bool]$Quiet
|
|
124
120
|
}
|
|
125
|
-
if ($Runtime -eq 'claude') {
|
|
126
|
-
$params.ProjectPath = $projectRoot
|
|
127
|
-
}
|
|
128
121
|
if ($Force) {
|
|
129
122
|
$params.Force = $true
|
|
130
123
|
}
|
|
@@ -1,18 +1,37 @@
|
|
|
1
1
|
param(
|
|
2
2
|
[ValidateSet('project', 'user')]
|
|
3
3
|
[string]$Scope = 'user',
|
|
4
|
+
[string]$ProjectPath,
|
|
4
5
|
[switch]$Force,
|
|
5
6
|
[switch]$Quiet
|
|
6
7
|
)
|
|
7
8
|
|
|
8
|
-
if ($Scope -eq 'project') {
|
|
9
|
-
Write-Error "Codex does not support project-local skills. Use -Scope user instead."
|
|
10
|
-
exit 1
|
|
11
|
-
}
|
|
12
|
-
|
|
13
9
|
$ErrorActionPreference = 'Stop'
|
|
14
10
|
Set-StrictMode -Version Latest
|
|
15
11
|
|
|
12
|
+
function Resolve-CodexHome {
|
|
13
|
+
param(
|
|
14
|
+
[Parameter(Mandatory = $true)][string]$TargetScope,
|
|
15
|
+
[string]$TargetProjectPath
|
|
16
|
+
)
|
|
17
|
+
|
|
18
|
+
if ($TargetScope -eq 'project') {
|
|
19
|
+
if (-not $TargetProjectPath -or $TargetProjectPath.Trim().Length -eq 0) {
|
|
20
|
+
throw "Project-local Codex install requires -ProjectPath."
|
|
21
|
+
}
|
|
22
|
+
if (-not (Test-Path -LiteralPath $TargetProjectPath)) {
|
|
23
|
+
New-Item -ItemType Directory -Force -Path $TargetProjectPath | Out-Null
|
|
24
|
+
}
|
|
25
|
+
$projectRoot = (Resolve-Path -LiteralPath $TargetProjectPath).Path
|
|
26
|
+
return (Join-Path $projectRoot '.codex')
|
|
27
|
+
}
|
|
28
|
+
|
|
29
|
+
if ($env:CODEX_HOME) {
|
|
30
|
+
return $env:CODEX_HOME
|
|
31
|
+
}
|
|
32
|
+
return (Join-Path $HOME '.codex')
|
|
33
|
+
}
|
|
34
|
+
|
|
16
35
|
function Write-Utf8NoBomFile {
|
|
17
36
|
param(
|
|
18
37
|
[Parameter(Mandatory = $true)][string]$Path,
|
|
@@ -66,7 +85,7 @@ if ($managedSkills.Count -ne 15) {
|
|
|
66
85
|
throw "Expected 15 managed SDTK-OPS skills but found $($managedSkills.Count)."
|
|
67
86
|
}
|
|
68
87
|
|
|
69
|
-
$codexHome =
|
|
88
|
+
$codexHome = Resolve-CodexHome -TargetScope $Scope -TargetProjectPath $ProjectPath
|
|
70
89
|
$skillsDest = Join-Path $codexHome 'skills'
|
|
71
90
|
New-Item -ItemType Directory -Force -Path $skillsDest | Out-Null
|
|
72
91
|
|
|
@@ -120,8 +139,12 @@ if ($installedNow.Count -ne 15) {
|
|
|
120
139
|
if (-not $Quiet) {
|
|
121
140
|
Write-Host ""
|
|
122
141
|
Write-Host "Install summary:"
|
|
123
|
-
Write-Host "- Scope:
|
|
142
|
+
Write-Host "- Scope: $Scope"
|
|
124
143
|
Write-Host "- Destination: $skillsDest"
|
|
125
144
|
Write-Host "- Copied: $copied"
|
|
126
145
|
Write-Host "- Skipped: $skipped"
|
|
146
|
+
if ($Scope -eq 'project') {
|
|
147
|
+
Write-Host "- Project-local Codex support requires launching Codex with CODEX_HOME=<project>/.codex."
|
|
148
|
+
Write-Host "- Native .codex/skills auto-discovery is not claimed."
|
|
149
|
+
}
|
|
127
150
|
}
|
|
@@ -1,4 +1,7 @@
|
|
|
1
1
|
param(
|
|
2
|
+
[ValidateSet('project', 'user')]
|
|
3
|
+
[string]$Scope = 'user',
|
|
4
|
+
[string]$ProjectPath,
|
|
2
5
|
[switch]$All,
|
|
3
6
|
[switch]$Quiet
|
|
4
7
|
)
|
|
@@ -6,6 +9,29 @@ param(
|
|
|
6
9
|
$ErrorActionPreference = 'Stop'
|
|
7
10
|
Set-StrictMode -Version Latest
|
|
8
11
|
|
|
12
|
+
function Resolve-CodexHome {
|
|
13
|
+
param(
|
|
14
|
+
[Parameter(Mandatory = $true)][string]$TargetScope,
|
|
15
|
+
[string]$TargetProjectPath
|
|
16
|
+
)
|
|
17
|
+
|
|
18
|
+
if ($TargetScope -eq 'project') {
|
|
19
|
+
if (-not $TargetProjectPath -or $TargetProjectPath.Trim().Length -eq 0) {
|
|
20
|
+
throw "Project-local Codex uninstall requires -ProjectPath."
|
|
21
|
+
}
|
|
22
|
+
if (-not (Test-Path -LiteralPath $TargetProjectPath)) {
|
|
23
|
+
New-Item -ItemType Directory -Force -Path $TargetProjectPath | Out-Null
|
|
24
|
+
}
|
|
25
|
+
$projectRoot = (Resolve-Path -LiteralPath $TargetProjectPath).Path
|
|
26
|
+
return (Join-Path $projectRoot '.codex')
|
|
27
|
+
}
|
|
28
|
+
|
|
29
|
+
if ($env:CODEX_HOME) {
|
|
30
|
+
return $env:CODEX_HOME
|
|
31
|
+
}
|
|
32
|
+
return (Join-Path $HOME '.codex')
|
|
33
|
+
}
|
|
34
|
+
|
|
9
35
|
$toolkitRoot = (Resolve-Path (Join-Path $PSScriptRoot '..')).Path
|
|
10
36
|
$skillsSource = Join-Path $toolkitRoot 'skills'
|
|
11
37
|
if (-not (Test-Path -LiteralPath $skillsSource)) {
|
|
@@ -21,7 +47,7 @@ if ($managedSkillNames.Count -ne 15) {
|
|
|
21
47
|
throw "Expected 15 managed SDTK-OPS skills but found $($managedSkillNames.Count)."
|
|
22
48
|
}
|
|
23
49
|
|
|
24
|
-
$codexHome =
|
|
50
|
+
$codexHome = Resolve-CodexHome -TargetScope $Scope -TargetProjectPath $ProjectPath
|
|
25
51
|
$skillsDest = Join-Path $codexHome 'skills'
|
|
26
52
|
if (-not (Test-Path -LiteralPath $skillsDest)) {
|
|
27
53
|
if (-not $Quiet) {
|
|
@@ -46,8 +72,11 @@ foreach ($name in $managedSkillNames) {
|
|
|
46
72
|
if (-not $Quiet) {
|
|
47
73
|
Write-Host ""
|
|
48
74
|
Write-Host "Uninstall summary:"
|
|
49
|
-
Write-Host "- Scope:
|
|
75
|
+
Write-Host "- Scope: $Scope"
|
|
50
76
|
Write-Host "- Destination: $skillsDest"
|
|
51
77
|
Write-Host "- Removed: $($removed.Count)"
|
|
52
78
|
Write-Host "- Missing/Skipped: $($missing.Count)"
|
|
79
|
+
if ($Scope -eq 'project') {
|
|
80
|
+
Write-Host "- Project-local Codex uninstall touched only SDTK-OPS-managed assets under <project>/.codex/skills."
|
|
81
|
+
}
|
|
53
82
|
}
|
|
@@ -1,12 +1,12 @@
|
|
|
1
|
-
{
|
|
2
|
-
"$comment": "Example profiles config for SDTK-OPS. Copy to sdtk-spec.config.profiles.json and customize for your
|
|
3
|
-
"profiles": {
|
|
4
|
-
"default": {
|
|
5
|
-
"stack": {
|
|
6
|
-
"backend": "UPDATE_ME",
|
|
7
|
-
"frontend": "UPDATE_ME",
|
|
8
|
-
"database": "UPDATE_ME"
|
|
9
|
-
}
|
|
10
|
-
}
|
|
11
|
-
}
|
|
12
|
-
}
|
|
1
|
+
{
|
|
2
|
+
"$comment": "Example profiles config for SDTK-OPS. Copy to sdtk-spec.config.profiles.json and customize for your runtime targets.",
|
|
3
|
+
"profiles": {
|
|
4
|
+
"default": {
|
|
5
|
+
"stack": {
|
|
6
|
+
"backend": "UPDATE_ME",
|
|
7
|
+
"frontend": "UPDATE_ME",
|
|
8
|
+
"database": "UPDATE_ME"
|
|
9
|
+
}
|
|
10
|
+
}
|
|
11
|
+
}
|
|
12
|
+
}
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025). Adapted for SDTK-OPS. -->
|
|
2
1
|
---
|
|
3
2
|
name: ops-backup
|
|
4
3
|
description: Backup and disaster recovery. Use when designing backup strategies, disaster recovery plans, or restore procedures -- covers RTO/RPO definition, backup verification, and cross-region replication.
|
|
@@ -90,4 +89,3 @@ After backup design is approved:
|
|
|
90
89
|
- implement storage and retention changes through `ops-infra-plan`
|
|
91
90
|
- validate restore evidence with `ops-verify`
|
|
92
91
|
- use `ops-monitor` so backup failures page the right team
|
|
93
|
-
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025). Adapted for SDTK-OPS. -->
|
|
2
1
|
|
|
3
2
|
# Backup Script Patterns
|
|
4
3
|
|
|
@@ -105,4 +104,3 @@ cleanup_old_backups() {
|
|
|
105
104
|
- replace `cloud-storage-copy` with the provider-specific upload command used by your platform
|
|
106
105
|
- verify every backup after encryption and before declaring success
|
|
107
106
|
- keep restore testing separate from production systems
|
|
108
|
-
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025). Adapted for SDTK-OPS. -->
|
|
2
1
|
---
|
|
3
2
|
name: ops-ci-cd
|
|
4
3
|
description: CI/CD pipeline design and management. Use when setting up or modifying build, test, and deployment pipelines -- covers pipeline stages, branch strategies, artifact management, and secret handling.
|
|
@@ -85,4 +84,3 @@ Optimize only after correctness:
|
|
|
85
84
|
| Manual deploy steps outside pipeline | Audit trail and repeatability disappear |
|
|
86
85
|
| Skip security scanning to save time | Vulnerabilities ship by default |
|
|
87
86
|
| No build cache or job parallelism | Pipeline slows down until teams bypass it |
|
|
88
|
-
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025). Adapted for SDTK-OPS. -->
|
|
2
1
|
|
|
3
2
|
# Pipeline Examples
|
|
4
3
|
|
|
@@ -110,4 +109,3 @@ deploy_prod:
|
|
|
110
109
|
- promote the same artifact between environments
|
|
111
110
|
- prefer platform identity federation over static cloud keys
|
|
112
111
|
- keep deployment commands explicit enough to review and replay
|
|
113
|
-
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025). Adapted for SDTK-OPS. -->
|
|
2
1
|
---
|
|
3
2
|
name: ops-container
|
|
4
3
|
description: Container operations. Use when building Docker images, writing Dockerfiles, creating Kubernetes manifests, or managing container lifecycle -- covers best practices, security scanning, and orchestration patterns.
|
|
@@ -92,4 +91,3 @@ Use a tagging and retention policy:
|
|
|
92
91
|
| Bake secrets into Dockerfile or image | Rotation and access control break immediately |
|
|
93
92
|
| Skip resource limits | Noisy neighbors and eviction behavior become unpredictable |
|
|
94
93
|
| Omit probes | Broken containers look healthy until users discover them |
|
|
95
|
-
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025). Adapted for SDTK-OPS. -->
|
|
2
1
|
|
|
3
2
|
# Kubernetes Manifest Patterns
|
|
4
3
|
|
|
@@ -113,4 +112,3 @@ spec:
|
|
|
113
112
|
- keep resource limits and probes in the first deployable version
|
|
114
113
|
- route config and secrets through references, not inline literals
|
|
115
114
|
- match `maxUnavailable` and `minAvailable` so rollout and maintenance rules do not fight each other
|
|
116
|
-
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025). Adapted for SDTK-OPS. -->
|
|
2
1
|
---
|
|
3
2
|
name: ops-cost
|
|
4
3
|
description: Cloud cost analysis and optimization. Use when reviewing infrastructure costs, right-sizing resources, or implementing cost reduction strategies -- covers cost allocation, tagging, reserved capacity, and budget alerts.
|
|
@@ -85,4 +84,3 @@ After a cost review:
|
|
|
85
84
|
- send architecture changes to `ops-infra-plan`
|
|
86
85
|
- deploy right-sizing changes with `ops-deploy`
|
|
87
86
|
- confirm savings and service health with `ops-verify`
|
|
88
|
-
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on superpowers by Jesse Vincent (MIT License, 2025). Adapted for SDTK-OPS. -->
|
|
2
1
|
---
|
|
3
2
|
name: ops-debug
|
|
4
3
|
description: Systematic infrastructure debugging. Use when encountering deployment failure, service outage, network issue, or unexpected infrastructure behavior -- binary search to root cause, evidence-first, no guessing fixes.
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025) and gstack by Garry Tan (MIT License, 2026). Adapted for SDTK-OPS. -->
|
|
2
1
|
---
|
|
3
2
|
name: ops-deploy
|
|
4
3
|
description: Deployment execution. Use when deploying infrastructure changes or application releases to any environment -- covers deployment strategies, health check gates, traffic management, and rollback procedures.
|
|
@@ -99,4 +98,3 @@ A deployment is complete only after:
|
|
|
99
98
|
- rollback remains possible or has been intentionally closed
|
|
100
99
|
- the exact evidence is recorded
|
|
101
100
|
- `ops-verify` confirms the post-deploy state
|
|
102
|
-
|
|
@@ -16,6 +16,25 @@ Use for:
|
|
|
16
16
|
- unclear routing between planning, debugging, deployment, monitoring, or security
|
|
17
17
|
- deciding which skill chain should run first
|
|
18
18
|
|
|
19
|
+
## OPS_HANDOFF Intake
|
|
20
|
+
|
|
21
|
+
If `DEV-Run` starts from `docs/dev/OPS_HANDOFF_[FEATURE_KEY].json`, inspect the handoff before choosing the first skill.
|
|
22
|
+
|
|
23
|
+
Read these fields first:
|
|
24
|
+
- `handoff_status`
|
|
25
|
+
- `suggested_next_ops_path`
|
|
26
|
+
- `open_blockers`
|
|
27
|
+
- `code_evidence_refs`
|
|
28
|
+
|
|
29
|
+
Routing rules:
|
|
30
|
+
- if `handoff_status` is `READY_FOR_SDTK_OPS`, default to `suggested_next_ops_path.start_with`
|
|
31
|
+
- treat `suggested_next_ops_path.suggested_chain` as the default chain unless fresh evidence requires a bounded reroute
|
|
32
|
+
- if `handoff_status` is `BLOCKED_FOR_SDTK_OPS`, the handoff is still inspectable but not a normal ready-path execution input
|
|
33
|
+
- blocked handoffs should route to bounded triage or clarification only; do not silently reinterpret them as deployment-ready
|
|
34
|
+
|
|
35
|
+
`SDTK-OPS` consumes the frozen handoff contract.
|
|
36
|
+
It does not redefine schema fields or invent alternate handoff names or locations.
|
|
37
|
+
|
|
19
38
|
## Priority Order
|
|
20
39
|
|
|
21
40
|
Choose in this order:
|
|
@@ -71,6 +90,8 @@ Use `ops-parallel` only when the work can safely split after the primary skill c
|
|
|
71
90
|
|
|
72
91
|
| Situation | Suggested Chain |
|
|
73
92
|
|-----------|-----------------|
|
|
93
|
+
| READY `OPS_HANDOFF` intake | `suggested_next_ops_path.start_with` -> `suggested_next_ops_path.suggested_chain` -> `ops-verify` |
|
|
94
|
+
| BLOCKED `OPS_HANDOFF` intake | inspect `open_blockers` -> bounded triage or clarification -> `ops-verify` only if a legal scoped OPS action actually runs |
|
|
74
95
|
| New service rollout | `ops-infra-plan` -> `ops-container` -> `ops-ci-cd` -> `ops-deploy` -> `ops-monitor` -> `ops-verify` |
|
|
75
96
|
| Production incident | `ops-incident` -> `ops-debug` -> `ops-deploy` -> `ops-verify` |
|
|
76
97
|
| Backup hardening | `ops-backup` -> `ops-infra-plan` -> `ops-monitor` -> `ops-verify` |
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025). Adapted for SDTK-OPS. -->
|
|
2
1
|
---
|
|
3
2
|
name: ops-incident
|
|
4
3
|
description: Incident response and management. Use when a production incident occurs or when establishing incident response procedures -- covers severity classification, response coordination, post-mortem facilitation, and on-call design.
|
|
@@ -110,4 +109,3 @@ During incident response:
|
|
|
110
109
|
- use `ops-debug` for diagnosis
|
|
111
110
|
- use `ops-monitor` to confirm recovery against live signals
|
|
112
111
|
- use `ops-verify` before declaring the system stable
|
|
113
|
-
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025). Adapted for SDTK-OPS. -->
|
|
2
1
|
|
|
3
2
|
# Communication Templates
|
|
4
3
|
|
|
@@ -31,4 +30,3 @@
|
|
|
31
30
|
**Impact Summary**: [who was affected and how]
|
|
32
31
|
**Follow-up**: Post-mortem scheduled for [date]. Action items will be tracked in [link].
|
|
33
32
|
```
|
|
34
|
-
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025). Adapted for SDTK-OPS. -->
|
|
2
1
|
|
|
3
2
|
# Incident Runbook Template
|
|
4
3
|
|
|
@@ -66,4 +65,3 @@
|
|
|
66
65
|
- External: [status page or customer update path]
|
|
67
66
|
- Follow-up: Create post-mortem within 48 hours
|
|
68
67
|
```
|
|
69
|
-
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025) and gstack by Garry Tan (MIT License, 2026). Adapted for SDTK-OPS. -->
|
|
2
1
|
---
|
|
3
2
|
name: ops-infra-plan
|
|
4
3
|
description: Infrastructure architecture planning. Use when designing cloud resources, networking, security groups, IAM policies, or IaC modules -- produces a reviewable infrastructure plan before provisioning.
|
|
@@ -83,7 +82,7 @@ Prefer reusable modules and explicit inputs over hand-built resources. Common pa
|
|
|
83
82
|
- alarms and dashboards defined in the same plan as the resource they guard
|
|
84
83
|
- environment-specific values separated from reusable module logic
|
|
85
84
|
|
|
86
|
-
Use `./references/iac-patterns.md` for concrete Terraform-style examples
|
|
85
|
+
Use `./references/iac-patterns.md` for concrete Terraform-style examples.
|
|
87
86
|
|
|
88
87
|
## Review Checklist
|
|
89
88
|
|
|
@@ -120,4 +119,3 @@ After the plan is approved:
|
|
|
120
119
|
- provision in dependency order
|
|
121
120
|
- verify each applied layer before moving forward
|
|
122
121
|
- use `ops-verify` before marking any provisioning step complete
|
|
123
|
-
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Based on agency-agents by AgentLand Contributors (MIT License, 2025) and gstack by Garry Tan (MIT License, 2026). Adapted for SDTK-OPS. -->
|
|
2
1
|
|
|
3
2
|
# IaC Patterns
|
|
4
3
|
|
|
@@ -138,4 +137,3 @@ Before applying an IaC change, confirm:
|
|
|
138
137
|
- network, identity, and secret dependencies are listed
|
|
139
138
|
- rollback covers both failed create and partial update
|
|
140
139
|
- health checks, alarms, and backups are defined with the resource
|
|
141
|
-
|