@danmoisan/drm-copilot-mcp 0.0.1 → 0.0.5

package/resources/codex-and-agents-customizations/.agents/skills/repo-automation-adapter/SKILL.md

@@ -1,49 +1,39 @@
 ---
 name: repo-automation-adapter
-description: 'Centralize host-surface and repo-automation differences for Codex. Use when a migrated workflow previously depended on GitHub Copilot or VS Code extension commands and needs a single Codex-compatible execution or fallback rule.'
+description: 'Centralize required drm-copilot MCP execution for Codex repo automation. Use when a workflow needs promotion, PR context, commit context, customization publishing, hard-lock resolution, or orchestration validation.'
 ---
 
 # Repo Automation Adapter
 
-Use this skill to keep host-specific workflow translation in one place.
+Use this skill to keep host-specific workflow execution rules in one place.
 
-## When to Use This Skill
+## Canonical Rule
 
-Use this skill when:
-- a migrated skill previously depended on `drmCopilotExtension.*` commands,
-- a workflow needs PR-context collection, issue promotion, or feature-folder creation,
-- the same fallback behavior would otherwise be repeated across multiple skills.
+The `drm-copilot` MCP server is the only approved execution surface for canonical repository automation covered by this skill.
 
-## Canonical Rule
+There is no fallback. If the server is unavailable, the required tool is unavailable, or the MCP call fails, the workflow must stop, persist blocked state when an orchestrator checkpoint is active, and report the missing dependency or failed MCP operation.
 
-Do not encode host-specific execution details in multiple workflow skills. Put them here and have the calling skills reference this skill.
+Do not replace a required MCP operation with local scripts, git reconstruction, direct filesystem synthesis, VS Code command IDs, or best-effort behavior.
 
-## Published Codex Automation Surface
+## When to Use This Skill
 
-The canonical Codex automation dependency for this repo is the published MCP server:
-- `drmCopilotExtension`
+Use this skill when:
 
-Downstream Codex skills should depend on the MCP server name `drmCopilotExtension`, not on raw VS Code command IDs.
+- a migrated workflow previously depended on `drmCopilotExtension.*` commands,
+- a workflow needs PR-context collection, issue promotion, feature-folder creation, commit-context collection, customization publishing, hard-lock prompt resolution, or orchestration-artifact validation,
+- multiple skills need the same MCP-required execution rule.
 
-Declare that dependency once on this skill via `agents/openai.yaml`.
+## Published Codex Automation Surface
 
-## Codex Capability Model
+The required Codex automation dependency for this repo is the published MCP server:
 
-Codex in this repo can reliably use:
-- repository files,
-- shell commands,
-- git,
-- local scripts that already exist in the repository,
-- configured MCP tools when available.
+- `drm-copilot`
 
-Codex in this repo should not assume direct access to:
-- `vscode/runCommand`,
-- `drmCopilotExtension.*` command execution,
-- GitHub issue or PR mutation unless an explicit connector or script is available.
+Downstream Codex skills must depend on the MCP server name `drm-copilot`, not on raw VS Code command IDs.
 
 ## Published MCP Tool Surface
 
-Prefer these semantic MCP tools when the server is configured:
+Use these semantic MCP tools when the corresponding operation is required:
 
 - `collect_commit_context`
 - `collect_pr_context`
@@ -54,8 +44,14 @@ Prefer these semantic MCP tools when the server is configured:
 - `potential_to_issue`
 - `new_active_feature_folder`
 - `resolve_execute_hard_lock_prompt`
+- `resolve_atomic_plan_prompt`
+- `validate_orchestration_artifacts`
+- `run_poshqc_format`
+- `run_poshqc_analyze`
+- `run_poshqc_analyze_autofix`
+- `run_poshqc_test`
 
-Legacy VS Code command IDs remain historical source material only:
+Legacy VS Code command IDs are historical source material only and must not be invoked:
 
 - `drmCopilotExtension.collectCommitContext`
 - `drmCopilotExtension.collectPrContext`
@@ -69,74 +65,97 @@ Legacy VS Code command IDs remain historical source material only:
 
 ## Adapter Preconditions
 
-Before treating the MCP path as available, assume these prerequisites:
+Before starting any workflow that depends on this skill, the orchestrator must assume these prerequisites are mandatory:
 
-- the Codex client is configured with MCP server name `drmCopilotExtension`
-- the published extension or bridge is installed and built
-- an open workspace folder exists for workspace-targeted operations
-- `python` is on `PATH`
-- `pwsh` is preferred, with Windows PowerShell fallback when applicable
+- the Codex project is trusted so project `.codex/config.toml` loads,
+- the Codex client is configured with MCP server name `drm-copilot`,
+- the `drm-copilot` MCP server is active,
+- the required MCP tool is exposed by the active server,
+- an open workspace folder exists for workspace-targeted operations.
+
+If any prerequisite is missing, stop before mutating workflow state.
 
 ## Execution Order
 
 For any host-specific workflow step:
 
-1. Prefer the published `drmCopilotExtension` MCP tool when it covers the requested operation.
-2. If the MCP server is unavailable, determine whether a deterministic git or filesystem fallback is sufficient.
-3. If a deterministic fallback is sufficient, use it and record that the result is a fallback artifact rather than a canonical tool-produced artifact.
-4. If no MCP path or safe fallback exists, stop and report the missing automation dependency instead of inventing behavior.
+1. Identify the required `drm-copilot` MCP tool.
+2. Call that MCP tool.
+3. Validate the MCP response according to the calling workflow's contract.
+4. If the tool is unavailable, the call fails, or the response does not satisfy the contract, stop and record blocked state. Do not execute a replacement path.
 
 ## Current Adapter Guidance
 
 ### PR context collection
 
-- Preferred: call tool `collect_pr_context` on MCP server `drmCopilotExtension`.
+- Required tool: `collect_pr_context`.
 - When the caller already resolved a base branch, pass that base explicitly.
-- Current fallback: use deterministic git commands to reconstruct equivalent context when review workflows only need base/head, merge-base, commits, and changed files.
-- When using fallback, record the provenance in the generated review artifact.
 - For orchestrator remediation loops, PR-context refresh is mandatory after each remediation commit and before each re-review.
-- When the caller explicitly requires MCP tooling for PR-context refresh, do not silently downgrade to fallback; stop and report the dependency gap instead.
+- If the tool is unavailable or fails, stop. Do not reconstruct PR context from local git commands.
 
 ### Commit context collection
 
-- Preferred: call tool `collect_commit_context` on MCP server `drmCopilotExtension`.
-- If the MCP server is unavailable and the workflow only needs staged-diff summary, use non-destructive git inspection as fallback and record that provenance.
+- Required tool: `collect_commit_context`.
 - For orchestrator remediation loops, collect commit context only after `git add -A` and only when staged changes exist.
-- For orchestrator remediation loops, do not continue to commit-message generation without an on-disk commit-context artifact path produced by the selected adapter path.
-- When the caller explicitly requires MCP tooling for commit-context collection, do not silently downgrade to fallback; stop and report the dependency gap instead.
+- Do not continue to commit-message generation without an on-disk commit-context artifact path produced by the MCP tool.
+- If the tool is unavailable or fails, stop. Do not replace it with staged-diff inspection.
 
 ### Feature promotion and active feature folder creation
 
-- Preferred MCP tools:
-  - `new_potential_entry`
-  - `new_potential_bug_entry`
-  - `potential_to_issue`
-  - `new_active_feature_folder`
-- Current rule: use the MCP tools as the canonical path.
-- Execute these lifecycle operations as one ordered chain:
-  - create potential entry
-  - promote with `potential_to_issue`
-  - capture numeric issue number from promotion output
-  - create or check out `${promotion-type}/${short-name}-${issue-num}`
-  - create active feature folder with `new_active_feature_folder`
-- `new_active_feature_folder` is not an allowed bootstrap substitute for missing promotion state.
-- If `${issue-num}` is missing, non-numeric, or placeholder text, stop instead of continuing.
-- If the MCP server is unavailable, surface a precise dependency gap unless the caller explicitly requests a best-effort local-only fallback.
-- Do not synthesize GitHub issue state, active-folder scaffolding, or placeholder lifecycle variables unless the user explicitly requests a best-effort local-only fallback.
-- When a local-only fallback is explicitly approved, preserve the same ordered lifecycle and verification gates; do not skip directly to folder creation.
+Required tools:
+
+- `new_potential_entry`
+- `new_potential_bug_entry`
+- `potential_to_issue`
+- `new_active_feature_folder`
+
+Execute these lifecycle operations as one ordered chain:
+
+1. Create the potential entry.
+2. Promote with `potential_to_issue`.
+3. Capture numeric issue number from promotion output.
+4. Create or check out `${promotion-type}/${short-name}-${issue-num}`.
+5. Create the active feature folder with `new_active_feature_folder`.
+
+`new_active_feature_folder` is not an allowed bootstrap substitute for missing promotion state. If `${issue-num}` is missing, non-numeric, or placeholder text, stop. Do not synthesize GitHub issue state, active-folder scaffolding, or placeholder lifecycle variables.
 
 ### Customization publishing and hard-lock resolution
 
-- Preferred MCP tools:
-  - `push_down_copilot_customizations`
-  - `push_down_codex_and_agents_customizations`
-  - `resolve_execute_hard_lock_prompt`
-- If the MCP server is unavailable, stop unless the caller explicitly provides an approved alternate path.
+Required tools:
+
+- `push_down_copilot_customizations`
+- `push_down_codex_and_agents_customizations`
+- `resolve_execute_hard_lock_prompt`
+- `resolve_atomic_plan_prompt`
+
+If the required tool is unavailable or fails, stop.
+
+### Orchestration artifact validation
+
+Required tool:
+
+- `validate_orchestration_artifacts`
+
+Use this tool for canonical validation of plans, policy audits, code reviews, feature audits, and orchestrator state. For orchestrator completion, call it with `artifact_type: "orchestrator-state"` and `require_complete: true`.
+
+If the tool is unavailable or fails, stop. Do not substitute direct CLI validation for canonical orchestrator completion.
+
+### PowerShell quality gates
+
+Required tools:
+
+- `run_poshqc_format`
+- `run_poshqc_analyze`
+- `run_poshqc_analyze_autofix`
+- `run_poshqc_test`
+
+When a workflow requires PoshQC execution through MCP, use only these tools. If the required tool is unavailable or fails, stop.
 
 ## Output Requirements
 
-When this skill is used, the calling workflow should report:
-- which operation required host adaptation,
-- which direct adapter or fallback path was selected,
-- whether the result is canonical or fallback-only,
-- what dependency is missing when the step is blocked.
+When this skill is used, the calling workflow must report:
+
+- which MCP operation was required,
+- which `drm-copilot` tool was called,
+- whether the MCP response satisfied the calling contract,
+- the blocked-state reason when the MCP dependency is unavailable or fails.

package/resources/codex-and-agents-customizations/.agents/skills/repo-automation-adapter/agents/openai.yaml

@@ -1,5 +1,5 @@
 dependencies:
   tools:
     - type: "mcp"
-      value: "drmCopilotExtension"
+      value: "drm-copilot"
       description: "Published drm-copilot stdio MCP bridge for repository automation"

package/resources/codex-and-agents-customizations/.agents/skills/research-issue/SKILL.md

@@ -1,16 +1,6 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: research-issue
 description: Investigate the best implementation approach for a feature or bug by analyzing the codebase and external references, then writing structured findings to artifacts/research/.
-allowed-tools:
-  - Read
-  - Grep
-  - Glob
-  - WebFetch
 ---
 
 # Research Issue Skill

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

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: review-epic
 description: Invoke the epic-review worker to produce epic-audit artifacts for an epic folder.

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

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: review-feature
 description: Invoke the feature-review worker to produce feature-audit artifacts for an active feature folder.

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

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: review-staged
 description: Invoke the staged-review worker to produce staged-review artifacts from the staged diff.

package/resources/codex-and-agents-customizations/.agents/skills/self-explanatory-code-commenting/SKILL.md

@@ -1,12 +1,8 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
+name: self-explanatory-code-commenting
 paths:
   - "**/*.py"
-description: Intent-first docstring and commenting standards. Applies to Python files.
+description: Intent-first docstring and commenting standards.
 ---
 
 # Code Commenting and Docstring Policy

package/resources/codex-and-agents-customizations/.agents/skills/skill-canonical-location-audit/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- Rewrite Claude skill-directory references to the native skill root.
-
 ---
 name: skill-canonical-location-audit
 description: 'Audit skills for canonical-location duplication. Use when ensuring a canonical location for a given item is defined in exactly one skill and duplicates are flagged.'

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

@@ -0,0 +1,86 @@
+---
+name: tonality
+description: Required communication tone policy for all files and responses.
+paths:
+  - "**"
+description: Required communication tone policy. Applies to all files and responses.
+---
+
+# Converted rule
+
+Source: legacy Claude rule `tonality`.
+
+# Tonality Policy
+
+This rule file summarizes the required tone policy for all agent-authored content in this repository.
+
+## Required Professional Tone
+
+All written output must use a professional tone. Professional tone means:
+
+- Clear, direct, and factual language.
+- Neutral businesslike phrasing.
+- Measured statements that match the available evidence.
+- Concise explanations that prioritize clarity over personality.
+- Respectful wording, even when reporting defects, regressions, or disagreements.
+
+Preferred characteristics: specific rather than vague; literal rather than theatrical; calm rather than excited; precise rather than promotional.
+
+## Humor and Joking — Prohibited
+
+Do not use jokes, banter, playful remarks, sarcasm, puns, or comedic phrasing.
+
+This prohibition includes:
+- Lighthearted commentary intended to entertain.
+- Winking or self-aware jokes about tools, code, bugs, or the development process.
+- Casual filler that weakens a formal or operational message.
+- Mocking, teasing, or exaggerated "fun" framing, even when mild.
+
+When deciding between a playful sentence and a plain sentence, use the plain sentence.
+
+## Hyperbole — Prohibited
+
+Do not use hyperbolic, inflated, or sensational language. Avoid:
+
+- Claims that something is perfect, flawless, amazing, incredible, revolutionary, or world-class (unless directly quoting an authoritative source and clearly marking it as a quotation).
+- Overstated certainty that goes beyond the verified evidence.
+- Dramatic framing that overstates urgency, difficulty, simplicity, risk, or impact.
+
+Use measured alternatives: replace absolute praise with evidence-based descriptions; replace dramatic warnings with specific risks and consequences; replace sweeping claims with concrete observations.
+
+## Metaphors — Tightly Restricted
+
+Metaphor, analogy, and figurative language are not the default style. They may be used only when ALL of the following are true:
+
+1. The metaphor is strictly utilitarian.
+2. It is required to explain a technical concept that would otherwise be less clear.
+3. It improves accuracy or comprehension for the intended audience.
+4. It is brief, literal in effect, and not decorative.
+
+If a concept can be explained clearly without metaphor, do not use metaphor.
+
+## Evidence-First Wording
+
+Match the strength of the wording to the strength of the evidence:
+
+- If something was verified, say it was verified and state how.
+- If something is likely but unconfirmed, say that it is likely or appears to be the case.
+- If something is unknown, say that it is unknown.
+- Do not imply certainty, completion, safety, or correctness without support.
+
+## Difficult Messages
+
+When reporting failures, defects, or policy violations:
+- State the issue directly.
+- Describe the impact without dramatizing it.
+- Identify the next corrective action when available.
+- Avoid blame-oriented or emotionally charged wording.
+
+When giving recommendations:
+- Prefer imperative, concrete language.
+- Explain the rationale briefly when it is not obvious.
+- Avoid motivational language, sales language, or celebratory phrasing.
+
+## Final Rule
+
+When tone is uncertain, choose the more restrained phrasing. The repository default is professionalism, clarity, and accuracy — not entertainment, flourish, or hype.