@mrciphersmith/keryx 0.2.97 → 0.2.98

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

@@ -12,8 +12,8 @@ triggers:
 metadata:
   author: "MrCipherSmith"
   version: "2.4.0"
-  category: "analysis"
-  compatible_harnesses: "cursor,codex,zed,opencode"
+  category: "orchestration"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
 ---
 
@@ -275,7 +275,7 @@ When focus specified: boost files matching focus keywords to P0; select ALL focu
 1. **Dependency search**: find all target files importing changed DTOs/APIs from source
 2. **Contract divergence**: compare new source contracts with current target implementation
 3. **Target deep dive**: read 2-3 key components that will need changes
-4. **Target rules compliance**: check `.cursor/rules/core/*.mdc` in target repo
+4. **Target rules compliance**: check `.metaproject/rules/core/*.mdc` in target repo
 
 ---
 
@@ -333,24 +333,14 @@ Wait for user confirmation before generating full report.
 ### Output Structure
 
 ```
-<DOCS_ROOT>/analysis/<feature-name>-<YYYY-MM-DD>/
-├── README.md                    # Index and navigation
-├── report/
-│   ├── en/report.md             # English for humans
-│   ├── ru/report.md             # Russian for humans
-│   └── ai/report.md             # Structured for AI agents (EN)
-├── plans/
-│   ├── en/implementation-plan.md
-│   ├── ru/implementation-plan.md
-│   └── ai/implementation-plan.md
-├── contracts/
-│   ├── api-changes.md           # API contract diff
-│   └── dto-comparison.md        # Before/after DTOs
-└── metrics/
-    └── analysis-metrics.md      # Analysis metadata
+<DOCS_ROOT>/analysis/<feature-name>/
+├── report.md                    # Findings, API contract diff, DTO comparison, cross-repo impact, analysis metrics
+└── implementation-plan.md       # Actionable implementation plan derived from the analysis
 ```
 
-The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
+No date-stamped folder: update `report.md`/`implementation-plan.md` in place for a rerun on the same feature rather than creating a parallel copy. Default output is a single English (`en`) pair. Add other language variants only if the user explicitly asks for them, and keep any variants you create synchronized.
+
+`report.md` should use Gherkin-style scenarios where they make findings easier for other AI agents to parse.
 > For full Gherkin output format and syntax rules, see `SKILL.detail.md`.
 
 ---
@@ -360,7 +350,7 @@ The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
 - Every claim MUST reference specific code: `[filename.ts:L123](file:///absolute/path#L123)`
 - Minimum 3 code examples per report
 - Mermaid diagrams for architecture, tables for DTO changes, flowcharts for data flow
-- Multi-language: `en/` for humans, `ru/` for humans, `ai/` for AI agents
+- Default to a single `en` document; add `ru`/`ai` (or other) variants only when the user explicitly asks, keeping them synchronized
 
 ---
 
@@ -378,7 +368,7 @@ The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
 
 ## Step 13: Analysis Metrics
 
-Track and include in `metrics/analysis-metrics.md`:
+Track and include in the `## Analysis Metrics` section of `report.md`:
 - Duration, files analyzed (P0/P1/P2), lines changed
 - Cross-repo dependencies, API endpoints changed, DTOs modified
 - Breaking changes count, test coverage %, risk level
@@ -415,7 +405,7 @@ Follow `documentation-management.mdc`: update `<DOCS_ROOT>/readme.md`, add entry
 4. **Never assume** — ask user when unclear
 5. **Never skip** intermediate review for complex analyses (P0 files > 3)
 6. **Always provide** concrete, actionable recommendations
-7. **Always include** both human-readable and AI-readable formats
+7. **Always default** to a single-language document (`en`); add other language variants only when the user explicitly asks
 
 ---
 

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

@@ -224,26 +224,16 @@ grep -r "focus_keyword" --include="*.spec.ts" --include="*.test.ts" src/
 
 ### Output for Mode B
 
-Generate **Feature Specification Document** instead of Change Analysis:
-
-```
-<DOCS_ROOT>/analysis/<feature>-current-state-<date>/
-├── README.md
-├── specification/
-│   ├── en/feature-specification.md
-│   ├── ru/feature-specification.md
-│   └── ai/feature-specification.md
-├── architecture/
-│   ├── data-flow.md
-│   ├── component-diagram.md
-│   └── api-contracts.md
-├── usage/
-│   ├── examples.md
-│   └── patterns.md
-└── tests/
-    └── test-coverage.md
+Generate **Feature Specification Document** instead of Change Analysis, using the same flat analysis-category layout as Mode A:
+
+```
+<DOCS_ROOT>/analysis/<feature-name>/
+├── report.md                    # Feature specification: purpose, API contracts, business logic, data flow, architecture, usage examples, test coverage
+└── implementation-plan.md       # Only if formalization surfaces follow-up implementation work
 ```
 
+No date-stamped folder, no `-current-state-<date>` suffix, and no mandatory `en`/`ru`/`ai` split — add language variants only if the user explicitly asks.
+
 ---
 
 ## Timeouts and Limits
@@ -397,7 +387,7 @@ Analyzing only new changes...
       "branch": "feature-name",
       "sha": "abc123",
       "base_sha": "def456",
-      "path": "feature-name-2024-01-15",
+      "path": "feature-name",
       "created_at": "2024-01-15T10:00:00Z",
       "updated_at": "2024-01-15T10:00:00Z",
       "status": "complete",
@@ -526,7 +516,7 @@ git log --oneline "${BASE_SHA}..HEAD"
 
 ## Step 10: Gherkin Output Format (Full)
 
-The AI-readable format in `report/ai/report.md` and `plans/ai/implementation-plan.md` uses Gherkin-style scenarios.
+Gherkin-style scenarios in `report.md` (and its `ai` language variant, when one is generated) make analysis results parseable by other AI agents. The same applies to `implementation-plan.md` for Phase scenarios.
 
 **Purpose**: Enable other AI agents to parse analysis results programmatically.
 
@@ -633,7 +623,7 @@ Feature: [Concise Feature Name]
     And the risk level is "[Low/Medium/High]"
 ```
 
-### 7. Implementation Plan (in plans/ai/)
+### 7. Implementation Plan (in implementation-plan.md)
 ```gherkin
 Feature: Implementation Plan for [Feature Name]
   Background:
@@ -711,7 +701,7 @@ Feature: Implementation Plan for [Feature Name]
 
 ## Step 13: Full Metrics and Complexity Score
 
-Track and report in `metrics/analysis-metrics.md`:
+Track and report in the `## Analysis Metrics` section of `report.md`:
 
 ```markdown
 ## Analysis Metrics

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

@@ -12,8 +12,8 @@ triggers:
 metadata:
   author: "MrCipherSmith"
   version: "2.4.0"
-  category: "analysis"
-  compatible_harnesses: "cursor,codex,zed,opencode"
+  category: "orchestration"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
 ---
 
@@ -275,7 +275,7 @@ When focus specified: boost files matching focus keywords to P0; select ALL focu
 1. **Dependency search**: find all target files importing changed DTOs/APIs from source
 2. **Contract divergence**: compare new source contracts with current target implementation
 3. **Target deep dive**: read 2-3 key components that will need changes
-4. **Target rules compliance**: check `.cursor/rules/core/*.mdc` in target repo
+4. **Target rules compliance**: check `.metaproject/rules/core/*.mdc` in target repo
 
 ---
 
@@ -333,24 +333,14 @@ Wait for user confirmation before generating full report.
 ### Output Structure
 
 ```
-<DOCS_ROOT>/analysis/<feature-name>-<YYYY-MM-DD>/
-├── README.md                    # Index and navigation
-├── report/
-│   ├── en/report.md             # English for humans
-│   ├── ru/report.md             # Russian for humans
-│   └── ai/report.md             # Structured for AI agents (EN)
-├── plans/
-│   ├── en/implementation-plan.md
-│   ├── ru/implementation-plan.md
-│   └── ai/implementation-plan.md
-├── contracts/
-│   ├── api-changes.md           # API contract diff
-│   └── dto-comparison.md        # Before/after DTOs
-└── metrics/
-    └── analysis-metrics.md      # Analysis metadata
+<DOCS_ROOT>/analysis/<feature-name>/
+├── report.md                    # Findings, API contract diff, DTO comparison, cross-repo impact, analysis metrics
+└── implementation-plan.md       # Actionable implementation plan derived from the analysis
 ```
 
-The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
+No date-stamped folder: update `report.md`/`implementation-plan.md` in place for a rerun on the same feature rather than creating a parallel copy. Default output is a single English (`en`) pair. Add other language variants only if the user explicitly asks for them, and keep any variants you create synchronized.
+
+`report.md` should use Gherkin-style scenarios where they make findings easier for other AI agents to parse.
 > For full Gherkin output format and syntax rules, see `SKILL.detail.md`.
 
 ---
@@ -360,7 +350,7 @@ The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
 - Every claim MUST reference specific code: `[filename.ts:L123](file:///absolute/path#L123)`
 - Minimum 3 code examples per report
 - Mermaid diagrams for architecture, tables for DTO changes, flowcharts for data flow
-- Multi-language: `en/` for humans, `ru/` for humans, `ai/` for AI agents
+- Default to a single `en` document; add `ru`/`ai` (or other) variants only when the user explicitly asks, keeping them synchronized
 
 ---
 
@@ -378,7 +368,7 @@ The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
 
 ## Step 13: Analysis Metrics
 
-Track and include in `metrics/analysis-metrics.md`:
+Track and include in the `## Analysis Metrics` section of `report.md`:
 - Duration, files analyzed (P0/P1/P2), lines changed
 - Cross-repo dependencies, API endpoints changed, DTOs modified
 - Breaking changes count, test coverage %, risk level
@@ -415,7 +405,7 @@ Follow `documentation-management.mdc`: update `<DOCS_ROOT>/readme.md`, add entry
 4. **Never assume** — ask user when unclear
 5. **Never skip** intermediate review for complex analyses (P0 files > 3)
 6. **Always provide** concrete, actionable recommendations
-7. **Always include** both human-readable and AI-readable formats
+7. **Always default** to a single-language document (`en`); add other language variants only when the user explicitly asks
 
 ---
 

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

@@ -12,8 +12,8 @@ triggers:
 metadata:
   author: "MrCipherSmith"
   version: "2.4.0"
-  category: "analysis"
-  compatible_harnesses: "cursor,codex,zed,opencode"
+  category: "orchestration"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
 ---
 
@@ -275,7 +275,7 @@ When focus specified: boost files matching focus keywords to P0; select ALL focu
 1. **Dependency search**: find all target files importing changed DTOs/APIs from source
 2. **Contract divergence**: compare new source contracts with current target implementation
 3. **Target deep dive**: read 2-3 key components that will need changes
-4. **Target rules compliance**: check `.cursor/rules/core/*.mdc` in target repo
+4. **Target rules compliance**: check `.metaproject/rules/core/*.mdc` in target repo
 
 ---
 
@@ -333,24 +333,14 @@ Wait for user confirmation before generating full report.
 ### Output Structure
 
 ```
-<DOCS_ROOT>/analysis/<feature-name>-<YYYY-MM-DD>/
-├── README.md                    # Index and navigation
-├── report/
-│   ├── en/report.md             # English for humans
-│   ├── ru/report.md             # Russian for humans
-│   └── ai/report.md             # Structured for AI agents (EN)
-├── plans/
-│   ├── en/implementation-plan.md
-│   ├── ru/implementation-plan.md
-│   └── ai/implementation-plan.md
-├── contracts/
-│   ├── api-changes.md           # API contract diff
-│   └── dto-comparison.md        # Before/after DTOs
-└── metrics/
-    └── analysis-metrics.md      # Analysis metadata
+<DOCS_ROOT>/analysis/<feature-name>/
+├── report.md                    # Findings, API contract diff, DTO comparison, cross-repo impact, analysis metrics
+└── implementation-plan.md       # Actionable implementation plan derived from the analysis
 ```
 
-The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
+No date-stamped folder: update `report.md`/`implementation-plan.md` in place for a rerun on the same feature rather than creating a parallel copy. Default output is a single English (`en`) pair. Add other language variants only if the user explicitly asks for them, and keep any variants you create synchronized.
+
+`report.md` should use Gherkin-style scenarios where they make findings easier for other AI agents to parse.
 > For full Gherkin output format and syntax rules, see `SKILL.detail.md`.
 
 ---
@@ -360,7 +350,7 @@ The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
 - Every claim MUST reference specific code: `[filename.ts:L123](file:///absolute/path#L123)`
 - Minimum 3 code examples per report
 - Mermaid diagrams for architecture, tables for DTO changes, flowcharts for data flow
-- Multi-language: `en/` for humans, `ru/` for humans, `ai/` for AI agents
+- Default to a single `en` document; add `ru`/`ai` (or other) variants only when the user explicitly asks, keeping them synchronized
 
 ---
 
@@ -378,7 +368,7 @@ The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
 
 ## Step 13: Analysis Metrics
 
-Track and include in `metrics/analysis-metrics.md`:
+Track and include in the `## Analysis Metrics` section of `report.md`:
 - Duration, files analyzed (P0/P1/P2), lines changed
 - Cross-repo dependencies, API endpoints changed, DTOs modified
 - Breaking changes count, test coverage %, risk level
@@ -415,7 +405,7 @@ Follow `documentation-management.mdc`: update `<DOCS_ROOT>/readme.md`, add entry
 4. **Never assume** — ask user when unclear
 5. **Never skip** intermediate review for complex analyses (P0 files > 3)
 6. **Always provide** concrete, actionable recommendations
-7. **Always include** both human-readable and AI-readable formats
+7. **Always default** to a single-language document (`en`); add other language variants only when the user explicitly asks
 
 ---
 

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

@@ -12,8 +12,8 @@ triggers:
 metadata:
   author: "MrCipherSmith"
   version: "2.4.0"
-  category: "analysis"
-  compatible_harnesses: "cursor,codex,zed,opencode"
+  category: "orchestration"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
 ---
 
@@ -275,7 +275,7 @@ When focus specified: boost files matching focus keywords to P0; select ALL focu
 1. **Dependency search**: find all target files importing changed DTOs/APIs from source
 2. **Contract divergence**: compare new source contracts with current target implementation
 3. **Target deep dive**: read 2-3 key components that will need changes
-4. **Target rules compliance**: check `.cursor/rules/core/*.mdc` in target repo
+4. **Target rules compliance**: check `.metaproject/rules/core/*.mdc` in target repo
 
 ---
 
@@ -333,24 +333,14 @@ Wait for user confirmation before generating full report.
 ### Output Structure
 
 ```
-<DOCS_ROOT>/analysis/<feature-name>-<YYYY-MM-DD>/
-├── README.md                    # Index and navigation
-├── report/
-│   ├── en/report.md             # English for humans
-│   ├── ru/report.md             # Russian for humans
-│   └── ai/report.md             # Structured for AI agents (EN)
-├── plans/
-│   ├── en/implementation-plan.md
-│   ├── ru/implementation-plan.md
-│   └── ai/implementation-plan.md
-├── contracts/
-│   ├── api-changes.md           # API contract diff
-│   └── dto-comparison.md        # Before/after DTOs
-└── metrics/
-    └── analysis-metrics.md      # Analysis metadata
+<DOCS_ROOT>/analysis/<feature-name>/
+├── report.md                    # Findings, API contract diff, DTO comparison, cross-repo impact, analysis metrics
+└── implementation-plan.md       # Actionable implementation plan derived from the analysis
 ```
 
-The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
+No date-stamped folder: update `report.md`/`implementation-plan.md` in place for a rerun on the same feature rather than creating a parallel copy. Default output is a single English (`en`) pair. Add other language variants only if the user explicitly asks for them, and keep any variants you create synchronized.
+
+`report.md` should use Gherkin-style scenarios where they make findings easier for other AI agents to parse.
 > For full Gherkin output format and syntax rules, see `SKILL.detail.md`.
 
 ---
@@ -360,7 +350,7 @@ The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
 - Every claim MUST reference specific code: `[filename.ts:L123](file:///absolute/path#L123)`
 - Minimum 3 code examples per report
 - Mermaid diagrams for architecture, tables for DTO changes, flowcharts for data flow
-- Multi-language: `en/` for humans, `ru/` for humans, `ai/` for AI agents
+- Default to a single `en` document; add `ru`/`ai` (or other) variants only when the user explicitly asks, keeping them synchronized
 
 ---
 
@@ -378,7 +368,7 @@ The AI-readable format (`report/ai/`, `plans/ai/`) uses Gherkin-style scenarios.
 
 ## Step 13: Analysis Metrics
 
-Track and include in `metrics/analysis-metrics.md`:
+Track and include in the `## Analysis Metrics` section of `report.md`:
 - Duration, files analyzed (P0/P1/P2), lines changed
 - Cross-repo dependencies, API endpoints changed, DTOs modified
 - Breaking changes count, test coverage %, risk level
@@ -415,7 +405,7 @@ Follow `documentation-management.mdc`: update `<DOCS_ROOT>/readme.md`, add entry
 4. **Never assume** — ask user when unclear
 5. **Never skip** intermediate review for complex analyses (P0 files > 3)
 6. **Always provide** concrete, actionable recommendations
-7. **Always include** both human-readable and AI-readable formats
+7. **Always default** to a single-language document (`en`); add other language variants only when the user explicitly asks
 
 ---
 

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

@@ -57,6 +57,6 @@
 | Field | Value |
 |-------|-------|
 | Base Dir | `.metaproject/jobs/<job-name>/ai/analysis` |
-| Folder Name | `async-search-current-state` |
-| Languages | `en, ru, ai` |
+| Folder Name | `async-search` |
+| Languages | `en` |
 | Include Metrics | `true` |

package/src/gdskills/bundled/skills/orchestration/feature-analyzer/analysis-request.template.md

@@ -75,5 +75,5 @@
 |-------|-------|
 | Base Dir | `<DOCS_ROOT>/analysis` |
 | Folder Name | |
-| Languages | `en, ru, ai` |
+| Languages | `en` |
 | Include Metrics | `true` |

package/src/gdskills/bundled/skills/orchestration/feature-analyzer/input-contract.schema.json

@@ -225,7 +225,7 @@
         },
         "folder_name": {
           "type": "string",
-          "description": "Custom folder name. Defaults to <feature>-<date> for Mode A, <feature>-current-state-<date> for Mode B"
+          "description": "Custom folder name. Defaults to <feature-name> (no date suffix) for both Mode A and Mode B"
         },
         "languages": {
           "type": "array",
@@ -233,13 +233,13 @@
             "type": "string",
             "enum": ["en", "ru", "ai"]
           },
-          "default": ["en", "ru", "ai"],
-          "description": "Which report languages to generate. ai = Gherkin format for AI agents"
+          "default": ["en"],
+          "description": "Which report languages to generate. Defaults to a single 'en' document; add 'ru'/'ai' only when the user explicitly asks for them. ai = Gherkin format for AI agents"
         },
         "include_metrics": {
           "type": "boolean",
           "default": true,
-          "description": "Include analysis-metrics.md in output"
+          "description": "Include an Analysis Metrics section in report.md"
         }
       }
     }

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

@@ -19,7 +19,7 @@
                     ↓
   [Субагент]     → выполняет SKILL.md feature-analyzer автономно
                     ↓
-  [Результат]    → docs/analysis/<feature>-<date>/
+  [Результат]    → docs/analysis/<feature>/
 -->
 
 ## Инструкция для оркестратора
@@ -211,7 +211,7 @@ TICKET REFERENCE:
 
 Base directory: {{output.base_dir | default("<DOCS_ROOT>/analysis")}}
 Folder name:    {{output.folder_name | default("auto-generated per SKILL.md rules")}}
-Languages:      {{output.languages | default("en, ru, ai")}}
+Languages:      {{output.languages | default("en")}}
 Include metrics: {{output.include_metrics | default("true")}}
 
 ═══════════════════════════════════════════════

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

@@ -10,7 +10,7 @@ triggers:
 metadata:
   author: "MrCipherSmith"
   version: "2.0.0"
-  category: "workflow"
+  category: "orchestration"
   compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
 ---
@@ -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/orchestration/code-verifier/SKILL.md
+Invoke: .metaproject/skills/gdskills/orchestration/code-verifier/SKILL.md
 Input:  codebase_path=<project_root>, scope=changed, base_branch=<base>
 ```
 

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

@@ -10,7 +10,7 @@ triggers:
 metadata:
   author: "MrCipherSmith"
   version: "2.0.0"
-  category: "workflow"
+  category: "orchestration"
   compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
 ---
@@ -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/orchestration/code-verifier/SKILL.md
+Invoke: .metaproject/skills/gdskills/orchestration/code-verifier/SKILL.md
 Input:  codebase_path=<project_root>, scope=changed, base_branch=<base>
 ```
 

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

@@ -10,7 +10,7 @@ triggers:
 metadata:
   author: "MrCipherSmith"
   version: "2.0.0"
-  category: "workflow"
+  category: "orchestration"
   compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
 ---
@@ -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/orchestration/code-verifier/SKILL.md
+Invoke: .metaproject/skills/gdskills/orchestration/code-verifier/SKILL.md
 Input:  codebase_path=<project_root>, scope=changed, base_branch=<base>
 ```
 

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

@@ -231,6 +231,7 @@ Required rules:
 - `.metaproject/rules/core/error-handling.mdc`
 - `.metaproject/rules/core/implementation-doc-mandate.mdc`
 - `.metaproject/rules/core/execution-metrics.md`
+- `.metaproject/rules/core/git-concurrency.mdc` — no `git stash`, no unscoped `git add`, pin every dispatch to its worktree
 
 Execution metrics (opt-in): when a USER runs this orchestrator directly, at the
 start ask "Collect execution statistics for this run? (yes/no)" per
@@ -320,6 +321,19 @@ worker reply is a `subagent-result` object
 line is `STATUS: <status>`
 (`.metaproject/rules/core/subagent-status-protocol.md`).
 
+`<worktree_path>` below is the absolute root of the checkout this flow's work
+happens in: the git worktree the flow runs in, or the project root when it runs
+in the main checkout. Resolve it once, before the first dispatch
+(`git rev-parse --show-toplevel` from that checkout), check
+`git -C <worktree_path> branch --show-current` is the branch the work belongs
+on, and pin every dispatch to it (`rules/core/git-concurrency.mdc`, "Pinning A
+Dispatch To Its Worktree").
+
+Workers do not commit: flow-orchestrator owns every commit and dispatches with
+auto-commit off (task-implementer's `automation.auto_commit: false`). A
+`subagent-dispatch` has no `automation` field, so the setting travels as the
+explicit constraint below — never as the worker's default, which is `true`.
+
 Dispatch payload, bound to the flow (map `target_skill` from the routing table):
 
 ```json
@@ -340,7 +354,10 @@ Dispatch payload, bound to the flow (map `target_skill` from the routing table):
   "constraints": [
     "Never edit flow.json.",
     "Never edit frozen acceptance criteria.",
-    "Return a subagent-result; first line must be STATUS:."
+    "Return a subagent-result; first line must be STATUS:.",
+    "Follow rules/core/git-concurrency.mdc: never git stash; never git add -A.",
+    "Root: <worktree_path>. Before the first write run `cd <worktree_path> && pwd && git branch --show-current`; run every git command as `git -C <worktree_path>`.",
+    "Auto-commit is off (automation.auto_commit: false): do not commit; list every path you changed in changed_files. flow-orchestrator commits them at the task boundary."
   ],
   "allowed_actions": ["read", "write", "run-command", "git"],
   "output_contract": { "schema": "subagent-result", "artifact_path": ".metaproject/flows/<dir>/journal.md" },
@@ -349,12 +366,37 @@ Dispatch payload, bound to the flow (map `target_skill` from the routing table):
 }
 ```
 
-After a worker succeeds, the flow-orchestrator marks task progress:
+**Task boundary commit, after every accepted worker result** (`DONE` or
+`DONE_WITH_CONCERNS`), then mark task progress. It commits exactly those
+`changed_files` from the worker's `subagent-result` that git still shows as
+changed, never `-A`/`--all`/`.` (`rules/core/git-concurrency.mdc` rule 4 and
+"Reporting Back"). It skips cleanly when none remain. That is expected, not an
+error, for a worker that reported no files (review, context, docs) or that
+committed on its own (tests-creator's stubs):
 
 ```bash
+set -- <each changed_files path, single-quoted: 'src/a.ts' 'docs/b c.md'>   # may be none; an unquoted path with a space splits and is skipped
+PENDING=()
+for p in "$@"; do
+  [ -n "$(git -C <worktree_path> status --porcelain -- "$p")" ] && PENDING+=("$p")
+done
+if [ ${#PENDING[@]} -eq 0 ]; then
+  echo "boundary commit: nothing left to commit, skipped"
+else
+  git -C <worktree_path> add -- "${PENDING[@]}"
+  git -C <worktree_path> commit -m "<type>(<scope>): <Tn title>
+
+task: <Tn>" -- "${PENDING[@]}"
+fi
 keryx flow task done <id> <Tn>
 ```
 
+Why each path is checked on its own: `git status --porcelain --` with no path
+lists the whole tree, `git add` fails on a path that is neither on disk nor
+tracked, and `git commit` with nothing staged exits 1. The trailing
+`-- "${PENDING[@]}"` commits only these paths, so a file another lane staged is
+not swept into this commit.
+
 If new work is discovered:
 
 ```bash
@@ -369,8 +411,8 @@ properly formatted `subagent-result`.
 
 | Worker `status` | flow-orchestrator action |
 |---|---|
-| `DONE` | Accept. `keryx flow task done <id> <Tn>`. Continue. |
-| `DONE_WITH_CONCERNS` | Accept, record every concern in `journal.md`, decide continue vs. add a fix task, then `flow task done`. Never silently drop concerns. |
+| `DONE` | Accept, run the task boundary commit (above), `keryx flow task done <id> <Tn>`. Continue. |
+| `DONE_WITH_CONCERNS` | Accept, run the task boundary commit (above), record every concern in `journal.md`, decide continue vs. add a fix task, then `flow task done`. Never silently drop concerns. |
 | `NEEDS_CONTEXT` | Do not fail. Enrich `context_refs`/`files_to_read` from gdgraph/gdctx/wiki/memory, then re-dispatch the same `dispatch_id`. |
 | `BLOCKED` | `keryx flow block <id> --reason "<worker reason>"`; resolve or escalate one concise question, then `flow unblock` and re-dispatch. |
 | `FAILED` | Emitted by harness **child** workers (`src/harness/child/contract.ts`), never by skill workers — `task-implementer` maps its own `failed` onto `BLOCKED`. Retry once with the same dispatch. If it fails again, block the flow and surface the error to the user. |

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

@@ -10,9 +10,9 @@ triggers:
 metadata:
   author: "MrCipherSmith"
   version: "1.1.0"
-  category: "analysis"
+  category: "orchestration"
   agent_worthy: true
-  compatible_harnesses: "cursor,codex,zed,opencode"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
 ---
 

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

@@ -10,9 +10,9 @@ triggers:
 metadata:
   author: "MrCipherSmith"
   version: "1.1.0"
-  category: "analysis"
+  category: "orchestration"
   agent_worthy: true
-  compatible_harnesses: "cursor,codex,zed,opencode"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
 ---
 

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

@@ -10,9 +10,9 @@ triggers:
 metadata:
   author: "MrCipherSmith"
   version: "1.1.0"
-  category: "analysis"
+  category: "orchestration"
   agent_worthy: true
-  compatible_harnesses: "cursor,codex,zed,opencode"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
 ---
 

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

@@ -10,9 +10,9 @@ triggers:
 metadata:
   author: "MrCipherSmith"
   version: "1.1.0"
-  category: "analysis"
+  category: "orchestration"
   agent_worthy: true
-  compatible_harnesses: "cursor,codex,zed,opencode"
+  compatible_harnesses: "cursor,codex,zed,opencode,claude"
 license: "MIT"
 ---