🎩 You're Invited:Meet the Socket team at Black Hat in Las Vegas, August 3-6.RSVP →
Sign In

@clawplays/ospec-cli

Package Overview
Dependencies
Maintainers
1
Versions
48
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@clawplays/ospec-cli - npm Package Compare versions

Comparing version
1.8.14
 to
1.8.15
+1
-1
assets/for-ai/ar/execution-protocol.md

@@ -64,3 +64,3 @@ ---

- في Goal مملوكة لـ controller، استخدم `ospec loop tick [changes/active/<change>]` بعد اكتمال كل worker task لإنشاء مراجعة موحدة مرتبطة بـ executor provenance الحقيقي وحزمة محدودة النطاق. استخدم `ospec execute review ... --task <task-id>` مباشرةً فقط خارج controller Loop
- عند تفعيل `documentation_updates` في task graph، يجب أن تحتوي كل مهمة على المصفوفة (`[]` عند عدم الحاجة)، وأن يظهر كل مسار docs معلن أيضا في `target_files` للمهمة نفسها، وأن يكون موجودا قبل الأرشفة، وأن يملك دليلا على تغير محتوى فعلي بين dispatch وcomplete. تبقى التشغيلات القديمة بلا baseline متوافقة لكنها تعرض الدليل كغير متحقق.
- عند تفعيل `documentation_updates` في task graph، يجب أن تحتوي كل مهمة على المصفوفة (`[]` عند عدم الحاجة)، وأن يظهر كل مسار docs معلن أيضا في `target_files` للمهمة نفسها، وأن يملك دليلا على تغير فعلي بين dispatch وcomplete. يعد الحذف الذي تمت مراجعته تغييرا صالحا عندما يثبت evidence أن baseline موجودا أصبح مفقودا عند الإكمال. عبر محاولات repair المتعددة يقارن finalize أول baseline بالحالة النهائية المكتملة، ويشترط أن تطابق workspace أحدث evidence لمالك المسار المعلن، لذلك لا يكفي تغيير قديم ولا يمر التراجع اللاحق. تبقى التشغيلات القديمة بلا baseline متوافقة فقط عندما تظل الوثيقة المعلنة موجودة، وتعرض الدليل كغير متحقق.
- بعد اعتماد task-level reviews واكتمال task graph، دع `ospec loop tick` التالي ينشئ final review في controller Loop؛ استخدم `ospec execute review` من دون `--task` فقط خارج controller Loop

@@ -67,0 +67,0 @@ - بعد أن يحتوي review artifact على قرار غير `PENDING`، استخدم `ospec execute feedback [changes/active/<change>] [--stage spec|quality]` لكتابة `artifacts/agents/review-feedback-plan.json` و`artifacts/agents/review-feedback-plan.md`؛ حدد accept أو revise أو clarify أو blocked قبل dispatch عمل إضافي، وأنشئ required user decision عندما يغير feedback scope أو direction أو API أو UI أو risk أو accepted tradeoffs، وأنشئ required user decision gate عندما يغير feedback scope أو direction أو API أو UI أو risk أو accepted tradeoffs

+1
-1
assets/for-ai/en-US/execution-protocol.md

@@ -73,3 +73,3 @@ ---

- For goals, derive `tasks.md` from `artifacts/agents/task-graph.json`; if tasks already exist but upstream docs are still templates, update them first and then reconcile tasks. For classic changes, derive `tasks.md` directly from `proposal.md` and the implementation scope.
- When a task graph includes `documentation_updates`, include that array on every task (`[]` when none); every declared docs path must also appear in that task's `target_files`, exist before archive, and have dispatch-to-completion meaningful-change evidence. Legacy runs without a captured baseline remain compatible but must report the evidence as unverified.
- When a task graph includes `documentation_updates`, include that array on every task (`[]` when none); every declared docs path must also appear in that task's `target_files` and have dispatch-to-completion meaningful-change evidence. A reviewed deletion is valid when evidence proves an existing baseline became missing. Across repair attempts, finalize compares the first baseline with the final completed state and requires the workspace to match the latest declared-owner evidence, so an old change or later reversion cannot pass. Legacy runs without a captured baseline remain compatible only when the declared document still exists and must report the evidence as unverified.
- For goals, do not archive while `artifacts/agents/task-graph.json` has unresolved task statuses, invalid dependencies, missing execution details, or top-level `status` other than `completed`

@@ -76,0 +76,0 @@ - Complete each task's single combined review (`artifacts/reviews/tasks/<task-id>/review.md`), then complete the single final `artifacts/reviews/final-review.md`; unresolved task-level or final review decisions block archive

+1
-1
assets/for-ai/ja-JP/execution-protocol.md

@@ -63,3 +63,3 @@ ---

- controller-owned Goal では、各 worker task 完了後に `ospec loop tick [changes/active/<change>]` で実 executor provenance に結び付いた統合 review と task-scoped package を作成する。`ospec execute review ... --task <task-id>` を直接使うのは non-controller workflow のみとする
- task graph で `documentation_updates` を有効にした場合、各 task に配列を持たせ（不要なら `[]`）、宣言した docs path を同じ task の `target_files` に含め、archive 前に存在させ、dispatch から complete までの有意な content change evidence を残す。baseline のない旧 run は互換性を保つが未検証と表示する。
- task graph で `documentation_updates` を有効にした場合、各 task に配列を持たせ（不要なら `[]`）、宣言した docs path を同じ task の `target_files` に含め、dispatch から complete までの有意な content change evidence を残す。既存 baseline が完了時に missing になったことを evidence が証明する reviewed deletion は有効な変更である。複数 repair attempt では finalize が最初の baseline と最後の完了状態を比較し、workspace がその path の最新 declared owner evidence と一致することを要求するため、古い変更や後続の reversion は通過しない。baseline のない旧 run は宣言文書が現在も存在する場合だけ互換性を保ち、未検証と表示する。
- task graph 完了後の final review も controller Loop の次の `ospec loop tick` で発行する。`--task` なしの `ospec execute review` を直接使うのは non-controller workflow のみとする

@@ -66,0 +66,0 @@ - review artifact が non-`PENDING` decision を持つ場合は `ospec execute feedback [changes/active/<change>] [--stage spec|quality]` で `artifacts/agents/review-feedback-plan.json` と `artifacts/agents/review-feedback-plan.md` を書く。追加作業を dispatch する前に accept、revise、clarify、blocked の handling を明確にし、feedback が scope、direction、API、UI、risk、accepted tradeoffs を変える場合は required user decision gate を作成する

+1
-1
assets/for-ai/zh-CN/execution-protocol.md

@@ -66,3 +66,3 @@ ---

- worker 记录 `DONE` 或 `DONE_WITH_CONCERNS` 后，controller-owned Goal 用 `ospec loop tick [changes/active/<change>]` 生成带真实 executor provenance 的合并 review action 和范围受控的 `artifacts/agents/review-packages/*.diff`；只有非 controller 流程才直接运行 `ospec execute review ... --task <task-id>`
- task graph 启用 `documentation_updates` 后，每个 task 都必须包含该数组（没有则为 `[]`）；声明的 docs 路径必须同时出现在同一 task 的 `target_files` 中、在归档前存在，并具有从 dispatch 到 complete 的有效内容变化证据。没有历史基线的旧流程保持兼容，但必须把证据标记为无法验证。
- task graph 启用 `documentation_updates` 后，每个 task 都必须包含该数组（没有则为 `[]`）；声明的 docs 路径必须同时出现在同一 task 的 `target_files` 中，并具有从 dispatch 到 complete 的有效内容变化证据。若 evidence 证明已有 baseline 在完成时变为不存在，则经过 review 的删除属于有效变化。多轮 repair 时，finalize 比较首个 baseline 与最终完成态，并要求当前工作区匹配该路径最后一个声明 owner 的 evidence，旧修改或后续回退不能通过。没有历史 baseline 的旧流程仅在声明文档仍存在时保持兼容，并必须把证据标记为无法验证。
- 所有单任务 review 通过且 task graph 完成后，controller Loop 用下一次 `ospec loop tick` 生成最终整体 review；只有非 controller 流程才直接运行不带 `--task` 的 `ospec execute review`

@@ -69,0 +69,0 @@ - review artifact 有非 `PENDING` 决策后，用 `ospec execute feedback [changes/active/<change>] [--stage spec|quality]` 写入 `artifacts/agents/review-feedback-plan.json` 和 `artifacts/agents/review-feedback-plan.md`；继续派发工作前，必须明确接受、修订、澄清或解除阻塞；当反馈影响范围、方向、API、UI、风险或已接受取舍时创建 required user decision gate

+1
-1
assets/global-skills/codex/ospec-goal/SKILL.md

@@ -83,3 +83,3 @@ ---

6. Draft or update `implementation-plan.md` from `design.md`; identify target files, expected results, verification commands, dependencies, parallelizable work, and conflicts.
7. Derive `artifacts/agents/task-graph.json` from `implementation-plan.md`; give every task a `documentation_updates` array (`[]` when none), include every declared docs path in the same task's `target_files`, and require meaningful-change evidence from dispatch to completion; derive `tasks.md` from the task graph. Mark every dependency/file-safe task `parallelizable: true`; every generated `parallelizable: false` task must include `serial_reason`, and `maxParallel=1` must include `maxParallelReason`. Split tasks with more than six `target_files`; when one atomic verification boundary genuinely requires that breadth, record a concrete `scope_reason`. Split implementation/automatic checks from external device, credential, third-party, or manual acceptance so an unavailable external gate cannot block unrelated implementation; downstream work may depend on the implementation slice, while the external acceptance remains a final hard gate. For L3 use `ospec loop allowlist derive/check/apply --from-task-graph` so exact paths and commands fail before expensive document reviewers run; never assume repeated configure calls append. Finalize also generates one indexed `docs/project/changes/<archive-path>.md` for this goal; its preflight refuses to overwrite a human-owned file at that path, and the generated summary does not replace required architecture, API, module, or operational documentation.
7. Derive `artifacts/agents/task-graph.json` from `implementation-plan.md`; give every task a `documentation_updates` array (`[]` when none), include every declared docs path in the same task's `target_files`, and require meaningful-change evidence from dispatch to completion; derive `tasks.md` from the task graph. Reviewed deletion is valid when completion evidence proves an existing baseline became missing. Across repair attempts, finalize compares the first baseline with the final completed state and requires the workspace to match the latest declared-owner evidence; do not restore a legitimately deleted document or rewrite history to satisfy archive. Mark every dependency/file-safe task `parallelizable: true`; every generated `parallelizable: false` task must include `serial_reason`, and `maxParallel=1` must include `maxParallelReason`. Split tasks with more than six `target_files`; when one atomic verification boundary genuinely requires that breadth, record a concrete `scope_reason`. Split implementation/automatic checks from external device, credential, third-party, or manual acceptance so an unavailable external gate cannot block unrelated implementation; downstream work may depend on the implementation slice, while the external acceptance remains a final hard gate. For L3 use `ospec loop allowlist derive/check/apply --from-task-graph` so exact paths and commands fail before expensive document reviewers run; never assume repeated configure calls append. Finalize also generates one indexed `docs/project/changes/<archive-path>.md` for this goal; its preflight refuses to overwrite a human-owned file at that path, and the generated summary does not replace required architecture, API, module, or operational documentation.
8. Run `ospec execute doc-review [changes/active/<goal>] --stage design`. When it reports `Reused approval: yes`, do not launch another reviewer. Otherwise execute one fresh independent design reviewer through `dispatch.runtimeAdapter`, immediately claim its real executor id, wait for Markdown plus structured findings, then complete that executor. Approval must validate before plan review.

@@ -86,0 +86,0 @@ 9. Run `ospec execute doc-review [changes/active/<goal>] --stage plan`. Reuse a valid approval; otherwise execute one fresh independent plan reviewer through `dispatch.runtimeAdapter`, claim its real executor id, wait for findings, then complete it before worker dispatch. The controlling AI must not self-approve either review.

+1
-1
dist/cli.js

@@ -65,3 +65,3 @@ #!/usr/bin/env node

const services_1 = require("./services");
const CLI_VERSION = '1.8.14';
const CLI_VERSION = '1.8.15';
function showInitUsage() {

@@ -68,0 +68,0 @@ console.log('Usage: ospec init [root-dir] [--summary "..."] [--tech-stack node,react] [--architecture "..."] [--document-language en-US|zh-CN|ja-JP|ar]');

+1
-1
package.json
{
"name": "@clawplays/ospec-cli",
"version": "1.8.14",
"version": "1.8.15",
"description": "Official OSpec CLI package for spec-driven development (SDD) and document-driven development in AI coding agent and CLI workflows.",

@@ -5,0 +5,0 @@ "main": "dist/index.js",

dist/services/ProjectService.js

Sorry, the diff of this file is too big to display

dist/services/TaskGraphExecutionService.js

Sorry, the diff of this file is too big to display