drmoisan
- 411 skills
- 0 followers
- 3 days ago last updated
- ▌ Codex Model Routing · drmoisan bundleResolve and validate the deterministic Codex topology plus the exact deployment agent, model slug, and reasoning effort. Use before spawning routed Codex workers, when scope or an orchestration ceiling changes, when resuming a delegating checkpoint, or when validating Codex topology and model receipts.
- ▌ Atomic Plan Contract · drmoisanAtomic plan format and toolchain contract shared by planning and execution agents. Use when generating, validating, or executing atomic plans with Phase 0, baseline capture, and final QA loops.
- ▌ Atomic Plan Contract 2 · drmoisanAtomic plan format and toolchain contract shared by planning and execution agents. Use when generating, validating, or executing atomic plans with Phase 0, baseline capture, and final QA loops.
- ▌ Epic Orchestrate · drmoisanExecute a manually authored multi-feature epic through deterministic waves, isolated worktrees, integration-branch fan-in, and a final integration PR.
- ▌ Orchestrator State · drmoisanOrchestrator-state remediation-cycle and human-interaction invariants.
- ▌ Epic Orchestrate 2 · drmoisanRoute a multi-feature epic through the deterministic wave-scheduling, integration-branch, and fan-in workflow for the epic-orchestrator agent.
- ▌ Parallel Remove · drmoisanRemove one item from a running parallel run per the state-dependent removal behavior table — withdraw and recolor for an unstarted item, detach or abandon for an in-flight item, reject for a merged item. No default disposition is ever inferred. The abandon path runs through one deterministic CLI invocation and is hook-gated.
- ▌ Parallel Close · drmoisanTerminate an open-mode parallel run. Rejected while any item is in flight, in which case nothing is appended and no state changes. A successful close appends one run-scoped mutations[] entry and performs no recompute. This is the only way an open-mode run terminates; open mode never auto-completes.
- ▌ Research Issue 2 · drmoisanInvestigate the best implementation approach for a feature or bug by analyzing the codebase and external references, then writing structured findings to the resolved research path under docs/features/<feature>/research/ (feature-associated) or docs/research/ (one-off).
- ▌ Csharp QA Gate · drmoisanFinal QA gate for C# changes. Executes the full CSharpier -> .NET Analyzers -> Nullable Analysis -> MSTest toolchain, compares against a captured baseline, enforces zero-regression deltas, and produces the required reporting block before the agent declares the change complete.
- ▌ Atomic Planner 3 · drmoisanGenerate deterministic phased implementation plans with atomic [P#-T#] checkbox tasks. Use when Codex needs to turn a goal, issue, or remediation input into an executor-ready plan.
- ▌ Atomic Executor 3 · drmoisanExecute an atomic-planner plan exactly as written. Use when a plan with [P#-T#] tasks already exists and Codex must carry it out task-by-task without replanning.
- ▌ Quota Throttling · drmoisanQuota throttling and account-switching policy for multi-agent orchestration. Use when pacing agent work against five-hour and seven-day usage limits, deciding whether and when to switch accounts, setting concurrency caps, forecasting a rate-limit wall, handling total weekly exhaustion, or designing a usage monitor. Covers account viability, failover-dependent pacing targets, the measured cost model, commit-before-the-wall, and the coordinator/agent division of labour.
- ▌ Execution Environment · drmoisanExecution-environment brief for research, planning, preflight, execution, and orchestration. Use before planning or delegating work so tool routes, command-text restrictions, the batch budget, hook context, CI shape, contract tests, evidence rules, coverage and file-size gates, and test-isolation checks are known and are not restated in plans.
- ▌ Orchestrator Workflow 4 · drmoisanCoordinate a feature or bug request from intake through promotion, planning, execution, validation, and review by selecting the correct small or large path and delegating to migrated Codex specialists when available.
- ▌ Repo Automation Adapter 4 · drmoisan bundleCentralize 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.
- ▌
- ▌
- ▌ Pr Author 6 · drmoisanWrite a GitHub-ready pull request body from the canonical PR-context bundle with strict verification and auto-close rules.
- ▌ Orchestrate 7 · drmoisanRoute a repository request through the deterministic orchestration workflow for feature, bug, research, planning, execution, and review handoffs.
- ▌ Csharp QA Gate 10 · drmoisanFinal QA gate for C# changes. Executes the full CSharpier -> .NET Analyzers -> Nullable Analysis -> MSTest toolchain, compares against a captured baseline, enforces zero-regression deltas, and produces the required reporting block before the agent declares the change complete.
- ▌ Python QA Gate 6 · drmoisanFinal QA gate for Python changes. Executes the full Black -> Ruff -> Pyright -> Pytest toolchain, compares against a captured baseline, enforces zero-regression deltas, and produces the required reporting block before the agent declares the change complete.
- ▌ Research Issue 6 · drmoisanInvestigate the best implementation approach for a feature or bug by analyzing the codebase and external references, then writing structured findings to artifacts/research/.
- ▌ Execute Hard Lock 6 · drmoisanPlace the session in atomic execution mode bound to a specific plan-of-record. Resolves the hard-lock prompt via the drmCopilotExtension MCP tool, then delegates to the atomic-executor subagent with the resolved text. Use when a caller provides ${plan-path} and ${work-mode} and requires strict plan-following behavior.
- ▌ Powershell QA Gate 6 · drmoisanFinal QA gate for PowerShell changes. Executes the full PoshQC format -> analyze -> test toolchain (with coverage where enforced), compares against a captured baseline, enforces zero-regression deltas, and produces the required reporting block before the agent declares the change complete.
- ▌ Atomic Plan Contract 9 · drmoisanAtomic plan format and toolchain contract shared by planning and execution agents. Use when generating, validating, or executing atomic plans with Phase 0, baseline capture, and final QA loops.
- ▌ Pr Context Artifacts 4 · drmoisanPR context artifact locations and refresh rules. Use when generating, reading, or inlining pr_context summary/appendix artifacts.
- ▌ Feature Review Workflow 9 · drmoisanFeature-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.
- ▌ Pr Base Branch Merge Base 9 · drmoisanResolve PRBaseBranch for mcp__drmCopilotExtension__collect_pr_context using merge-base ancestry. Use when orchestrators or review workflows need the correct comparison base branch and must select the branch with the most recent common ancestor commit with HEAD.
- ▌ Pr Base Branch Merge Base 10 · drmoisanResolve PRBaseBranch for VS Code command: `drm-copilot: Collect PR Context` (command ID: `drmCopilotExtension.collectPrContext`) using merge-base ancestry. Use when orchestrators or review workflows need the correct comparison base branch and must select the branch with the most recent common ancestor commit with HEAD.
- ▌ Feature Promotion Lifecycle 9 · drmoisanDeterministic 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.
- ▌ Policy Audit Template Usage 6 · drmoisanPolicy audit template usage and output requirements. Use when creating policy-audit.<timestamp>.md artifacts from the repo templates.
- ▌ Evidence And Timestamp Conventions 9 · drmoisanEvidence storage and timestamp naming conventions for audits and remediation. Use when storing baseline/regression/QA evidence or naming audit artifacts with ISO-8601 timestamps.
- ▌ Remediation Handoff Atomic Planner 8 · drmoisanReusable remediation trigger and atomic_planner handoff steps. Use when audits require remediation inputs and a delegated remediation plan.
- ▌ Csharp Orchestration State Machine 6 · drmoisanCheckpoint schema and resume protocol for long-running C# orchestration workflows.
- ▌ Powershell Orchestration State Machine 7 · drmoisanCheckpoint schema and resume protocol for long-running PowerShell orchestration workflows.
- ▌ Atomic Plan Contract 8 · drmoisanAtomic plan format and toolchain contract shared by planning and execution agents. Use when generating, validating, or executing atomic plans with Phase 0, baseline capture, and final QA loops.
- ▌ Feature Review Workflow 8 · drmoisanFeature-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 Promotion Lifecycle 8 · drmoisanDeterministic promotion workflow from potential feature/bug entry to issue, branch, active feature folder, and downstream spec/research handoffs. Prefer VS Code extension command execution when extension tools are available; use underlying scripts only as fallback.
- ▌ Evidence And Timestamp Conventions 8 · drmoisanEvidence storage and timestamp naming conventions for audits and remediation. Use when storing baseline/regression/QA evidence or naming audit artifacts with ISO-8601 timestamps.
- ▌ Epic Run 5 · drmoisanExecute a previously planned epic by replaying the committed epic-kickoff artifact through the epic-orchestrator agent. Use after /epic-plan has prepared the epic (issues, folders, research, specs, atomic plans, preflight clearance) and the user is ready to execute end-to-end.
- ▌ Epic Plan 5 · drmoisanScope and prepare a multi-feature epic end-to-end before execution for the epic-planner agent - epic-worthiness gate, decomposition, dependency-wave design, complexity assessment, preparation-mode child orchestrator delegations, integration-branch fan-in, and the epic-orchestrator kickoff prompt artifact.
- ▌ Feature Review 3 · drmoisanReview 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.
- ▌ Epic Orchestrate 5 · drmoisanRoute a multi-feature epic through the deterministic wave-scheduling, integration-branch, and fan-in workflow for the epic-orchestrator agent.
- ▌ Feature Review Workflow 7 · drmoisanFeature-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.
- ▌ Pr Base Branch Merge Base 8 · drmoisanResolve PRBaseBranch for VS Code command: `drm-copilot: Collect PR Context` (command ID: `drmCopilotExtension.collectPrContext`) using merge-base ancestry. Use when orchestrators or review workflows need the correct comparison base branch and must select the branch with the most recent common ancestor commit with HEAD.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Orchestrate 5 · drmoisanRoute a repository request through the deterministic orchestration workflow for feature, bug, research, planning, execution, and review handoffs.
- ▌
- ▌ Orchestrate 6 · drmoisanRoute a repository request through the deterministic orchestration workflow for feature, bug, research, planning, execution, and review handoffs.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Orchestrator Workflow 3 · drmoisanCoordinate a feature or bug request from intake through promotion, planning, execution, validation, and review by selecting the correct small or large path and delegating to migrated Codex specialists when available.
- ▌
- ▌
- ▌
- ▌ Repo Automation Adapter 3 · drmoisan bundleCentralize 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.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Epic Run 3 · drmoisanExecute a previously prepared epic by resolving its committed kickoff artifact and delegating it to the Codex epic-orchestrator agent.
- ▌ Epic Run 4 · drmoisanExecute a previously planned epic by replaying the committed epic-kickoff artifact through the epic-orchestrator agent. Use after /epic-plan has prepared the epic (issues, folders, research, specs, atomic plans, preflight clearance) and the user is ready to execute end-to-end.
- ▌ Epic Plan 3 · drmoisanScope and prepare a multi-feature epic end-to-end before execution through the Codex epic-planner agent.
- ▌ Pr Author 3 · drmoisanWrite a GitHub-ready pull request body from the canonical PR-context bundle with strict verification and auto-close rules.
- ▌ Epic Plan 4 · drmoisanScope and prepare a multi-feature epic end-to-end before execution for the epic-planner agent - epic-worthiness gate, decomposition, dependency-wave design, complexity assessment, preparation-mode child orchestrator delegations, integration-branch fan-in, and the epic-orchestrator kickoff prompt artifact.
- ▌ Pr Author 4 · drmoisanWrite a GitHub-ready pull request body from the canonical PR-context bundle with strict verification and auto-close rules.
- ▌
- ▌ Orchestrate 3 · drmoisanRoute a repository request through the deterministic orchestration workflow for feature, bug, research, planning, execution, and review handoffs.
- ▌ Review Epic 2 · drmoisanInvoke the epic-review worker to produce epic-audit artifacts for an epic folder.
- ▌ Orchestrate 4 · drmoisanRoute a repository request through the deterministic orchestration workflow for feature, bug, research, planning, execution, and review handoffs.
- ▌