vankayalapatin/d365fo-agents
AI agents for Dynamics 365 Finance & Operations (D365 F&O): ticket → fit-gap → FDD → TDD → X++ → review → QA/UAT. Finance and supply chain analysts, an architect, security and reporting specialists, a developer, a reviewer and QA, on top of d365fo-mcp-server. Security & licensing built in.
D365 F&O solution architect and orchestrator. Start here with a business ticket (pasted ADO text, however vague), written requirements or an FDD from another team, a clear small change that names what to build, a field-only change, a "task:" whose design is your own request (developer only), or just a question to explore. Picks the start point, runs the finance, supply chain and security assessments or a gap check, writes the functional design (FDD) and technical design (TDD) for sign-off, then runs the developer (in the background, taking the user's new input mid-build), reviewer and QA until the change is accepted. Explore and FDD work also run on Microsoft Learn alone when the MCP server is not connected. Writes no code itself.
Rules from the shared d365fo standards that only d365fo-architect needs: recording sign-offs, background runs, choice forms and using the user's answers.
The ten D365 F&O engineering standards (S1–S10) every design, change and review must meet — config over hardcoding, reversibility, extensions only, labels, EDTs and naming, SysOperation, set-based and transaction-safe data access, security per entry point, BP clean and tested, grounded in real metadata. Use when designing, writing or reviewing X++.
Finance impact checklist for D365 F&O changes — general ledger, posting, dimensions, AP, AR, tax, cash and bank, fixed assets, budgeting, intercompany, currency, period close, audit. Use in the finance functional agent.
How a d365fo functional agent turns a vague business ticket into a grounded fit-gap and impact assessment — standard-first ladder, cross-module areas, how to ask questions, and what counts as evidence. Use in the finance and supply chain functional agents.
How every d365fo agent reads the workspace, environment and real metadata through the d365fo MCP server before making any claim, what to do when a tool is missing or fails, and how analysis work runs on Microsoft Learn alone when the server is not connected. Use at the start of every d365fo agent run.
Rules for changing D365 F&O SSRS reports and business documents — when not to use SSRS, reading large reports safely, choosing between dataset extension, custom design and menu item redirect, duplicating standard reports, Print management, and the split between what agents write and what a developer does in Report Designer. Use when a ticket touches a report or printed document.
Supply chain impact checklist for D365 F&O changes — procurement, sales, pricing, product information, inventory, costing, warehouse, transportation, production, planning, quality. Use in the supply chain functional agent.
Rules for designing D365 F&O security changes — reading current coverage, mapping personas to roles, choosing the smallest change (privilege, duty or role extension), license impact, segregation of duties, data security and the limits of what the AOT shows. Use in the security agent and when writing or reviewing the TDD security section.
File templates the d365fo agents fill in: analysis, assessment, FDD, TDD, task card, changes, build log, review and QA. Use whenever a d365fo agent creates or updates a work file.
The shared protocol for the d365fo agent team — where the ticket, assessments, FDD, TDD and review files live, the IDs that trace requirements from ticket to test, sign-off gates, loop limits, and the status line every agent ends with. Use in every d365fo agent run.