@danmoisan/drm-copilot-mcp 0.0.1

package/resources/codex-and-agents-customizations/.agents/skills/feature-promotion-lifecycle/SKILL.md

@@ -0,0 +1,129 @@
+# Converted skill
+
+Applied rewrites:
+- None
+
+---
+name: feature-promotion-lifecycle
+description: Deterministic promotion workflow from potential feature/bug entry to issue, branch, active feature folder, and downstream spec/research handoffs. Agent sessions must use the drmCopilotExtension MCP tool surface and record raw promotion receipts under the canonical checkpoint namespace.
+---
+
+# Feature Promotion Lifecycle
+
+Canonical variable model and MCP-only command sequence for promoting potential feature/bug entries and initializing active feature delivery.
+
+## When to Use This Skill
+
+Use this skill when:
+- A large-scope change requires feature/bug promotion workflow.
+- A short-path workflow still requires promotion/folder initialization before delegated implementation.
+- An orchestrator must create potential docs, promote to issue, branch, and active feature folder.
+- Downstream research/spec agents depend on deterministic paths and identifiers.
+
+## MCP Tool Availability Preflight
+
+Before any promotion step starts, verify that the required `drmCopilotExtension` MCP tools are available in the current agent session.
+
+Required MCP tool set:
+- feature potential entry: `mcp__drmCopilotExtension__new_potential_entry` with `short_name=${short-name}`
+- bug potential entry: `mcp__drmCopilotExtension__new_potential_bug_entry` with `short_name=${short-name}`
+- potential-to-issue promotion: `mcp__drmCopilotExtension__potential_to_issue` with `potential_path=${relativeFile}`, `promotion_type=${promotion-type}`, `work_mode=${work-mode}`
+- active feature folder creation: `mcp__drmCopilotExtension__new_active_feature_folder` with `feature_name=${long-name}`, `type=${promotion-type}`, `issue_number=${issue-num}`, `work_mode=${work-mode}`
+
+If the required MCP tools are unavailable, stop before potential-entry creation, issue promotion, or active-folder creation begins. Restore MCP connectivity first. Agent sessions do not have an approved non-MCP execution branch for promotion work.
+
+## Agent-Session Promotion Execution Rule
+
+Execute the lifecycle only through the MCP tool forms listed above. The MCP path is the sole authoritative execution path for agent sessions.
+
+After each successful promotion operation, persist the raw MCP receipt payload under the matching checkpoint key in `artifacts/orchestration/orchestrator-state.json`:
+- `delegation_receipts.promotion.potential_entry`
+- `delegation_receipts.promotion.issue`
+- `delegation_receipts.promotion.feature_folder`
+
+Each `delegation_receipts.promotion.*` field stores the raw MCP receipt payload returned by the corresponding promotion operation without lossy normalization.
+
+Note: VS Code command-palette commands may exist for interactive extension use, but this note is non-authoritative for agent sessions.
+
+## Canonical Variables
+
+- `${promotion-type}`: `feature` or `bug`
+- `${short-name}`: lowercase slug, hyphen-separated
+- `${relativeFile}`: workspace-relative path to created potential entry markdown
+- `${long-name}`: `${relativeFile}` filename without `.md`
+- `${issue-num}`: promoted GitHub issue number
+- `${feature-folder}`: active feature folder path
+- `${plan-path}`: single canonical plan file path reused across planning and preflight revisions
+- `${work-mode}`: `minor-audit`, `full-feature`, or `full-bug` (legacy `full` is accepted only as an alias for `full-feature`)
+- `${short-path-flag}`: `--work-mode minor-audit` (mandatory for short-path promotion/folder creation)
+
+`${relativeFile}` MUST resolve to a real potential markdown path before promotion begins. If the path is missing, invalid, or non-markdown, stop. Do not infer or synthesize the missing value.
+
+`${issue-num}` MUST be numeric after promotion and before branch or folder creation. If promotion does not return a numeric issue number, stop. Do not infer or synthesize the missing value.
+
+When orchestrator routing selects short path, promotion/folder initialization still occurs and MUST use `minor-audit` mode.
+
+Lifecycle guardrails:
+- `${relativeFile}` MUST resolve to a real potential markdown path before promotion.
+- `${issue-num}` MUST be numeric after promotion and before branch or folder creation.
+- Do not infer or synthesize the missing value.
+- If `${relativeFile}` or `${issue-num}` is missing, placeholder text, or unverified, stop before branch creation, active-folder creation, or active-folder authoring.
+
+1) Use the same MCP tool-availability preflight described above and continue only when the required promotion tools are available.
+
+2) Promote the potential document through `mcp__drmCopilotExtension__potential_to_issue` with `work_mode=minor-audit`.
+
+3) Create branch:
+- `${promotion-type}/${short-name}-${issue-num}`
+
+4) Create the active feature folder through `mcp__drmCopilotExtension__new_active_feature_folder` with `work_mode=minor-audit`.
+
+4a) Verify minor-audit folder integrity before proceeding:
+- `${feature-folder}/issue.md` exists and contains `- Work Mode: minor-audit`
+- `${feature-folder}/issue.md` contains an explicit `## Acceptance Criteria` section
+- `${feature-folder}/spec.md` does not exist
+- `${feature-folder}/user-story.md` does not exist
+- if any check fails, stop and remediate before planning
+
+5) Delegate minimal-audit plan creation to `atomic_planner` with directive:
+- `DIRECTIVE: MINIMAL-AUDIT PLAN REQUIRED`
+
+5a) Resolve and persist `${plan-path}` before delegation:
+- reuse the earliest existing `plan*.md` in `${feature-folder}` when present
+- otherwise create exactly one canonical plan file path and reuse it for all revisions
+
+6) Require preflight validation via `atomic_executor` until:
+- `PREFLIGHT: ALL CLEAR`
+
+7) Execute plan Phase 0 only via executor and checkpoint evidence.
+
+8) Branch:
+- manual bootstrap: save state and stop,
+- non-bootstrap: continue with constrained small-path development.
+
+9) Validate delivery via executor against `issue.md`, then run reduced audit/remediation loop until ready-to-merge.
+
+## Required Outputs for Downstream Handoffs
+
+Before delegating research/spec/planning, provide:
+- `${feature-folder}/issue.md`
+- `${feature-folder}/spec.md` (or expected target path)
+- `${feature-folder}/user-story.md` (or explicit `NONE`)
+- latest research artifact path(s)
+- constraints/APIs/invariants to preserve
+
+Mode-aware expectations:
+- For `minor-audit`, the explicit `## Acceptance Criteria` section in `issue.md` is the primary acceptance-criteria source and `spec.md`/`user-story.md` may be intentionally absent by design.
+- For `minor-audit`, do not infer acceptance criteria from other `issue.md` sections such as verification notes, next steps, or severity checklists.
+- For `minor-audit`, `spec.md`/`user-story.md` must be treated as integrity failures when they appear unexpectedly in the active folder.
+- For `full-feature`, `spec.md` and `user-story.md` are expected alongside `issue.md`.
+- For `full-bug`, `spec.md` is expected alongside `issue.md`; `user-story.md` should be absent unless the requirements explicitly justify it.
+
+Selected-mode persistence requirements:
+- Producer outputs MUST persist exactly one marker in `issue.md` metadata above the first `##` heading:
+	- `- Work Mode: minor-audit`
+	- `- Work Mode: full-feature`
+	- `- Work Mode: full-bug`
+- Persisted marker MUST represent selected mode after eligibility checks, not requested mode.
+- If a legacy requested `full` path is accepted, tooling MUST normalize it to `full-feature` before persistence.
+- If a requested `minor-audit` path is rejected by eligibility checks, tooling MUST fail closed to `full-feature`, emit the downgrade reason, and persist `- Work Mode: full-feature`.

package/resources/codex-and-agents-customizations/.agents/skills/feature-review/SKILL.md

@@ -0,0 +1,106 @@
+---
+name: feature-review
+description: 'Review a feature branch relative to a base branch and write audit artifacts into the active feature folder. Use when Codex must produce policy, code, and feature audits and trigger remediation planning when needed.'
+---
+
+# Feature Review
+
+Workflow skill for PR-style feature review in Codex.
+
+## Required Shared Skills
+
+Always apply:
+- `policy-compliance-order`
+- `evidence-and-timestamp-conventions`
+- `policy-audit-template-usage`
+- `pr-context-artifacts`
+- `acceptance-criteria-tracking`
+- `remediation-handoff-atomic-planner`
+
+Use as needed:
+- `pr-base-branch-merge-base`
+- `repo-automation-adapter`
+
+## Role
+
+- Review the feature branch relative to the correct base.
+- Produce audit-grade artifacts, not code fixes.
+- Prefer deterministic evidence from PR-context artifacts and exact diff anchors.
+- Trigger remediation planning when blockers or unmet acceptance criteria exist.
+
+## Required Outputs
+
+Write timestamped artifacts into the active feature folder:
+- `policy-audit.<timestamp>.md`
+- `code-review.<timestamp>.md`
+- `feature-audit.<timestamp>.md`
+- `remediation-inputs.<timestamp>.md` when remediation is required
+- `remediation-plan.<timestamp>.md` when remediation is required
+
+The final review report MUST end with these exact single-line fields:
+- `REVIEW_STATUS: PASS` or `REVIEW_STATUS: REMEDIATION_REQUIRED`
+- `FEATURE_FOLDER: <path>`
+- `POLICY_AUDIT: <path>`
+- `CODE_REVIEW: <path>`
+- `FEATURE_AUDIT: <path>`
+- `REMEDIATION_INPUTS: <path-or-NONE>`
+- `REMEDIATION_PLAN: <path-or-NONE>`
+
+Each required review artifact MUST pass the matching validator command before review can be reported as complete:
+- the `validate_orchestration_artifacts` MCP tool with `artifact_type: "policy-audit"` and `artifact_path: <path>`
+- the `validate_orchestration_artifacts` MCP tool with `artifact_type: "code-review"` and `artifact_path: <path>`
+- the `validate_orchestration_artifacts` MCP tool with `artifact_type: "feature-audit"` and `artifact_path: <path>`
+
+## Review Flow
+
+1. Resolve the base branch.
+   - Use the supplied base when present.
+  - If the supplied base is missing or ambiguous, use `pr-base-branch-merge-base`.
+  - Do not default to the repository default branch unless merge-base resolution fails for all candidates.
+2. Load PR context from the canonical artifacts defined by `pr-context-artifacts`.
+3. If PR context is missing or stale, refresh it through `repo-automation-adapter` using the resolved base branch.
+4. Determine the active feature folder deterministically from the scoping docs and PR context.
+5. Create the policy audit, code review, and feature audit.
+   - validate each artifact immediately after writing it
+6. Check off passing acceptance criteria in the authoritative requirement sources per `acceptance-criteria-tracking`.
+7. If remediation is required, create remediation inputs first and then hand off plan creation using `remediation-handoff-atomic-planner`.
+8. In the final report:
+   - set `REVIEW_STATUS: PASS` only when no remediation artifact is required,
+   - set `REVIEW_STATUS: REMEDIATION_REQUIRED` when remediation inputs or a remediation plan were required,
+   - include every required artifact-path field exactly once.
+
+### Enforced Remediation Handoff Contract
+
+When remediation is required:
+
+- create `remediation-inputs.<timestamp>.md` before any remediation planning handoff,
+- create the remediation plan target file on disk before delegating plan creation,
+- automatically delegate remediation planning to `atomic-planner`,
+- treat `remediation-inputs.<timestamp>.md` as the primary requirements source,
+- include the canonical PR-context summary and appendix, the review artifacts, and the original feature plan file(s) in the delegated context package,
+- if the remediation planning handoff cannot be started or does not return a receipt, stop and report blocked state,
+- do not claim review completion until the remediation plan file exists on disk.
+
+## Required Artifact Shapes
+
+- `policy-audit.<timestamp>.md`
+  - MUST be copied from the canonical template and MUST NOT retain the template instruction block.
+  - MUST contain the canonical major headings and Appendix B command reference.
+- `code-review.<timestamp>.md`
+  - MUST contain `## Executive Summary`.
+  - MUST contain `## Findings Table`.
+  - MUST contain a Markdown table header with `Severity | File | Location | Finding | Recommendation | Rationale | Evidence`.
+- `feature-audit.<timestamp>.md`
+  - MUST contain `## Scope and Baseline`.
+  - MUST contain `## Acceptance Criteria Inventory`.
+  - MUST contain `## Acceptance Criteria Evaluation`.
+  - MUST contain `## Summary`.
+  - MUST contain `## Acceptance Criteria Check-off`.
+
+## Review Constraints
+
+- Do not silently fix code during review.
+- Prefer check-only commands.
+- If a tool cannot be run, mark the related section as unverified or partial with a concrete reason.
+- Do not claim completion until every required artifact exists on disk and its validator passes.
+- Do not omit any required final result field from the review report.

package/resources/codex-and-agents-customizations/.agents/skills/feature-review-workflow/SKILL.md

@@ -0,0 +1,181 @@
+# Converted skill
+
+Applied rewrites:
+- None
+
+---
+name: feature-review-workflow
+description: 'Feature-branch review workflow for base-branch resolution, PR-context refresh, active feature folder selection, review artifact generation, validator gates, acceptance-criteria check-off, and remediation triggers. Use when authoring or executing PR-style feature reviews.'
+---
+
+# Feature Review Workflow
+
+Reusable workflow guidance for PR-style feature review.
+
+## Required Shared Skills
+
+Always apply:
+- `policy-compliance-order`
+- `evidence-and-timestamp-conventions`
+- `policy-audit-template-usage`
+- `pr-context-artifacts`
+- `pr-base-branch-merge-base`
+- `acceptance-criteria-tracking`
+- `remediation-handoff-atomic-planner`
+
+## Role
+
+- Review a feature branch relative to the correct base branch.
+- Produce audit artifacts, not implementation fixes.
+- Prefer deterministic evidence from canonical PR-context artifacts and exact diff anchors.
+- Trigger remediation planning when blockers or unmet acceptance criteria remain.
+
+## Workflow Contract
+
+### Baseline and evidence
+
+- Treat the review as a feature-vs-base audit, not an isolated file inspection.
+- Use `artifacts/pr_context.summary.txt` as the primary evidence source.
+- Use `artifacts/pr_context.appendix.txt` as the baseline-diff appendix for raw evidence and exact anchors.
+- If PR-context artifacts are missing or stale, refresh them per `pr-context-artifacts` using the resolved base branch.
+
+### Review artifact templates
+
+- When creating review artifacts from templates, use the MCP-exposed bundled assets instead of copying directly from repo template paths.
+- Resolve the templates through the MCP server tool `resolve_policy_audit_template_asset` with these selectors:
+  - `template` for `policy-audit.<timestamp>.md`
+  - `code-review-template` for `code-review.<timestamp>.md`
+  - `feature-audit-template` for `feature-audit.<timestamp>.md`
+- The MCP-resolved asset is the authoritative template source for review artifacts in this workflow.
+
+### No silent fixes
+
+- Do not clean up code during review.
+- If checks fail, document the failure and include exact remediation guidance.
+
+### Work-mode acceptance-criteria contract
+
+- Read the persisted marker from `issue.md` using one of:
+  - `- Work Mode: minor-audit`
+  - `- Work Mode: full-feature`
+  - `- Work Mode: full-bug`
+- Legacy compatibility: interpret `- Work Mode: full` as `full-feature`.
+- Acceptance-criteria sources by marker:
+  - `minor-audit`: only the explicit `## Acceptance Criteria` section in `issue.md`
+  - `full-feature`: `spec.md` and `user-story.md`
+  - `full-bug`: `spec.md`
+- Fail closed:
+  - if the marker is missing or malformed, use `full-feature`
+  - if `minor-audit` is selected and `issue.md` lacks `## Acceptance Criteria`, require remediation
+
+## Ordered Procedure
+
+1. **Resolve the base branch**
+   - Use the supplied base branch when it is present.
+   - Otherwise resolve `PRBaseBranch` with `pr-base-branch-merge-base`.
+   - Record the resolved branch, merge-base SHA, merge-base timestamp, and top competing candidates when available.
+
+2. **Load or refresh PR context**
+   - Load the canonical PR-context summary and appendix per `pr-context-artifacts`.
+   - Refresh only when the artifacts are missing or stale relative to the current branch state.
+
+3. **Determine the active feature folder**
+   - Prefer the active feature folder that corresponds to the primary changed scoping docs.
+   - If multiple active folders are present, prefer the one whose suffix matches the issue number in the branch name.
+   - Otherwise choose the folder with the most material scoping-doc changes.
+   - If no active feature folder exists, create `docs/features/active/<today>-feature-review/` and document the assumption.
+
+4. **Produce the policy audit**
+  - Use `policy-audit-template-usage` and the MCP `template` asset to drive the artifact structure.
+   - Include exact command references for the checks that were run.
+   - Validate the resulting `policy-audit.<timestamp>.md` immediately after writing it.
+
+5. **Run required checks**
+   - Prefer repo-defined, check-only commands.
+   - Default order:
+     1. formatting check
+     2. lint check
+     3. type check
+     4. tests
+     5. coverage (mandatory for every language that has changed files)
+        - TypeScript: `npm run test:unit:coverage` → artifact: `coverage/lcov.info`
+        - Python: `poetry run pytest --cov` → artifact: `artifacts/python/lcov.info`
+        - PowerShell: `mcp__drmCopilotExtension__run_poshqc_test` → artifact: `artifacts/pester/powershell-coverage.xml`
+        - C#: `vstest.console.exe <test-assembly-paths> /EnableCodeCoverage` → artifact: `artifacts/csharp/coverage.xml`
+        - Coverage thresholds:
+          - New code files (added in this feature): line coverage must be >= 90%. Flag as FAIL otherwise.
+          - Modified files (changed but previously existing): line coverage must show no regression relative to baseline and must remain >= 80%. Flag as FAIL otherwise.
+          - Repo-wide line coverage must remain >= 80% per language. Flag as FAIL otherwise.
+        - If coverage artifacts already exist from the executor run, inspect them instead of re-running.
+        - If no coverage artifact exists for a language that has changed files, flag as FAIL — coverage verification is mandatory for all languages with changed files.
+   - Run the smallest relevant subset first when the repo policy permits it.
+   - If a tool cannot run in the environment, mark the affected section unverified or partial with a concrete reason.
+
+6. **Produce the code review**
+  - Create the artifact from the MCP `code-review-template` asset.
+   - Write `code-review.<timestamp>.md` with:
+     - `## Executive Summary`
+     - `## Findings Table`
+     - a Markdown findings table header containing `Severity | File | Location | Finding | Recommendation | Rationale | Evidence`
+   - Include typed-Python review where Python files changed.
+   - Validate the artifact immediately after writing it.
+
+7. **Produce the feature audit**
+  - Create the artifact from the MCP `feature-audit-template` asset.
+   - Write `feature-audit.<timestamp>.md` with:
+     - `## Scope and Baseline`
+     - `## Acceptance Criteria Inventory`
+     - `## Acceptance Criteria Evaluation`
+     - `## Summary`
+     - `## Acceptance Criteria Check-off`
+   - Use the resolved base branch in the baseline section.
+   - Evaluate each criterion as PASS, PARTIAL, FAIL, or UNVERIFIED.
+   - Check off passing criteria in the authoritative source files per `acceptance-criteria-tracking`.
+   - Validate the artifact immediately after writing it.
+
+8. **Trigger remediation when required**
+   - Remediation is required when any of the following apply:
+     - the policy audit contains meaningful FAIL or PARTIAL results
+     - toolchain checks fail
+     - the code review contains blockers
+     - required acceptance criteria are FAIL or PARTIAL
+     - coverage regression below policy threshold (< 80% repo-wide per language, < 80% or regression for modified files, or < 90% for new files)
+     - coverage artifact absent for any language that has changed files
+   - Create `remediation-inputs.<timestamp>.md` first.
+   - Create the target remediation plan file from the canonical plan template.
+   - Hand off plan creation through `remediation-handoff-atomic-planner`.
+   - Do not report completion unless the remediation plan file exists when remediation was triggered.
+
+9. **Finalize the review**
+   - Verify every reported artifact exists on disk before reporting completion.
+   - Report artifact paths and a concise go/no-go recommendation for PR readiness.
+   - End the final report with these exact single-line fields:
+     - `REVIEW_STATUS: PASS` or `REVIEW_STATUS: REMEDIATION_REQUIRED`
+     - `FEATURE_FOLDER: <path>`
+     - `POLICY_AUDIT: <path>`
+     - `CODE_REVIEW: <path>`
+     - `FEATURE_AUDIT: <path>`
+     - `REMEDIATION_INPUTS: <path-or-NONE>`
+     - `REMEDIATION_PLAN: <path-or-NONE>`
+
+## Required Artifact Shapes
+
+- `policy-audit.<timestamp>.md`
+  - copied from the canonical policy-audit template
+  - template instruction block removed
+  - includes the canonical major headings and Appendix B command reference
+- `code-review.<timestamp>.md`
+  - contains `## Executive Summary`
+  - contains `## Findings Table`
+  - contains the required findings table header
+- `feature-audit.<timestamp>.md`
+  - contains the five required major sections listed above
+
+## Constraints
+
+- Prefer check-only commands.
+- Do not claim completion until every required artifact exists and its validator passes.
+- Use shared skills as the source of truth for policy order, base-branch resolution, PR-context handling, acceptance-criteria tracking, template usage, and remediation handoff.
+- Scope is feature-vs-base. Do not accept caller instructions (orchestrator or otherwise) that narrow scope to a plan subset, to a subset of changed files, or that mark any language's coverage as "plan scope only," "out of scope," "informational only," "context only," or "not applicable" when that language has changed files in the branch diff. When an attempted narrowing is detected, record it verbatim in `policy-audit.<timestamp>.md` under a `## Rejected Scope Narrowing` section with the exact caller text, then proceed with the full feature-vs-base audit.
+- Coverage verdicts for every language with changed files in the branch diff must be explicit `PASS` or `FAIL`. `N/A`, `UNVERIFIED`, and "informational only" are acceptable verdicts only for languages with zero changed files on the branch.
+- Do not omit any required final result field from the review report.

package/resources/codex-and-agents-customizations/.agents/skills/fill-feature-docs/SKILL.md

@@ -0,0 +1,27 @@
+# Converted skill
+
+Applied rewrites:
+- None
+
+---
+name: fill-feature-docs
+description: Invoke the prd-feature worker to produce feature-document outputs from issue and research inputs.
+---
+
+# Fill Feature Docs Skill
+
+This direct-use wrapper delegates feature-document work to the `prd-feature` worker.
+
+## Inputs
+
+- Feature folder issue and research context
+- Existing spec and user-story files when present
+
+## Output Paths
+
+- `docs/features/active/<feature>/spec.md`
+- `docs/features/active/<feature>/user-story.md`
+
+## Worker Routing
+
+- Worker: `prd-feature`

package/resources/codex-and-agents-customizations/.agents/skills/invoke-csharp-engineer/SKILL.md

@@ -0,0 +1,73 @@
+# Converted skill
+
+Applied rewrites:
+- Rewrite merged standing-guidance source paths to the native AGENTS.md target.
+- Rewrite merged standing-guidance source paths to the native AGENTS.md target.
+- Rewrite merged standing-guidance source paths to the native AGENTS.md target.
+- Rewrite Claude skill paths to shared skill paths.
+- Rewrite Claude rule paths to shared skill paths.
+
+---
+name: invoke-csharp-engineer
+description: Invoke the csharp-typed-engineer worker to design, implement, and verify C# changes within typed repository boundaries. Applies CSharpier -> .NET Analyzers -> Nullable Analysis -> MSTest toolchain, the 1-3 production-file small-path budget, and zero-regression quality gates.
+---
+
+# Implement C# Skill
+
+This direct-use wrapper delegates C# implementation work to the `csharp-typed-engineer` worker. Use this entry point when a prompt needs a scoped C# change that must stay inside the typed engineer's guardrails.
+
+## When to Use This Skill
+
+Use this skill when:
+
+- The user requests a C# code change, bug fix, refactor, or test addition.
+- Estimated scope fits the small path (1-3 production files plus corresponding tests).
+- The toolchain (CSharpier, .NET Analyzers, Nullable Analysis, MSTest) can be run in the current environment, or the user has explicitly authorized an unverified plan-only response.
+
+If the estimated scope exceeds the small-path budget, this skill defers to the orchestrated flow via `csharp-change-budget-router` instead of proceeding directly.
+
+## Inputs
+
+- Objective statement (what the change must accomplish).
+- Files or entrypoints in scope.
+- Constraints, including public APIs that must be preserved.
+- Optional approved plan. If none is supplied, the worker delegates plan authoring to `atomic_planner` before any edits.
+- Optional budget override in the form `budget: prod=<N>, test=<M>` subject to repo policy compliance.
+
+## Output Paths
+
+- C# source and test files within the approved scope.
+- Baseline evidence under `<FEATURE>/evidence/baseline/<timestamp>/` and post-change evidence under `<FEATURE>/evidence/qa-gates/<timestamp>/` per `evidence-and-timestamp-conventions`.
+- This location is canonical per evidence-and-timestamp-conventions and is not overridable. See `.agents/skills/evidence-and-timestamp-conventions/SKILL.md` for the canonical evidence path authority.
+- Plan artifacts under the active feature folder when the task is feature-scoped.
+
+## Required Reporting Block
+
+The worker must return the following reporting block:
+
+1. Scope (exact file list).
+2. Baseline (CSharpier, .NET Analyzers, Nullable Analysis, MSTest, coverage status).
+3. Plan (design and test strategy).
+4. Diffs (patch-style or full-file replacements).
+5. QA Gate Results (CSharpier, .NET Analyzers, Nullable Analysis, MSTest, and coverage deltas, or clearly marked **unverified**).
+
+## Worker Routing
+
+- Worker: `csharp-typed-engineer`
+
+## Preloaded Contracts
+
+The worker operates under the following preloaded skills and rules:
+
+- `policy-compliance-order`
+- `csharp-change-budget-router`
+- `atomic-plan-contract`
+- `csharp-qa-gate`
+- `acceptance-criteria-tracking`
+- `feature-promotion-lifecycle`
+- `remediation-handoff-atomic-planner`
+- `evidence-and-timestamp-conventions`
+- `.agents/skills/csharp/SKILL.md` (path-scoped for `**/*.cs` and `**/*.csproj`)
+- `AGENTS.md`
+- `AGENTS.md`
+- `AGENTS.md`

package/resources/codex-and-agents-customizations/.agents/skills/invoke-powershell-engineer/SKILL.md

@@ -0,0 +1,74 @@
+# Converted skill
+
+Applied rewrites:
+- Rewrite merged standing-guidance source paths to the native AGENTS.md target.
+- Rewrite merged standing-guidance source paths to the native AGENTS.md target.
+- Rewrite merged standing-guidance source paths to the native AGENTS.md target.
+- Rewrite Claude skill paths to shared skill paths.
+- Rewrite Claude rule paths to shared skill paths.
+
+---
+name: invoke-powershell-engineer
+description: Invoke the powershell-typed-engineer worker to design, implement, and verify PowerShell changes within typed repository boundaries. Applies PoshQC format -> analyze -> test toolchain, the 1-2 production-file direct-mode budget, the 3-production + 3-test per-batch cap, and zero-regression quality gates.
+---
+
+# Implement PowerShell Skill
+
+This direct-use wrapper delegates PowerShell implementation work to the `powershell-typed-engineer` worker. Use this entry point when a prompt needs a scoped PowerShell change that must stay inside the typed engineer's guardrails.
+
+## When to Use This Skill
+
+Use this skill when:
+
+- The user requests a PowerShell code change, bug fix, refactor, or test addition.
+- Estimated scope fits the direct-mode path (1-2 production PowerShell files plus corresponding tests).
+- The toolchain (PoshQC format, PSScriptAnalyzer, Pester with coverage where enforced) can be run in the current environment, or the user has explicitly authorized an unverified plan-only response.
+
+If the estimated scope exceeds the direct-mode budget, this skill defers to the orchestrated flow via `powershell-change-budget-router` instead of proceeding directly.
+
+## Inputs
+
+- Objective statement (what the change must accomplish).
+- Files or entrypoints in scope (exact script or module paths and corresponding `*.Tests.ps1` paths).
+- Constraints, including public function or module contracts that must be preserved.
+- Optional approved plan. If none is supplied, the worker delegates plan authoring to `atomic_planner` before any edits.
+- Optional budget override in the form `budget: prod=<N>, test=<M>` subject to repo policy compliance.
+
+## Output Paths
+
+- PowerShell source (`*.ps1`, `*.psm1`, `*.psd1`) and Pester test (`*.Tests.ps1`) files within the approved scope.
+- Baseline evidence under `<FEATURE>/evidence/baseline/<timestamp>/` and post-change evidence under `<FEATURE>/evidence/qa-gates/<timestamp>/` per `evidence-and-timestamp-conventions`.
+- This location is canonical per evidence-and-timestamp-conventions and is not overridable. See `.agents/skills/evidence-and-timestamp-conventions/SKILL.md` for the canonical evidence path authority.
+- Plan artifacts under the active feature folder when the task is feature-scoped.
+
+## Required Reporting Block
+
+The worker must return the `powershell-qa-gate` reporting block:
+
+1. Scope (exact file list).
+2. Baseline (PSScriptAnalyzer, Pester, coverage status).
+3. Plan (design and test strategy, including minimal DI seams and external executable wrapper mock strategy).
+4. Diffs (patch-style or full-file replacements).
+5. QA Gate Results (PSScriptAnalyzer, Pester, and coverage deltas, or clearly marked **unverified**).
+
+## Worker Routing
+
+- Worker: `powershell-typed-engineer`
+
+## Preloaded Contracts
+
+The worker operates under the following preloaded skills and rules:
+
+- `policy-compliance-order`
+- `powershell-change-budget-router`
+- `powershell-orchestration-state-machine`
+- `atomic-plan-contract`
+- `powershell-qa-gate`
+- `acceptance-criteria-tracking`
+- `feature-promotion-lifecycle`
+- `remediation-handoff-atomic-planner`
+- `evidence-and-timestamp-conventions`
+- `.agents/skills/powershell/SKILL.md` (path-scoped for `**/*.ps1`, `**/*.psm1`, `**/*.psd1`)
+- `AGENTS.md`
+- `AGENTS.md`
+- `AGENTS.md`

package/resources/codex-and-agents-customizations/.agents/skills/invoke-python-engineer/SKILL.md

@@ -0,0 +1,73 @@
+# Converted skill
+
+Applied rewrites:
+- Rewrite merged standing-guidance source paths to the native AGENTS.md target.
+- Rewrite merged standing-guidance source paths to the native AGENTS.md target.
+- Rewrite merged standing-guidance source paths to the native AGENTS.md target.
+- Rewrite Claude skill paths to shared skill paths.
+- Rewrite Claude rule paths to shared skill paths.
+
+---
+name: invoke-python-engineer
+description: Invoke the python-typed-engineer worker to design, implement, and verify Python changes within typed repository boundaries. Applies Black -> Ruff -> Pyright -> Pytest toolchain, the 3-production + 3-test per-batch budget, and zero-regression quality gates.
+---
+
+# Implement Python Skill
+
+This direct-use wrapper delegates Python implementation work to the `python-typed-engineer` worker. Use this entry point when a prompt needs a scoped Python change that must stay inside the typed engineer's guardrails.
+
+## When to Use This Skill
+
+Use this skill when:
+
+- The user requests a Python code change, bug fix, refactor, or test addition.
+- Estimated scope fits the small path (1-3 production files plus corresponding tests).
+- The toolchain (Black, Ruff, Pyright, Pytest) can be run in the current environment, or the user has explicitly authorized an unverified plan-only response.
+
+If the estimated scope exceeds the small-path budget, this skill defers to the orchestrated flow via `python-change-budget-router` instead of proceeding directly.
+
+## Inputs
+
+- Objective statement (what the change must accomplish).
+- Files or entrypoints in scope.
+- Constraints, including public APIs that must be preserved.
+- Optional approved plan. If none is supplied, the worker delegates plan authoring to `atomic_planner` before any edits.
+- Optional budget override in the form `budget: prod=<N>, test=<M>` subject to repo policy compliance.
+
+## Output Paths
+
+- Python source and test files within the approved scope.
+- Baseline evidence under `<FEATURE>/evidence/baseline/<timestamp>/` and post-change evidence under `<FEATURE>/evidence/qa-gates/<timestamp>/` per `evidence-and-timestamp-conventions`.
+- This location is canonical per evidence-and-timestamp-conventions and is not overridable. See `.agents/skills/evidence-and-timestamp-conventions/SKILL.md` for the canonical evidence path authority.
+- Plan artifacts under the active feature folder when the task is feature-scoped.
+
+## Required Reporting Block
+
+The worker must return the `python-qa-gate` reporting block:
+
+1. Scope (exact file list).
+2. Baseline (Ruff, Pyright, Pytest, coverage status).
+3. Plan (design and test strategy).
+4. Diffs (patch-style or full-file replacements).
+5. QA Gate Results (Ruff, Pyright, Pytest, and coverage deltas, or clearly marked **unverified**).
+
+## Worker Routing
+
+- Worker: `python-typed-engineer`
+
+## Preloaded Contracts
+
+The worker operates under the following preloaded skills and rules:
+
+- `policy-compliance-order`
+- `python-change-budget-router`
+- `atomic-plan-contract`
+- `python-qa-gate`
+- `acceptance-criteria-tracking`
+- `feature-promotion-lifecycle`
+- `remediation-handoff-atomic-planner`
+- `evidence-and-timestamp-conventions`
+- `.agents/skills/python/SKILL.md` (path-scoped for `**/*.py`)
+- `AGENTS.md`
+- `AGENTS.md`
+- `AGENTS.md`