npm - @mrciphersmith/keryx - Versions diffs - 0.2.71 → 0.2.73 - Mend

@mrciphersmith/keryx 0.2.71 → 0.2.73

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.

Files changed (162) hide show

package/src/gdskills/bundled/skills/orchestration/job-documenter/SKILL.opencode.md CHANGED Viewed

@@ -1,6 +1,7 @@
 ---
 name: job-documenter
-description: "Creates and maintains structured job documentation in jobs/. Called by job-orchestrator to initialize job folders, create analysis/report/review documents, and maintain the job README. Follows jobs-documentation.mdc conventions."
+model_tier: light
+description: "Use when a job folder needs to be initialized, or analysis/report/review documents need to be created or updated in jobs/."
 triggers:
   - "Document job"
   - "Initialize job folder"
@@ -14,11 +15,19 @@ metadata:
 license: "MIT"
 ---
+<SUBAGENT-STOP>
+If you were dispatched as a subagent to execute a specific task, skip this skill entirely.
+This skill is for orchestrators and interactive session-level routing only.
+Proceed directly with your assigned task.
+</SUBAGENT-STOP>
 # Job Documenter
+> **JOBS_ROOT Note:** `JOBS_ROOT` is always passed explicitly by the orchestrator in the dispatch prompt. Never resolve it yourself — do not fall back to any hardcoded path.
 ## Purpose
-Sub-agent responsible for creating and maintaining structured job documentation in `.metaproject/jobs/`. Called exclusively by `job-orchestrator` to persist the lifecycle of orchestrated tasks — from initial plan through analysis, implementation, review, and final report.
+Sub-agent responsible for creating and maintaining structured job documentation in `<JOBS_ROOT>/`. Called exclusively by `job-orchestrator` to persist the lifecycle of orchestrated tasks — from initial plan through analysis, implementation, review, and final report.
 **This skill is NOT invoked directly by users.** It is a service skill dispatched by the orchestrator.
@@ -43,7 +52,7 @@ The orchestrator provides a structured prompt with the following fields:
 ```
 ACTION:    init | add-document | update-readme | finalize
 JOB_NAME:  <kebab-case folder name>
-JOBS_ROOT: .metaproject/jobs
+JOBS_ROOT: <JOBS_ROOT>
 DATA:      <action-specific payload — see below>
 ```
@@ -150,7 +159,7 @@ PLAN:        <ordered list of planned steps>
    DOCUMENTER_RESULT:
      action: init
      status: success | error
-     job_path: .metaproject/jobs/<JOB_NAME>
+     job_path: <JOBS_ROOT>/<JOB_NAME>
      files_created: [README.md, man/plan.md, ai/plan.md]
      error_details: <if status is error>
    ```
@@ -299,7 +308,7 @@ SUMMARY:       <1-3 sentence summary of what was accomplished>
    DOCUMENTER_RESULT:
      action: finalize
      status: success | error
-     job_path: .metaproject/jobs/<JOB_NAME>
+     job_path: <JOBS_ROOT>/<JOB_NAME>
      final_status: <FINAL_STATUS>
      total_documents: <count of all files in man/ + ai/>
      verification: passed | <list of discrepancies>
@@ -336,12 +345,12 @@ When the orchestrator dispatches this skill as a sub-agent, it should use this p
 ```
 You are the job-documenter agent. Your task is to manage job documentation.
-Load the skill from: skills/job-documenter/SKILL.md
+Load the skill from: skills/orchestration/job-documenter/SKILL.md
 Follow the rules from: rules/core/jobs-documentation.mdc
 ACTION: <action>
 JOB_NAME: <job-name>
-JOBS_ROOT: .metaproject/jobs
+JOBS_ROOT: <JOBS_ROOT>
 DATA:
 <action-specific data>

package/src/gdskills/bundled/skills/orchestration/job-documenter/SKILL.zed.md CHANGED Viewed

@@ -1,6 +1,7 @@
 ---
 name: job-documenter
-description: "Creates and maintains structured job documentation in jobs/. Called by job-orchestrator to initialize job folders, create analysis/report/review documents, and maintain the job README. Follows jobs-documentation.mdc conventions."
+model_tier: light
+description: "Use when a job folder needs to be initialized, or analysis/report/review documents need to be created or updated in jobs/."
 triggers:
   - "Document job"
   - "Initialize job folder"
@@ -14,11 +15,19 @@ metadata:
 license: "MIT"
 ---
+<SUBAGENT-STOP>
+If you were dispatched as a subagent to execute a specific task, skip this skill entirely.
+This skill is for orchestrators and interactive session-level routing only.
+Proceed directly with your assigned task.
+</SUBAGENT-STOP>
 # Job Documenter
+> **JOBS_ROOT Note:** `JOBS_ROOT` is always passed explicitly by the orchestrator in the dispatch prompt. Never resolve it yourself — do not fall back to any hardcoded path.
 ## Purpose
-Sub-agent responsible for creating and maintaining structured job documentation in `.metaproject/jobs/`. Called exclusively by `job-orchestrator` to persist the lifecycle of orchestrated tasks — from initial plan through analysis, implementation, review, and final report.
+Sub-agent responsible for creating and maintaining structured job documentation in `<JOBS_ROOT>/`. Called exclusively by `job-orchestrator` to persist the lifecycle of orchestrated tasks — from initial plan through analysis, implementation, review, and final report.
 **This skill is NOT invoked directly by users.** It is a service skill dispatched by the orchestrator.
@@ -43,7 +52,7 @@ The orchestrator provides a structured prompt with the following fields:
 ```
 ACTION:    init | add-document | update-readme | finalize
 JOB_NAME:  <kebab-case folder name>
-JOBS_ROOT: .metaproject/jobs
+JOBS_ROOT: <JOBS_ROOT>
 DATA:      <action-specific payload — see below>
 ```
@@ -150,7 +159,7 @@ PLAN:        <ordered list of planned steps>
    DOCUMENTER_RESULT:
      action: init
      status: success | error
-     job_path: .metaproject/jobs/<JOB_NAME>
+     job_path: <JOBS_ROOT>/<JOB_NAME>
      files_created: [README.md, man/plan.md, ai/plan.md]
      error_details: <if status is error>
    ```
@@ -299,7 +308,7 @@ SUMMARY:       <1-3 sentence summary of what was accomplished>
    DOCUMENTER_RESULT:
      action: finalize
      status: success | error
-     job_path: .metaproject/jobs/<JOB_NAME>
+     job_path: <JOBS_ROOT>/<JOB_NAME>
      final_status: <FINAL_STATUS>
      total_documents: <count of all files in man/ + ai/>
      verification: passed | <list of discrepancies>
@@ -336,12 +345,12 @@ When the orchestrator dispatches this skill as a sub-agent, it should use this p
 ```
 You are the job-documenter agent. Your task is to manage job documentation.
-Load the skill from: skills/job-documenter/SKILL.md
+Load the skill from: skills/orchestration/job-documenter/SKILL.md
 Follow the rules from: rules/core/jobs-documentation.mdc
 ACTION: <action>
 JOB_NAME: <job-name>
-JOBS_ROOT: .metaproject/jobs
+JOBS_ROOT: <JOBS_ROOT>
 DATA:
 <action-specific data>