sdtk-ops-kit 0.2.5 → 0.2.6

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.
@@ -1,12 +1,12 @@
1
1
  {
2
- "version": "0.2.5",
3
- "sourceCommit": "17db9f2e515e7dc0cb120d0bf8dae4f01487a239",
2
+ "version": "0.2.6",
3
+ "sourceCommit": "c47349426d5c0a3cf63e5bb5e6a5e02c7c64b86c",
4
4
  "fileCount": 36,
5
5
  "files": [
6
6
  {
7
7
  "path": "toolkit/AGENTS.md",
8
- "sha256": "0387e747b9eb4500f810b338b28d795841e796fdaa40c4002e07b0d88b724167",
9
- "size": 11053
8
+ "sha256": "0871c6d46c64a093fc5f9d06af373db8143943cd27f144957dad0cc86893dc62",
9
+ "size": 15069
10
10
  },
11
11
  {
12
12
  "path": "toolkit/install.ps1",
@@ -35,13 +35,13 @@
35
35
  },
36
36
  {
37
37
  "path": "toolkit/sdtk-spec.config.json",
38
- "sha256": "8247ddf24502ce285bee213eefc801ce6b0b83afe00efd828468ac9130f53b09",
39
- "size": 111
38
+ "sha256": "ce760f639a09913b236be6dde6c692ea19ee92eb1d9e63d10dcdeb398e7ed2fb",
39
+ "size": 1209
40
40
  },
41
41
  {
42
42
  "path": "toolkit/sdtk-spec.config.profiles.example.json",
43
- "sha256": "e63d512ef00b750fea1d952be28e827fba8577ba536f32fa74e8708f48655ca7",
44
- "size": 303
43
+ "sha256": "e04ea5e3f72510e569ab849ebef3dea4a8728c2996c485e997d3e13a6c4f1f86",
44
+ "size": 1495
45
45
  },
46
46
  {
47
47
  "path": "toolkit/SDTKOPS_TOOLKIT.md",
@@ -1,11 +1,11 @@
1
- 0387e747b9eb4500f810b338b28d795841e796fdaa40c4002e07b0d88b724167 toolkit/AGENTS.md
1
+ 0871c6d46c64a093fc5f9d06af373db8143943cd27f144957dad0cc86893dc62 toolkit/AGENTS.md
2
2
  e79e1ab404abf83a4f90838a2f6450c387ada7e65b137a18f70f0cab74fc14f0 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
6
  fdb9631a80ecfb0d986a52a2833e88bf15c5303ab654d35bad6d64cca43046e8 toolkit/scripts/uninstall-codex-skills.ps1
7
- 8247ddf24502ce285bee213eefc801ce6b0b83afe00efd828468ac9130f53b09 toolkit/sdtk-spec.config.json
8
- e63d512ef00b750fea1d952be28e827fba8577ba536f32fa74e8708f48655ca7 toolkit/sdtk-spec.config.profiles.example.json
7
+ ce760f639a09913b236be6dde6c692ea19ee92eb1d9e63d10dcdeb398e7ed2fb toolkit/sdtk-spec.config.json
8
+ e04ea5e3f72510e569ab849ebef3dea4a8728c2996c485e997d3e13a6c4f1f86 toolkit/sdtk-spec.config.profiles.example.json
9
9
  58cfc74a11b8a0a18d0113a12e0e0b7a1188b253f7d19ff259d551914a831c4e toolkit/SDTKOPS_TOOLKIT.md
10
10
  1cd81e12cebdb2be528803e2d8afe43959aab1493e55499af529b99ec566a56c toolkit/skills/ops-backup/references/backup-script-patterns.md
11
11
  76e8385190d967bf98b3cafbbf8925d9b9c656ee7a7ed66ff51285b6459ebff1 toolkit/skills/ops-backup/SKILL.md
@@ -32,6 +32,8 @@ When starting a new session, read context in this order when the files exist:
32
32
 
33
33
  Do not read the entire historical session archive by default. Use `SDTK_SESSION_MEMORY_*.md` only when chronology or past acceptance details are required.
34
34
 
35
+ Active orchestration check: if `.sdtk/agent-runtime/runs/` holds a run whose state is not terminal (`running` or `waiting_for_approval`), surface it in one line (run id plus the blocking gate, if any) and offer `sdtk-agent run continue` before starting unrelated work, the same way `.sdtk/handoff/` items are surfaced.
36
+
35
37
  ## 3) Orchestrator-First Intake Protocol
36
38
  For every unprefixed user request:
37
39
  1. Classify the request intent before selecting PM/BA/ARCH/DEV/QA or a downstream product lane.
@@ -63,6 +65,7 @@ Use this compact matrix during intake so the agent picks the smallest sufficient
63
65
  | Atlas graph build or viewer work | `sdtk-spec atlas` compatibility workflow or `sdtk-wiki atlas` for canonical SDTK-WIKI work | Local `.sdtk/atlas` compatibility graph or `.sdtk/wiki` SDTK-WIKI result |
64
66
  | SDTK-WIKI Ask | `sdtk-wiki ask` | Grounded answer when `.sdtk/wiki/graph` plus `wiki.ask` entitlement/runtime preconditions are present, otherwise explicit blocker |
65
67
  | Existing project scan: project ingest, project refresh, or project audit | Matching premium project workflow | Project-local foundation, refresh, or audit result without overclaiming entitlement |
68
+ | Multi-step durable workflow: 3+ dependent steps, human gates between steps, must survive a pause, or spans multiple lanes/sessions | Propose `sdtk-agent` orchestration (opt-in, token-aware, see the orchestration cost gate in section 5) | `.sdtk/agent-runtime/runs/<run_id>/` ledger plus `reports/final_report.md` |
66
69
  | "what should we do next" | Orchestrator state review | Recommended next action with rationale and lane choice |
67
70
 
68
71
  Guardrails:
@@ -78,6 +81,7 @@ Ask clarification when:
78
81
  3. the target repo, project, or path is missing
79
82
  4. implementation is requested without an acceptance boundary
80
83
  5. the next command could mutate external state
84
+ 6. the next step would spawn multiple sub-agents or incur significant token cost, such as dispatching an `sdtk-agent` run
81
85
 
82
86
  Proceed when:
83
87
  1. the intent and target are clear
@@ -85,6 +89,16 @@ Proceed when:
85
89
  3. the user already approved the relevant plan or spec
86
90
  4. the requested change is bounded and verifiable
87
91
 
92
+ ### 5.1) Orchestration Cost Gate (sdtk-agent)
93
+ `sdtk-agent` chains multiple steps and dispatches each ready task through an adapter, so a single run can spawn many sub-agents and consume significant token budget. Because of that cost, orchestration is always opt-in:
94
+
95
+ 1. Never auto-start an `sdtk-agent` run on the user's behalf. Only propose it.
96
+ 2. Propose only when a routing trigger is hit (the multi-step row in section 4) and the workflow clears the minimum size (default: 3 dependent steps). One- or two-step bounded tasks route straight to a lane instead of orchestration.
97
+ 3. When proposing, state the trade-off concretely and let the user decide, defaulting to "no / run inline". Run `sdtk-agent workflow validate` first (it does not spawn anything) to count tasks, human gates, and adapter dispatches, then quote a cost band: dispatch count 3 or fewer is Low, 4-8 is Medium, more than 8 or any loop/retry is High. Example:
98
+ > This request fits sdtk-agent: durable, resumable, with hard approval gates, but it will spawn several agents and cost more tokens than an inline run. Estimate: 9 steps, 3 gates, 11 dispatches (token cost: HIGH). Use sdtk-agent for this, or run it inline? (default: inline)
99
+ 4. `run start` only creates the ledger and never spawns; treat it as the safe preview point. Dispatch happens on `run continue`, which is an explicit user action. Before a `run continue` that would dispatch several ready tasks at once, report how many tasks and which adapters are about to run, and let the user confirm or step through one task at a time.
100
+ 5. Honor `.sdtk/agent-runtime/config.json` `orchestration.confirmationMode` (`always` by default): no mode ever allows dispatch without at least one confirmation per run.
101
+
88
102
  ## 6) Clarification Protocol
89
103
  Apply for all roles (`/pm`, `/ba`, `/arch`, `/dev`, `/qa`):
90
104
  1. If there is ambiguity or missing data, log `Open Questions` as `OQ-xx` in the current phase artifact.
@@ -122,6 +136,9 @@ Use the suite products according to task intent:
122
136
  - requirements, BA, PRD, backlog, architecture, QA artifacts
123
137
  - handoff generation and release-gate traceability
124
138
  - entry: `/orchestrator` (recommended), `/pm`, `/ba`, `/arch`, `/dev`, `/qa`
139
+ - `SDTK-DESIGN`
140
+ - screen/layout design, visual tokens, prototype evidence, design handoff before coding
141
+ - use before `SDTK-CODE` when implementation needs reviewable screens or a design handoff
125
142
  - `SDTK-CODE`
126
143
  - build a feature
127
144
  - fix a bug
@@ -138,6 +155,18 @@ Use the suite products according to task intent:
138
155
  - monitoring, incident response, security-infra, backup, compliance
139
156
  - entry: `ops-discover` (when boundary is unclear), `ops-plan`, `ops-deploy`, `ops-incident`, `ops-monitor`, `ops-backup`, `ops-verify`, `ops-debug`
140
157
 
158
+ Cross-cutting capabilities (not a linear lane; usable across every phase):
159
+
160
+ - `SDTK-WIKI` (memory)
161
+ - project knowledge graph, docs view, and grounded `sdtk-wiki ask`
162
+ - any lane may read from it for recall; build with `sdtk-wiki atlas build`
163
+ - `SDTK-AGENT` (orchestration)
164
+ - a durable, file-driven DAG controller that sits above `sdtk-code` agent-team; it does not own a phase, it chains steps across lanes
165
+ - surface: `sdtk-agent run start|continue|status|report`, `gate approve|reject`, `workflow validate`, `adapter hermes-kanban plan`
166
+ - use only when a workflow has 3+ dependent steps, needs human gates between steps, or must survive a pause; otherwise route straight to a lane
167
+ - opt-in and token-aware: always propose-then-confirm before dispatch (see the orchestration cost gate in section 5)
168
+ - the CLI is runtime-neutral and installs no skills; the engine is Free, and live external dispatch is not part of this release (hermes-kanban is dry-run only)
169
+
141
170
  If the current project only has `SDTK-SPEC` runtime assets installed:
142
171
  - keep `/dev` bounded to planning and `CODE_HANDOFF`
143
172
  - do not overclaim that SDTK-CODE or SDTK-OPS runtime assets are already installed
@@ -156,6 +185,8 @@ If the current project only has `SDTK-SPEC` runtime assets installed:
156
185
  - For SDTK-SPEC-only installs: keep `/dev` bounded to planning and `CODE_HANDOFF`; do not claim SDTK-CODE or SDTK-OPS are installed.
157
186
  - For Codex runtimes: project-local skills require the explicit local `CODEX_HOME=<project>/.codex` contract; native `.codex/skills` auto-discovery is not claimed.
158
187
  - Use `ops-parallel` or `code-parallel` only for truly independent slices. If parallel dispatch is unavailable in the active runtime, execute them sequentially in one controller session.
188
+ - `SDTK-AGENT` is runtime-neutral: it installs no skills and behaves identically on Claude and Codex. It is CLI-only, so do not invent a slash command for it.
189
+ - The `sdtk-agent` hermes-kanban adapter is dry-run only in this release; it never calls a live gateway or creates a real card. Live dispatch is a future Pro capability, so do not claim it.
159
190
 
160
191
  ## 11) Discovery And PM Readiness
161
192
  - PM initiation starts only after `docs/discovery/REQUIREMENT_[FEATURE_KEY].md` is marked `READY_FOR_PM_INITIATION`.
@@ -1,6 +1,38 @@
1
1
  {
2
- "toolkit": "SDTK-OPS",
3
- "version": "1.0.0",
4
- "skills_path": "toolkit/skills",
5
- "skill_prefix": "ops-"
2
+ "docs": {
3
+ "artifactsLanguage": "EN",
4
+ "guidanceLanguage": "VI",
5
+ "preserveOriginalInput": true,
6
+ "appendixIncludeEnglishTranslation": true,
7
+ "aiPeerReviewAllowed": true
8
+ },
9
+ "orchestration": {
10
+ "apiDesignDetailMode": "auto",
11
+ "testCaseSpecMode": "auto"
12
+ },
13
+ "stack": {
14
+ "backend": "Set your backend stack (example: Python Django REST Framework)",
15
+ "frontend": "Set your frontend stack (example: React + Vite)",
16
+ "mobile": "N/A",
17
+ "database": "Set your database (example: PostgreSQL 15)",
18
+ "auth": "Set your auth strategy (example: JWT/OAuth2)",
19
+ "detection": {
20
+ "language": null,
21
+ "framework": null,
22
+ "frameworkVersion": null,
23
+ "packageManager": null,
24
+ "confidence": "low",
25
+ "evidence": [],
26
+ "detectedAt": null,
27
+ "method": "static"
28
+ }
29
+ },
30
+ "commands": {
31
+ "backendTests": "UPDATE_ME: set backend test command",
32
+ "backendTypecheck": "UPDATE_ME: set backend typecheck command",
33
+ "backendLint": "UPDATE_ME: set backend lint command",
34
+ "frontendTests": "UPDATE_ME: set frontend test command",
35
+ "frontendLint": "UPDATE_ME: set frontend lint command",
36
+ "e2eTests": "UPDATE_ME: set e2e test command"
37
+ }
6
38
  }
@@ -1,12 +1,50 @@
1
1
  {
2
- "$comment": "Example profiles config for SDTK-OPS. Copy to sdtk-spec.config.profiles.json and customize for your runtime targets.",
3
2
  "profiles": {
4
- "default": {
3
+ "django-react": {
4
+ "orchestration": {
5
+ "apiDesignDetailMode": "auto",
6
+ "testCaseSpecMode": "auto"
7
+ },
5
8
  "stack": {
6
- "backend": "UPDATE_ME",
7
- "frontend": "UPDATE_ME",
8
- "database": "UPDATE_ME"
9
+ "backend": "Python 3.11 + Django 4.x + Django REST Framework",
10
+ "frontend": "React 18 + Vite",
11
+ "mobile": "N/A",
12
+ "database": "PostgreSQL 15",
13
+ "auth": "JWT"
14
+ },
15
+ "commands": {
16
+ "backendTests": "python -m pytest",
17
+ "backendTypecheck": "python -m mypy src/backend",
18
+ "backendLint": "python -m ruff check src/backend",
19
+ "frontendTests": "npm run test",
20
+ "frontendLint": "npm run lint",
21
+ "e2eTests": "npm run e2e"
22
+ }
23
+ },
24
+ "node-nextjs": {
25
+ "orchestration": {
26
+ "apiDesignDetailMode": "auto",
27
+ "testCaseSpecMode": "auto"
28
+ },
29
+ "stack": {
30
+ "backend": "Node.js 20 + Express/Fastify",
31
+ "frontend": "Next.js 14",
32
+ "mobile": "N/A",
33
+ "database": "PostgreSQL 15",
34
+ "auth": "OAuth2 + JWT"
35
+ },
36
+ "commands": {
37
+ "backendTests": "npm run test:api",
38
+ "backendTypecheck": "npm run typecheck:api",
39
+ "backendLint": "npm run lint:api",
40
+ "frontendTests": "npm run test:web",
41
+ "frontendLint": "npm run lint:web",
42
+ "e2eTests": "npm run test:e2e"
9
43
  }
10
44
  }
11
- }
45
+ },
46
+ "notes": [
47
+ "Copy one profile into sdtk-spec.config.json and adjust for your project.",
48
+ "Do not keep UPDATE_ME placeholders before running real delivery gates."
49
+ ]
12
50
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "sdtk-ops-kit",
3
- "version": "0.2.5",
3
+ "version": "0.2.6",
4
4
  "description": "Skill-driven operations toolkit for deployment, verification, monitoring, incident response, backup, security, compliance, and cost discipline.",
5
5
  "bin": {
6
6
  "sdtk-ops": "bin/sdtk-ops.js"