@mrciphersmith/keryx 0.2.70 → 0.2.72

package/src/gdskills/bundled/skills/orchestration/context-collector/SKILL.codex.md

@@ -13,8 +13,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "context"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Context Collector
@@ -512,7 +512,7 @@ When the orchestrator dispatches this skill as a sub-agent:
 You are the context-collector agent. Your task is to research and build
 a context document for the current job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 ACTION: collect
 JOB_NAME: <job-name>
@@ -534,7 +534,7 @@ For updates:
 You are the context-collector agent. Your task is to update the existing
 context document for this job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 ACTION: update
 JOB_NAME: <job-name>

package/src/gdskills/bundled/skills/orchestration/context-collector/SKILL.cursor.md

@@ -13,8 +13,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "context"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Context Collector
@@ -512,7 +512,7 @@ When the orchestrator dispatches this skill as a sub-agent:
 You are the context-collector agent. Your task is to research and build
 a context document for the current job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 ACTION: collect
 JOB_NAME: <job-name>
@@ -534,7 +534,7 @@ For updates:
 You are the context-collector agent. Your task is to update the existing
 context document for this job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 ACTION: update
 JOB_NAME: <job-name>

package/src/gdskills/bundled/skills/orchestration/context-collector/SKILL.md

@@ -14,8 +14,8 @@ metadata:
   version: "1.1.0"
   category: "context"
   agent_worthy: true
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 <SUBAGENT-STOP>
@@ -600,7 +600,7 @@ When the orchestrator dispatches this skill as a sub-agent:
 You are the context-collector agent. Your task is to research and build
 a context document for the current job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 ACTION: collect
 JOB_NAME: <job-name>
@@ -622,7 +622,7 @@ For updates:
 You are the context-collector agent. Your task is to update the existing
 context document for this job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 ACTION: update
 JOB_NAME: <job-name>

package/src/gdskills/bundled/skills/orchestration/context-collector/SKILL.opencode.md

@@ -13,8 +13,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "context"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Context Collector
@@ -512,7 +512,7 @@ When the orchestrator dispatches this skill as a sub-agent:
 You are the context-collector agent. Your task is to research and build
 a context document for the current job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 ACTION: collect
 JOB_NAME: <job-name>
@@ -534,7 +534,7 @@ For updates:
 You are the context-collector agent. Your task is to update the existing
 context document for this job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 ACTION: update
 JOB_NAME: <job-name>

package/src/gdskills/bundled/skills/orchestration/context-collector/SKILL.zed.md

@@ -13,8 +13,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "context"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Context Collector
@@ -512,7 +512,7 @@ When the orchestrator dispatches this skill as a sub-agent:
 You are the context-collector agent. Your task is to research and build
 a context document for the current job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 ACTION: collect
 JOB_NAME: <job-name>
@@ -534,7 +534,7 @@ For updates:
 You are the context-collector agent. Your task is to update the existing
 context document for this job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 ACTION: update
 JOB_NAME: <job-name>

package/src/gdskills/bundled/skills/orchestration/context-collector/orchestrator-prompt.md

@@ -58,7 +58,7 @@ IF ACTION == "update":
 You are the context-collector agent. Your task is to research and build
 a context document for the current job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 DO NOT ask the user any questions. Execute all phases autonomously.
 
@@ -85,7 +85,7 @@ and return a CONTEXT_RESULT block as your final message.
 You are the context-collector agent. Your task is to update the existing
 context document for this job.
 
-Load the skill from: skills/context-collector/SKILL.md
+Load the skill from: skills/orchestration/context-collector/SKILL.md
 
 DO NOT ask the user any questions. Execute the update flow autonomously.
 

package/src/gdskills/bundled/skills/orchestration/feature-analyzer/SKILL.codex.md

@@ -13,8 +13,8 @@ metadata:
   author: "MrCipherSmith"
   version: "2.4.0"
   category: "analysis"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Feature Analyzer
@@ -996,9 +996,9 @@ For UI changes, use Playwright/Storybook (see AGENTS.md for available tools):
 **Leverage other skills via AGENTS.md catalog:**
 
 Before finalizing analysis, consider running:
-- `skills/code-style-review` - if architecture changes detected
-- `skills/code-ai-review` - for self-validation of findings
-- `skills/code-mobx-store-review` - if store changes found
+- `skills/review/code-style-review` - if architecture changes detected
+- `skills/review/code-ai-review` - for self-validation of findings
+- `skills/review/code-mobx-store-review` - if store changes found
 
 **How to invoke:**
 1. Reference `AGENTS.md` Skills Catalog

package/src/gdskills/bundled/skills/orchestration/feature-analyzer/SKILL.cursor.md

@@ -13,8 +13,8 @@ metadata:
   author: "MrCipherSmith"
   version: "2.4.0"
   category: "analysis"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Feature Analyzer
@@ -996,9 +996,9 @@ For UI changes, use Playwright/Storybook (see AGENTS.md for available tools):
 **Leverage other skills via AGENTS.md catalog:**
 
 Before finalizing analysis, consider running:
-- `skills/code-style-review` - if architecture changes detected
-- `skills/code-ai-review` - for self-validation of findings
-- `skills/code-mobx-store-review` - if store changes found
+- `skills/review/code-style-review` - if architecture changes detected
+- `skills/review/code-ai-review` - for self-validation of findings
+- `skills/review/code-mobx-store-review` - if store changes found
 
 **How to invoke:**
 1. Reference `AGENTS.md` Skills Catalog

package/src/gdskills/bundled/skills/orchestration/feature-analyzer/SKILL.md

@@ -13,8 +13,8 @@ metadata:
   author: "MrCipherSmith"
   version: "2.4.0"
   category: "analysis"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 <SUBAGENT-STOP>
@@ -322,9 +322,9 @@ Check `AGENTS.md` for available tools (`playwright-testing.mdc`, `storybook-guid
 ## Step 8: Integration with Other Skills
 
 Before finalizing, consider running:
-- `skills/code-style-review` — if architecture changes detected
-- `skills/code-ai-review` — for self-validation of findings
-- `skills/code-mobx-store-review` — if store changes found
+- `skills/review/code-style-review` — if architecture changes detected
+- `skills/review/code-ai-review` — for self-validation of findings
+- `skills/review/code-mobx-store-review` — if store changes found
 
 ---
 

package/src/gdskills/bundled/skills/orchestration/feature-analyzer/SKILL.opencode.md

@@ -13,8 +13,8 @@ metadata:
   author: "MrCipherSmith"
   version: "2.4.0"
   category: "analysis"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Feature Analyzer
@@ -996,9 +996,9 @@ For UI changes, use Playwright/Storybook (see AGENTS.md for available tools):
 **Leverage other skills via AGENTS.md catalog:**
 
 Before finalizing analysis, consider running:
-- `skills/code-style-review` - if architecture changes detected
-- `skills/code-ai-review` - for self-validation of findings
-- `skills/code-mobx-store-review` - if store changes found
+- `skills/review/code-style-review` - if architecture changes detected
+- `skills/review/code-ai-review` - for self-validation of findings
+- `skills/review/code-mobx-store-review` - if store changes found
 
 **How to invoke:**
 1. Reference `AGENTS.md` Skills Catalog

package/src/gdskills/bundled/skills/orchestration/feature-analyzer/SKILL.zed.md

@@ -13,8 +13,8 @@ metadata:
   author: "MrCipherSmith"
   version: "2.4.0"
   category: "analysis"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Feature Analyzer
@@ -996,9 +996,9 @@ For UI changes, use Playwright/Storybook (see AGENTS.md for available tools):
 **Leverage other skills via AGENTS.md catalog:**
 
 Before finalizing analysis, consider running:
-- `skills/code-style-review` - if architecture changes detected
-- `skills/code-ai-review` - for self-validation of findings
-- `skills/code-mobx-store-review` - if store changes found
+- `skills/review/code-style-review` - if architecture changes detected
+- `skills/review/code-ai-review` - for self-validation of findings
+- `skills/review/code-mobx-store-review` - if store changes found
 
 **How to invoke:**
 1. Reference `AGENTS.md` Skills Catalog

package/src/gdskills/bundled/skills/orchestration/feature-dev/SKILL.codex.md

@@ -11,8 +11,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "workflow"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode,claude"
 ---
 
 # Feature Development (7-Phase)
@@ -70,7 +70,7 @@ End-to-end feature development workflow from idea to merge-ready PR.
 5. Fix failing tests (max 3 attempts per test)
 
 ### Phase 6: REVIEW (Self)
-1. Launch `code-review` skill on own changes (if available)
+1. Launch the `review-orchestrator` skill on own changes
 2. Or run a focused self-review:
    - `git diff main...HEAD` — review the full diff
    - Check for: TODOs left behind, console.logs, hardcoded values

package/src/gdskills/bundled/skills/orchestration/feature-dev/SKILL.cursor.md

@@ -11,8 +11,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "workflow"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode,claude"
 ---
 
 # Feature Development (7-Phase)
@@ -70,7 +70,7 @@ End-to-end feature development workflow from idea to merge-ready PR.
 5. Fix failing tests (max 3 attempts per test)
 
 ### Phase 6: REVIEW (Self)
-1. Launch `code-review` skill on own changes (if available)
+1. Launch the `review-orchestrator` skill on own changes
 2. Or run a focused self-review:
    - `git diff main...HEAD` — review the full diff
    - Check for: TODOs left behind, console.logs, hardcoded values

package/src/gdskills/bundled/skills/orchestration/feature-dev/SKILL.md

@@ -11,8 +11,8 @@ metadata:
   author: "MrCipherSmith"
   version: "2.0.0"
   category: "workflow"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode,claude"
 ---
 
 <SUBAGENT-STOP>
@@ -97,7 +97,7 @@ End-to-end feature development workflow from idea to merge-ready PR.
 Run `code-verifier` on the full diff:
 
 ```
-Invoke: skills/code-verifier/SKILL.md
+Invoke: skills/orchestration/code-verifier/SKILL.md
 Input:  codebase_path=<project_root>, scope=changed, base_branch=<base>
 ```
 
@@ -107,7 +107,7 @@ Input:  codebase_path=<project_root>, scope=changed, base_branch=<base>
 
 ### Phase 7: REVIEW (Self)
 
-1. Launch `code-review` skill on own changes (if available)
+1. Launch the `review-orchestrator` skill on own changes
 2. Or run a focused self-review:
    - `git diff main...HEAD` — review the full diff
    - Check for: TODOs left behind, console.logs, hardcoded values

package/src/gdskills/bundled/skills/orchestration/flow-orchestrator/SKILL.md

@@ -14,8 +14,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.3.0"
   category: "orchestration"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode,claude"
 ---
 
 # Flow Orchestrator
@@ -84,8 +84,8 @@ flowchart TD
   H -- "yes" --> I{"Ask user how to finish"}
   I -- "create PR" --> J["create PR and run review/fix loop"]
   J --> K{"review clean, PR mergeable?"}
-  K -- "no, attempts < 6" --> J
-  K -- "no, attempts = 6" --> R["enrich context and change fix strategy"]
+  K -- "no, attempts < 3" --> J
+  K -- "no, attempts = 3 or repetition detected" --> R["enrich context and change fix strategy"]
   R --> J
   K -- "yes" --> L["merge PR into recorded base branch"]
   L --> M["keryx flow implemented --pr"]
@@ -128,10 +128,21 @@ it already tried. The flow package does.
       ```
 
    5. Apply the Phase 4 attempt budget against the **persisted** count. If
-      `attempts.count` for the task has already reached six, do not re-dispatch
-      the same approach: go to the re-planning step (Phase 4, PR review/fix
-      loop, step 4) and record the decision in `journal.md`.
-   6. If the flow is `blocked`, read the blocking reason from `journal.md`,
+      `attempts.count` for the task has already reached **three**, do not
+      re-dispatch the same approach: go to the re-planning step (Phase 4, PR
+      review/fix loop, step 4) and record the decision in `journal.md`.
+   6. Run the repetition check before spending an attempt, whatever the count
+      says:
+
+      ```bash
+      keryx review loop --flow <id> --task <Tn>
+      ```
+
+      A non-zero exit means the same finding has recurred or two consecutive
+      rounds produced identical output. Go straight to the re-planning step.
+      Do not spend the remaining attempts on the same approach because the
+      budget has some left — that is the failure this check exists to catch.
+   7. If the flow is `blocked`, read the blocking reason from `journal.md`,
       resolve or escalate it, then `keryx flow unblock <id>`.
 4. If the user wants a new flow, continue at 0.1.
 
@@ -231,8 +242,13 @@ did not exist and 24 completed flows shipped with an open task:
   `flow.json`, which `keryx flow init` writes for every flow it creates. A
   package created before the gate landed does not carry the flag, and for it
   the gate reports `skipped` and blocks nothing;
-- a task fails the gate when its status is not `done`, when its disposition is
-  `failed`, or when its disposition is `skipped` with no recorded reason;
+- a task fails the gate when its status is not `done`; when its disposition is
+  `failed`; when its disposition is `blocked` (terminal, but the work did not
+  happen — and the harness emits this disposition on its own for a run that
+  ended blocked); when its disposition is `skipped` with no recorded reason; or
+  when its disposition is a value this build does not recognise. An
+  unrecognised disposition FAILS rather than falling through: a gate whose
+  default for the unknown case is "pass" is not a gate;
 - to close a task as deliberately not needed, record why:
 
   ```bash
@@ -346,15 +362,31 @@ Before accepting implementation:
 1. Run focused tests for touched scope.
 2. Run `code-verifier`.
 3. Run `keryx health run` when Code Health is enabled.
-4. Run `review-orchestrator` with relevant domains.
+4. Check the bounds, then run `review-orchestrator` with relevant domains.
+
+   ```bash
+   keryx review budget --spent <usd-so-far> --outstanding <subagents you already have in flight>
+   ```
+
+   A non-zero exit means the spend ceiling (3 USD by default) has been reached:
+   **stop and ask the user** rather than dispatching another fan-out.
+
+   `--outstanding` is the part that matters here. `review-orchestrator`
+   dispatches reviewers in parallel and runs *nested* under this skill, and
+   keryx cannot observe subagents in another process. Passing the count you
+   already have in flight is the only thing that makes the concurrency cap mean
+   anything across the nesting; omit it and the cap bounds the reviewer fan-out
+   alone, which the review record then states plainly rather than implying
+   otherwise.
+
 5. If findings require code changes, dispatch fix work through `task-implementer`
    and record the fix task in the flow.
 6. Close the skill-learning loop (see `rules/core/skill-lifecycle.mdc`). Collect
    the `skill_drift` fields from task-implementer results and the
    `## Skill Learning` block from review-orchestrator. For each flagged
    project-skill, dispatch a subagent — on a cheaper / non-flagship model if one
-   is available (`.metaproject/scripts/detect-models.sh`; see
-   `rules/core/model-selection.mdc`), otherwise the session model — to run
+   is available (`keryx review tier --findings 1 --diff-lines 0` resolves one from runtime
+   provider detection; see `rules/core/model-selection.mdc`), otherwise the session model — to run
    `keryx skills learn --from-review <report> --skill <m>/<s>` and return the
    proposal. Then read the proposal and `skills learn apply` it, or discard it.
    Never apply unread; never put `learn` in a hook.
@@ -392,18 +424,45 @@ How should this flow end?
    branch state.
 2. If findings or required check failures remain, create or update a flow fix
    task, dispatch `task-implementer`, push the fix, and run review again.
-3. Allow at most six review/fix attempts for the current approach. Count an
-   attempt when review/check results are available, including a clean result,
+3. Allow at most **three** review/fix attempts for the current approach. Count
+   an attempt when review/check results are available, including a clean result,
    and record it with `keryx flow task attempt <id> <Tn> --outcome ...` so the
    count survives a session restart. Read the budget from that task's
    `attempts.count` in `flow.json`, never from this session's memory.
-4. If attempt six is not clean, do not blindly repeat the same loop. Enrich
-   context from the findings, affected graph, relevant wiki, and
-   health/testing artifacts; identify the likely cycle cause; choose a
-   materially different fix strategy or split the work into narrower tasks;
-   record the decision in `journal.md`; then continue with the enriched
-   context.
-5. Never merge while findings or required checks remain unresolved. If the
+
+   Three, and the same three that `task-implementer` and `job-orchestrator`
+   already use. This skill said six, which was an outlier with nothing behind
+   it. The evidence converges on three: *"the first three to four repair
+   iterations account for most achievable gains"*
+   ([arXiv:2607.05197](https://arxiv.org/abs/2607.05197)); correctness falls
+   **0.820 -> 0.673** across two forced revisions while cumulative ever-correct
+   is **0.847** ([arXiv:2607.24604](https://arxiv.org/abs/2607.24604)) — the
+   agent finds the fix and then destroys it, throwing away ~15 points by not
+   stopping. Aider hardcodes `max_reflections = 3`; OpenHands' critic uses 3.
+   Rounds four through six were not buying convergence; they were buying
+   regressions.
+
+4. **Before** spending an attempt, and regardless of how much budget is left,
+   run the repetition check:
+
+   ```bash
+   keryx review loop --flow <id> --task <Tn>
+   ```
+
+   It escalates (non-zero exit) when the same finding recurs in two rounds, or
+   two consecutive rounds produce identical review output. It reads the review
+   packages on disk and the persisted `attempts.count`, not this session's
+   memory, and it deliberately never reads the remaining budget — an agent
+   emitting the identical failing output three times must be caught on the
+   second, not after the budget runs out.
+
+5. If the third attempt is not clean, **or the repetition check escalated
+   earlier**, do not blindly repeat the same loop. Enrich context from the
+   findings, affected graph, relevant wiki, and health/testing artifacts;
+   identify the likely cycle cause; choose a materially different fix strategy
+   or split the work into narrower tasks; record the decision in `journal.md`;
+   then continue with the enriched context.
+6. Never merge while findings or required checks remain unresolved. If the
    re-planned approach still cannot produce a mergeable PR, leave the flow
    `in-progress` and report the blocker instead of forcing completion.
 

package/src/gdskills/bundled/skills/orchestration/issue-analyzer/SKILL.codex.md

@@ -11,8 +11,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "analysis"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Issue Analyzer

package/src/gdskills/bundled/skills/orchestration/issue-analyzer/SKILL.cursor.md

@@ -11,8 +11,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "analysis"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Issue Analyzer

package/src/gdskills/bundled/skills/orchestration/issue-analyzer/SKILL.md

@@ -12,8 +12,8 @@ metadata:
   version: "1.1.0"
   category: "analysis"
   agent_worthy: true
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Issue Analyzer

package/src/gdskills/bundled/skills/orchestration/issue-analyzer/SKILL.opencode.md

@@ -11,8 +11,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "analysis"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Issue Analyzer

package/src/gdskills/bundled/skills/orchestration/issue-analyzer/SKILL.zed.md

@@ -11,8 +11,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "analysis"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Issue Analyzer

package/src/gdskills/bundled/skills/orchestration/job-documenter/SKILL.codex.md

@@ -10,8 +10,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "documentation"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Job Documenter
@@ -336,7 +336,7 @@ 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>

package/src/gdskills/bundled/skills/orchestration/job-documenter/SKILL.cursor.md

@@ -10,8 +10,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "documentation"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Job Documenter
@@ -336,7 +336,7 @@ 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>

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

@@ -1,5 +1,6 @@
 ---
 name: job-documenter
+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"
@@ -10,8 +11,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "documentation"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 <SUBAGENT-STOP>
@@ -344,7 +345,7 @@ 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>

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

@@ -10,8 +10,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "documentation"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Job Documenter
@@ -336,7 +336,7 @@ 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>

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

@@ -10,8 +10,8 @@ metadata:
   author: "MrCipherSmith"
   version: "1.0.0"
   category: "documentation"
+  compatible_harnesses: "cursor,codex,zed,opencode"
 license: "MIT"
-compatibility: "cursor,codex,zed,opencode"
 ---
 
 # Job Documenter
@@ -336,7 +336,7 @@ 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>