opensddrag 0.2.0 → 0.2.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opensddrag",
-  "version": "0.2.0",
+  "version": "0.2.2",
   "description": "CLI client to connect any project to the OpenSddRag SDD+Harness MCP server",
   "keywords": [
     "sdd",

package/src/templates/skills/apply.js

@@ -7,18 +7,27 @@ export const applySkill = {
   body: (slug, note) => `# OpenSddRag — Apply
 ${note}## When to use
 To implement tasks one at a time, validating each against its spec acceptance criteria before
-marking it done. Read ALL planning artifacts (proposal + specs + design) as context first.
+marking it done. Read the design (and, per task, the spec it implements) as context — the
+proposal is not re-read during apply, since the design already encodes its decisions.
 
 ## Inputs
 $ARGUMENTS = change name, or a specific task name.
 
 ## Workflow
 
-### Step 1 — Load full planning context
-\`get_working_context(project_slug="${slug}")\`
-\`read_artifact(name="<change-name>-proposal", project_slug="${slug}")\`
-\`read_artifact(name="<change-name>-design", project_slug="${slug}")\`
-Get and read all specs linked to this change.
+### Step 1 — Load implementation context
+1. Load the working context:
+   \`get_working_context(project_slug="${slug}")\`
+2. Fetch the list of all artifacts to serve as the freshness oracle:
+   \`list_artifacts(project_slug="${slug}")\`
+3. Retrieve the change's design content (\`<change-name>-design\`):
+   - Locate the design artifact in the \`list_artifacts\` results to get its \`id\` and \`updated_at\`.
+   - If no design exists, output "Design missing for change '<change-name>'. Run /opsr:design before /opsr:apply." and STOP.
+   - Look up the design's \`id\` in the working context's \`context.content_cache\` (if present):
+     - **CACHE HIT:** If the cache entry exists and its \`updated_at\` matches the oracle's \`updated_at\`, use the cached design content. Do not call \`read_artifact\`.
+     - **CACHE MISS/STALE:** If the cache entry is missing or its \`updated_at\` does not match, call \`read_artifact(name="<change-name>-design", project_slug="${slug}")\`. Then, update the working context cache by calling \`update_working_context\` with \`context.content_cache[<artifact_id>] = {type: "design", content: "<content>", updated_at: "<updated_at>"}\`.
+4. Do NOT read the proposal during apply — its rationale is already captured in the design.
+5. Read the specific spec a task implements pointwise at validation time (Step 6) using the same caching logic (check cache, hit → use, miss/stale → read and cache). Tasks themselves are never cached.
 
 ### Step 2 — List pending tasks
 \`list_artifacts(type="task", status="active", project_slug="${slug}")\`
@@ -57,7 +66,7 @@ ${harnessChecklistBlock(slug, "on_apply", "Marking the task archived")}
 - Task status advanced draft → active → archived in the database.
 
 ## Important rules
-- Read ALL planning artifacts before implementing — never code from the task alone.
+- Read the design and the task's spec before implementing — never code from the task alone. Do not re-read the proposal during apply.
 - Run the harness checklist (on_apply) BEFORE marking a task archived; STOP on any error-severity rule.
 - One task at a time; do not batch-archive tasks.
 `,

package/src/templates/skills/archive.js

@@ -13,21 +13,21 @@ $ARGUMENTS = change name. If not provided, list active changes and ask.
 
 ## Workflow
 
-### Step 1 — Get the full status of the change
-\`list_artifacts(type="proposal", project_slug="${slug}")\`
-\`get_relationships(name="<change-name>-proposal", project_slug="${slug}")\`
-Gather all linked artifacts (specs, design, tasks).
+### Step 1 — Load the change bundle
+\`read_change_bundle(change_name="<change-name>", project_slug="${slug}")\`
+Archiving sweeps every artifact of the change, so load them all in one call. The
+response carries the proposal, design, specs, and the task list
+(\`tasks[] = {name, status}\`) with \`task_count\`. Proceed to Step 2.
 
 ### Step 2 — Validate artifact completion
-\`list_artifacts(type="task", status="draft", project_slug="${slug}")\`
+From the bundle's \`tasks[]\`, treat any task whose \`status\` is not \`archived\` as pending.
 If pending tasks exist → warn the user and ask for confirmation to archive anyway.
 
 ### Step 3 — Validate task completion
-Count draft vs archived tasks. If any draft tasks remain → warn and confirm.
+Count pending vs archived tasks from the bundle. If any non-archived tasks remain → warn and confirm.
 
 ### Step 4 — Check for delta specs that need syncing
-\`list_artifacts(type="spec", project_slug="${slug}")\`
-Filter for metadata.change_name = "<change-name>" AND metadata.is_delta = true.
+From the bundle's \`specs[]\`, filter for metadata.change_name = "<change-name>" AND metadata.is_delta = true.
 If deltas exist: show the affected capabilities and ask "Sync delta specs to main specs now? (recommended)".
 - If yes → run the /opsr:sync workflow (load the opensddrag-sync skill) for each delta.
 - If no → archive without syncing.

package/src/templates/skills/index.js

@@ -49,7 +49,7 @@ const frontmatter = (name, description) =>
  */
 export function getSkills(slug, serverUrl) {
   const note = `> **MCP server:** \`opensddrag\` (${serverUrl}) | **project_slug:** \`${slug}\`
-> **Available tools:** \`create_artifact\`, \`read_artifact\`, \`list_artifacts\`, \`update_artifact\`, \`validate_artifact\`, \`link_artifacts\`, \`get_relationships\`, \`search_semantic\`, \`recall_episodes\`, \`get_working_context\`, \`update_working_context\`, \`record_trace\`, \`get_harness_checklist\`
+> **Available tools:** \`create_artifact\`, \`read_artifact\`, \`list_artifacts\`, \`read_change_bundle\`, \`update_artifact\`, \`validate_artifact\`, \`link_artifacts\`, \`get_relationships\`, \`search_semantic\`, \`recall_episodes\`, \`get_working_context\`, \`update_working_context\`, \`record_trace\`, \`get_harness_checklist\`
 > If these tools are not in your active tool list, the \`opensddrag\` MCP server is not connected — STOP and inform the user.\n\n`;
 
   return SKILLS.map((skill) => ({

package/src/templates/skills/verify.js

@@ -14,16 +14,19 @@ $ARGUMENTS = change name.
 
 ## Workflow
 
-### Step 1 — Load all artifacts
-\`read_artifact(name="<change-name>-proposal", project_slug="${slug}")\`
-\`read_artifact(name="<change-name>-design", project_slug="${slug}")\`
-\`get_relationships(name="<change-name>-proposal", project_slug="${slug}")\`
-Read each linked spec and task artifact.
+### Step 1 — Load the change bundle
+\`read_change_bundle(change_name="<change-name>", project_slug="${slug}")\`
+Verification is holistic, so load everything in one call. The response carries the
+proposal, design, full specs, and a task list (\`tasks[] = {name, status}\`) with
+\`task_count\`. If \`task_count\` does not equal the number of returned task entries,
+report an **incomplete bundle** for the change and STOP before declaring verification
+complete. Otherwise proceed — do **not** issue additional \`read_artifact\` calls for
+the proposal, design, or specs.
 
 ### Step 2 — Verify COMPLETENESS
-\`list_artifacts(type="task", status="draft", project_slug="${slug}")\`
+From the bundle's \`tasks[]\`, treat any task whose \`status\` is not \`archived\` as pending.
 - If pending tasks exist → **CRITICAL: Tasks not complete**.
-Extract every REQ-NNN from the specs and search the codebase for implementation evidence.
+Extract every REQ-NNN from the bundle's specs and search the codebase for implementation evidence.
 - If a requirement has no evidence → **CRITICAL: Requirement not implemented**.
 
 ### Step 3 — Verify CORRECTNESS