drmoisan
- 411 skills
- 0 followers
- 2 days ago last updated
- ▌ Initialize Discovery Workspace 2 · drmoisanInitialize or explicitly configure a discovery workspace through root-owned operations before constrained review. Use when asked to bootstrap a discovery workspace or preview its initial structure.
- ▌ Initialize Discovery Workspace 3 · drmoisanInitialize or explicitly configure a discovery workspace through root-owned operations before constrained review. Use when asked to bootstrap a discovery workspace or preview its initial structure.
- ▌ Adjudicate Unspecified Behavior · drmoisanDraft traceable proposals for unresolved behavior and separate them from root-owned approval. Use when asked to adjudicate contradictory or undocumented behavior and derive explicitly requested acceptance criteria.
- ▌ Adjudicate Unspecified Behavior 2 · drmoisanDraft traceable proposals for unresolved behavior and separate them from root-owned approval. Use when asked to adjudicate contradictory or undocumented behavior and derive explicitly requested acceptance criteria.
- ▌ Adjudicate Unspecified Behavior 3 · drmoisanDraft traceable proposals for unresolved behavior and separate them from root-owned approval. Use when asked to adjudicate contradictory or undocumented behavior and derive explicitly requested acceptance criteria.
- ▌ Discovery Behavior Reconciliation 3 · drmoisanDispatch unresolved behavior to canonical proposal and root-approval handling. Use when invoking the existing behavior-reconciliation alias.
- ▌ Discovery Runtime Characterization 3 · drmoisanDispatch runtime characterization to its canonical supplied-evidence workflow. Use when invoking the existing runtime-characterization alias.
- ▌ Remediation Handoff Atomic Planner 11 · drmoisanReusable remediation trigger and atomic_planner handoff steps. Use when audits require remediation inputs and a delegated remediation plan.
- ▌ Evidence And Timestamp Conventions 12 · 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.
- ▌ Extract Feature Contract 2 · drmoisanExtract evidence-backed feature contracts for selected legacy components and record unresolved behavior. Use when asked to document a feature contract from source, tests, documentation and supplied evidence.
- ▌ Extract Feature Contract 3 · drmoisanExtract evidence-backed feature contracts for selected legacy components and record unresolved behavior. Use when asked to document a feature contract from source, tests, documentation and supplied evidence.
- ▌ Discovery Coverage Ledger 3 · drmoisanDispatch explicit inventory, extraction or review without mixing coverage ownership. Use when invoking the existing coverage-ledger alias with action=inventory, extract or review.
- ▌ Review Discovery Coverage · drmoisanReview selected discovery coverage and parity with authoritative reports and explicit findings. Use when asked for a structural, discovery-complete or parity-complete review.
- ▌ Translate Claude To Codex 3 · drmoisanTranslate the native Claude Code runtime, including Claude rules, skills, agents, hooks, and settings, into the native Codex ecosystem. Preserve mechanical enforceability, diff against existing Codex state, produce an approval plan with an enforceability ledger, then apply it.
- ▌ Review Discovery Coverage 2 · drmoisanReview selected discovery coverage and parity with authoritative reports and explicit findings. Use when asked for a structural, discovery-complete or parity-complete review.
- ▌ Review Discovery Coverage 3 · drmoisanReview selected discovery coverage and parity with authoritative reports and explicit findings. Use when asked for a structural, discovery-complete or parity-complete review.
- ▌ Csharp Change Budget Router 9 · drmoisanBudget-first routing contract for C# work: estimate production-file scope, choose small vs large path, enforce orchestration-first routing for larger changes, and use the VS Code extension command surface for promotion lifecycle steps when available.
- ▌ Feature Promotion Lifecycle 11 · drmoisanDeterministic promotion workflow from potential feature/bug entry to issue, branch, active feature folder, and downstream spec/research handoffs. Agent sessions must use the drm-copilot MCP tool surface and record raw promotion receipts under the canonical checkpoint namespace.
- ▌ Policy Audit Template Usage 7 · drmoisanPolicy audit template usage and output requirements. Use when creating timestamped policy-audit artifacts from the repository templates.
- ▌ Discovery Validate Artifacts 3 · drmoisanDispatch artifact validation to the canonical explicit-kind and mode workflow. Use when invoking the existing validate-artifacts alias.
- ▌ Validate Discovery Artifacts · drmoisanValidate an exact discovery artifact selection or configured graph through authoritative modes. Use when asked to validate discovery artifacts or evaluate an explicit completion or planning prerequisite.
- ▌ Validate Discovery Artifacts 2 · drmoisanValidate an exact discovery artifact selection or configured graph through authoritative modes. Use when asked to validate discovery artifacts or evaluate an explicit completion or planning prerequisite.
- ▌ Validate Discovery Artifacts 3 · drmoisanValidate an exact discovery artifact selection or configured graph through authoritative modes. Use when asked to validate discovery artifacts or evaluate an explicit completion or planning prerequisite.
- ▌ Characterize Runtime Behavior · drmoisanDescribe selected runtime scenarios from supplied captures or honest manual plans. Use when asked to characterize legacy behavior, record runtime evidence or prepare not-run and blocked scenarios.
- ▌ Generate Acceptance Scenarios · drmoisanGenerate traceable acceptance specifications, eligible views and explicit pending material. Use when asked to derive acceptance scenarios from confirmed contracts and approved decisions.
- ▌ Characterize Runtime Behavior 2 · drmoisanDescribe selected runtime scenarios from supplied captures or honest manual plans. Use when asked to characterize legacy behavior, record runtime evidence or prepare not-run and blocked scenarios.
- ▌ Generate Acceptance Scenarios 2 · drmoisanGenerate traceable acceptance specifications, eligible views and explicit pending material. Use when asked to derive acceptance scenarios from confirmed contracts and approved decisions.
- ▌ Characterize Runtime Behavior 3 · drmoisanDescribe selected runtime scenarios from supplied captures or honest manual plans. Use when asked to characterize legacy behavior, record runtime evidence or prepare not-run and blocked scenarios.
- ▌ Generate Acceptance Scenarios 3 · drmoisanGenerate traceable acceptance specifications, eligible views and explicit pending material. Use when asked to derive acceptance scenarios from confirmed contracts and approved decisions.
- ▌ Initialize Discovery Workspace · drmoisanInitialize or explicitly configure a discovery workspace through root-owned operations before constrained review. Use when asked to bootstrap a discovery workspace or preview its initial structure.
- ▌ Docs Inventory Surface · drmoisanInventory the documented surface of a repository (commands, options, routes, configuration keys, public symbols) through the docs MCP tools. Use as the first step of docs-architect work.
- ▌ Documentation Workflow · drmoisanRun the documentation estate workflow from initialization to docs-complete validation by dispatching the seven docs skills in order. Use when a repository documentation estate must be created, extended or brought to docs-complete.
- ▌ Invoke Csharp Engineer 10 · drmoisanInvoke the csharp-typed-engineer worker to design, implement, and verify C# changes within typed repository boundaries. Applies CSharpier, .NET analyzers, nullable analysis, and MSTest with the one-to-three production-file small-path budget and zero-regression quality gates read from the single gate run and compared with the `Phase 0 baseline`.
- ▌ Invoke Python Engineer 6 · drmoisanInvoke the python-typed-engineer worker to design, implement, and verify Python changes within typed repository boundaries. Applies Black, Ruff, Pyright, and Pytest with a 1-3 production-file direct-mode budget, routing to the orchestrated large path above it, and zero-regression quality gates read from the single gate run and compared with the `Phase 0 baseline`.
- ▌ Docs Inventory Surface 2 · drmoisanInventory the documented surface of a repository (commands, options, routes, configuration keys, public symbols) through the docs MCP tools. Use as the first step of docs-architect work.
- ▌ Documentation Workflow 2 · drmoisanRun the documentation estate workflow from initialization to docs-complete validation by dispatching the seven docs skills in order. Use when a repository documentation estate must be created, extended or brought to docs-complete.
- ▌ Docs Inventory Surface 3 · drmoisanInventory the documented surface of a repository (commands, options, routes, configuration keys, public symbols) through the docs MCP tools. Use as the first step of docs-architect work.
- ▌ Documentation Workflow 3 · drmoisanRun the documentation estate workflow from initialization to docs-complete validation by dispatching the seven docs skills in order. Use when a repository documentation estate must be created, extended or brought to docs-complete.
- ▌ Architecture Boundaries 3 · drmoisanArchitecture boundary enforcement rules for a host-neutral layered architecture.
- ▌ Discovery Parity Matrix 3 · drmoisanDispatch parity reconciliation to the canonical Requirements Reconciler workflow. Use when invoking the existing discovery parity-matrix alias.
- ▌ Docs Reconcile Behavior · drmoisanRecord coverage dispositions, evidence pins and parity dimensions through update_docs_ledger, previewing each change as a dry run first. Use when coverage findings or review judgments must be written to the estate artifacts.
- ▌ Inventory Legacy System · drmoisanInventory selected legacy repository surfaces with explicit analyzer scope and truthful coverage dispositions. Use when asked to inventory a legacy system or refresh selected discovery coverage.
- ▌ Reconcile Parity Matrix · drmoisanReconcile selected feature and client parity against pinned source facts and target evidence. Use when asked to update a parity matrix or identify migration gaps without changing approved decisions.
- ▌ Docs Reconcile Behavior 2 · drmoisanRecord coverage dispositions, evidence pins and parity dimensions through update_docs_ledger, previewing each change as a dry run first. Use when coverage findings or review judgments must be written to the estate artifacts.
- ▌ Inventory Legacy System 2 · drmoisanInventory selected legacy repository surfaces with explicit analyzer scope and truthful coverage dispositions. Use when asked to inventory a legacy system or refresh selected discovery coverage.
- ▌ Reconcile Parity Matrix 2 · drmoisanReconcile selected feature and client parity against pinned source facts and target evidence. Use when asked to update a parity matrix or identify migration gaps without changing approved decisions.
- ▌ Docs Reconcile Behavior 3 · drmoisanRecord coverage dispositions, evidence pins and parity dimensions through update_docs_ledger, previewing each change as a dry run first. Use when coverage findings or review judgments must be written to the estate artifacts.
- ▌ Inventory Legacy System 3 · drmoisanInventory selected legacy repository surfaces with explicit analyzer scope and truthful coverage dispositions. Use when asked to inventory a legacy system or refresh selected discovery coverage.
- ▌ Reconcile Parity Matrix 3 · drmoisanReconcile selected feature and client parity against pinned source facts and target evidence. Use when asked to update a parity matrix or identify migration gaps without changing approved decisions.
- ▌ Discovery Repo Inventory 3 · drmoisanDispatch repository inventory to the canonical legacy inventory workflow. Use when invoking the existing discovery repo-inventory alias.
- ▌ Extract Feature Contract · drmoisanExtract evidence-backed feature contracts for selected legacy components and record unresolved behavior. Use when asked to document a feature contract from source, tests, documentation and supplied evidence.
- ▌ Csharp QA Gate 12 · drmoisanFinal QA gate for C# changes. Runs CSharpier, .NET analyzers, nullable analysis, and MSTest; compares static results and the tests and coverage of the single gate run to the Phase A baseline (the `Phase 0 baseline`), enforces zero-regression deltas, and reports before completion.
- ▌ Python QA Gate 7 · drmoisanFinal QA gate for Python changes. Runs Black, Ruff, Pyright, and Pytest; compares static results and the tests and coverage of the single gate run to the Phase A baseline (the `Phase 0 baseline`), enforces zero-regression deltas, and reports before completion.
- ▌ Research Issue 8 · drmoisanInvestigate the best implementation approach for a feature or bug by analyzing the codebase and external references, then writing structured findings to the applicable tracked research folder.
- ▌ Docs Author Page · drmoisan bundleWrite or revise one documentation page from the template for its Diataxis mode, fill its front matter and link it from its root entry page. Use for every page docs-author writes.
- ▌ Owner Directives · drmoisanOwner-directive relay for coordinators and delegated agents. Use when the repository owner gives the coordinator an instruction that a delegated orchestrator or specialist must act on: record it in the item checkpoint, relay it as a fenced Owner directives block, and record an honored or refused decision for each directive acted on.
- ▌ Docs Author Page 2 · drmoisan bundleWrite or revise one documentation page from the template for its Diataxis mode, fill its front matter and link it from its root entry page. Use for every page docs-author writes.
- ▌ Docs Author Page 3 · drmoisan bundleWrite or revise one documentation page from the template for its Diataxis mode, fill its front matter and link it from its root entry page. Use for every page docs-author writes.
- ▌
- ▌ Bash Command Shape · drmoisanBash command shape for running a tool or reading a file in another directory without chaining cd.
- ▌ Discovery Workflow 3 · drmoisanDispatch an explicit canonical discovery workflow without adding authority. Use when invoking the legacy discovery umbrella with a selected skill_id.
- ▌
- ▌ Docs Review Coverage · drmoisanReview documentation coverage, page accuracy and the surface delta of a branch, read-only. Use before docs-complete validation and during feature review of a change that alters the documented surface.
- ▌ Pr Context Artifacts 6 · drmoisanPR context artifact locations and refresh rules. Use when generating, reading, or inlining pr_context summary/appendix artifacts.
- ▌ Docs Review Coverage 2 · drmoisanReview documentation coverage, page accuracy and the surface delta of a branch, read-only. Use before docs-complete validation and during feature review of a change that alters the documented surface.
- ▌ Epic Progress Report · drmoisan bundlePost recurring epic progress reports from the coordinator session: a five-line TL;DR every 20 minutes and an hourly full status update with a push notification. Progress is measured in plan tasks and typed steps (research, spec, plan, preflight, execution, review, PR, CI, merge, main sync, integration PR); the time remaining is a dependency-aware critical path, list-scheduled under the parallel cap at each feature sequential task velocity, with sequential and aggregate velocity, a range, and the serial sum as the upper bound. Use when an epic or a standalone item is running and the owner wants scheduled progress and time-remaining reports, or when the reports must be started, reset after a pause, moved to a new cadence, stopped, or recreated after a restart.
- ▌ Docs Review Coverage 3 · drmoisanReview documentation coverage, page accuracy and the surface delta of a branch, read-only. Use before docs-complete validation and during feature review of a change that alters the documented surface.
- ▌ Execution Environment 2 · 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, test runtime, and test-isolation checks are known and are not restated in plans.
- ▌
- ▌ Docs Init · drmoisanCreate the documentation estate profile for a repository and validate it. Use from the root session before any other docs skill runs.
- ▌ Docs Init 2 · drmoisanCreate the documentation estate profile for a repository and validate it. Use from the root session before any other docs skill runs.
- ▌ Docs Plan Ia · drmoisanPlan the documentation information architecture: pages, Diataxis modes, audiences and owners. Use after the surface inventory, before any page is written.
- ▌ Docs Plan Ia 2 · drmoisanPlan the documentation information architecture: pages, Diataxis modes, audiences and owners. Use after the surface inventory, before any page is written.
- ▌ Docs Plan Ia 3 · drmoisanPlan the documentation information architecture: pages, Diataxis modes, audiences and owners. Use after the surface inventory, before any page is written.
- ▌ Docs Validate · drmoisanValidate the documentation estate artifacts for one mode and the head revision, read-only; receipt persistence is a root or CI step. Use to establish docs-complete before an integration merge.
- ▌
- ▌ Docs Validate 2 · drmoisanValidate the documentation estate artifacts for one mode and the head revision, read-only; receipt persistence is a root or CI step. Use to establish docs-complete before an integration merge.
- ▌ Docs Validate 3 · drmoisanValidate the documentation estate artifacts for one mode and the head revision, read-only; receipt persistence is a root or CI step. Use to establish docs-complete before an integration merge.
- ▌ Parallel Add · drmoisanAdmit one new item into a running parallel run — preparation via a preparation-mode child orchestrator run, conflict-edge computation against all items including in-flight ones, and the admission decision that either places the item in the current cohort or defers it and recolors the unstarted subgraph. Appends exactly one mutations[] entry. In-flight items are never moved.
- ▌ Parallel Plan · drmoisanPrepare a set of thematically unrelated items for concurrent execution before any execution begins - item intake over issue numbers and potential-entry paths, concurrent preparation-mode child orchestrator delegations, blast-radius computation and V1-V3 validation, cohort seeding with a recomputation-parity check, run-manifest and planner-checkpoint authoring, and the parallel-orchestrator kickoff artifact.
- ▌ Orchestrate 2 · drmoisanRoute a repository request through the deterministic orchestration workflow for feature, bug, research, planning, execution, and review handoffs.
- ▌ Pr Author · drmoisanWrite a GitHub-ready pull request body from the canonical PR-context bundle with strict verification and auto-close rules.
- ▌
- ▌ Orchestrate · drmoisanRoute a repository request through the deterministic orchestration workflow for feature, bug, research, planning, execution, and review handoffs.
- ▌ Epic Plan 2 · 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.
- ▌
- ▌ Epic Run · drmoisanExecute a previously prepared epic by resolving its committed kickoff artifact and delegating it to the Codex epic-orchestrator agent.
- ▌ Epic Plan · drmoisanScope and prepare a multi-feature epic end-to-end before execution through the Codex epic-planner agent.
- ▌ Evidence And Timestamp Conventions · 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 · drmoisanRemediation handoff chain from orchestrator through atomic-planner, atomic-executor, and feature-review. Use when an audit cycle requires a delegated remediation plan, preflight clearance, task-by-task execution, and reaudit.
- ▌ Evidence And Timestamp Conventions 2 · 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.
- ▌ Acceptance Criteria Tracking · drmoisanTrack and check off acceptance criteria in requirement source files (issue.md, spec.md, user-story.md) as they are delivered. Use when executing plans, reviewing features, or validating delivery to keep AC checkboxes current.
- ▌ Powershell Change Budget Router · drmoisanBudget-first routing contract for PowerShell work: estimate production-file scope, choose small vs large path, enforce direct-mode escalation to orchestrator, and use the VS Code extension command surface for promotion lifecycle steps when available.
- ▌ Feature Promotion Lifecycle 2 · drmoisanDeterministic promotion workflow from potential feature/bug entry to issue, branch, active feature folder, and downstream spec/research handoffs. Agent sessions must use the drm-copilot MCP tool surface and record raw promotion receipts under the canonical checkpoint namespace.
- ▌ Invoke Powershell Engineer · drmoisanInvoke the powershell-typed-engineer worker to design, implement, and verify PowerShell changes within typed repository boundaries. Applies PoshQC formatting, analysis, and testing with a one-to-two production-file direct-mode budget and zero-regression quality gates.
- ▌ Orchestrator Workflow · 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.
- ▌ Cleanup Merged Worktrees · drmoisan bundleDetect, consolidate, and delete git worktrees/branches that are fully merged into main; use after an epic or feature's PRs have merged and stale drm-copilot-wt-* branches/worktrees remain, driving the detect -> report -> consolidate -> pr-author handoff -> post-merge deletion workflow.
- ▌ Feature Review Workflow 2 · 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.
- ▌ Parallel Orchestrate · drmoisanExecute a prepared parallel run for the parallel-orchestrator agent — cohort scheduling under a max_concurrency cap, per-item fan-out onto isolated worktrees branched from origin/main, per-item merge to main after durably confirming CI green, worktree cleanup, and the generated parallel-status.md projection. There is no integration branch and no final integration pull request.
- ▌ Pr Context Artifacts · drmoisanPR context artifact locations and refresh rules. Use when generating, reading, or inlining pr_context summary/appendix artifacts.