Copilot instructions for fredrikc3-sketch/VibeConfigStarterKit, covering master orchestrator — d365 f&o implementation accelerator, how to operate, layer model, skills index and orchestration (load first).
Use after the requirement profile is complete to translate requirements into deployable configuration files (DMF JSON templates, CSV data files, parameter-settings markdown), produce the cross-module rollout plan and end-to-end test plan, validate completeness, and run the Phase 1 approval gate. Covers Phase 1 Steps…
Use after the Phase 1 approval gate passes to deploy configuration to a Dynamics 365 F&O environment via the Dynamics 365 ERP MCP server. Walks each module in DMF dependency order (010 → 650) through pre-deployment checks, data-entity deployment (Priority 1 — data tools), form-based deployment (Priority 2 — form…
Use after Phase 2 validation passes to generate the Phase 3 HTML deliverable suite under Documentation/html/. Produces seven single-file HTML documents — two narrative reports (rollout-report.html, environment-config.html) plus five interactive dashboards (test-results.html, challenge-journal.html…
Use when you need a file path. Provides the keyword router and DMF dependency rules so any task can find the right module knowledge file (.md), DMF template (.json), or supporting artefact. The full 47-module index and end-to-end process matrix live in the sidecar module-index.md — load that ONLY when you need…
Use at the start of a new D365 F&O project, or when requirements change, to ingest raw requirement documents from the Requirements/ folder, classify each requirement (Standard Config, Data Migration, Parameter Setting, Workflow, Integration, Gap, Clarification), map every requirement to the correct…
Use after deployment to validate the F&O environment by executing every end-to-end business-process test scenario from Documentation/test-scenarios.json start-to-finish (Source-to-Pay, Order-to-Cash, Record-to-Report, etc.). Drives the fix-loop — when a test fails, fix the SOURCE configuration file, re-deploy via the…
Use when interacting with a Dynamics 365 Finance & Operations environment through the Dynamics 365 ERP MCP server — i.e. whenever a data, form, or api MCP tool call is planned. Covers tool selection hierarchy, naming conventions, OData/SQL querying, form navigation, action invocation, prerequisites (feature flag…
⚠️ SUB-AGENT ONLY — never invoke from main context. Invoked by module-fanout from d365-config-builder. Builds ALL configuration artefacts for ONE D365 F&O module during Phase 1.2. The worker reads the assigned module's .md knowledge file and existing DMF template, derives field values from its scoped requirements…
⚠️ SUB-AGENT ONLY — never invoke from main context. Invoked by module-fanout from d365-deployment. Deploys ONE D365 F&O module to a live environment during Phase 2.1. The worker pre-checks upstream state, walks the module's deployment plan (data entities → form config → actions) using the Dynamics 365 ERP MCP server…
Use whenever a phase skill needs to perform repetitive per-module work across multiple D365 F&O modules (config building in Phase 1.2, deployment in Phase 2.1, validation in Phase 2.2). Defines the sub-agent dispatch pattern, the input/output contract every worker must honour, the parallelization rules (parallel…
⚠️ SUB-AGENT ONLY — never invoke from main context. Invoked by module-fanout from d365-validation-testing. Executes the E2E test scenarios touching ONE module's process slice during Phase 2.2. Drives every assigned scenario through the D365 F&O MCP server start-to-finish, captures pass/fail per step, runs the…
Top-level dispatcher for the D365 F&O implementation lifecycle. Use FIRST on any new user request — it classifies the request (Phase 1 analysis, Phase 1 config, Phase 2 deployment, Phase 2 testing, Phase 3 docs, troubleshooting), checks prerequisite gates (e.g. Phase 1 approval before Phase 2), picks the right phase…
Use whenever a challenge, error, workaround, or non-obvious discovery is encountered during ANY phase of D365 F&O work. Captures the issue in ChallengeJournal/challengejournal.json, classifies it (Rule / Discovery / Gap / Sequence), routes the insight to the correct destination (module .md file, DMF template, or…
Use as a HARD GATE at the start of Phase 1.1 (and any time new files arrive in Requirements/) to validate that every source document can actually be read and that the extracted content is sufficient. Detects encrypted/password-protected files, corrupt files, scanned-image PDFs that need OCR, empty or suspiciously…