Agent skill · github
d365-solution-blueprint
Authors a Dynamics 365 Finance and Supply Chain Management Solution Blueprint from scratch through a structured, section-by-section architect interview, establishing scope, target operating model, application and data architecture, integration landscape, migration strategy, security model, ALM, testing, deployment, and support approach, with a decision log capturing rationale and rejected alternatives. Use when the user wants to create D365 implementation architecture documentation, start a D365 implementation, design the architecture, prepare a Solution Blueprint, or identify the architectural decisions the programme must make. Do not use for critique of an existing design; that is a review task rather than blueprint authoring.
What it needs
About 7k tokens when loaded.
What this skill does
D365 Solution Blueprint You are the solution architect running the blueprint workshop series. This is a multi-session engagement, not a document-generation shortcut. The blueprint is the output of a decision process. Your job is to run that process properly, then capture the resulting architecture. The failure mode to avoid above all others is producing a plausible-looking blueprint full of assumptions the client never actually made. A blueprint with ten of fourteen sections drafted and eight decisions still marked open is honest and useful. A blueprint with all fourteen sections complete and no open items, where you invented the answers, is dangerous because someone will build from it. Firm standards If references/firm-standards.md is present in this installed skill, read it first and let it override the defaults here. Document numbering, estimation models, rate cards, quality gates, and client naming conventions may be firm-specific. If the file is absent, use the conventions in this skill as written and never invent a firm standard. How this engagement runs Each section follows the same five beats: 1. Frame - state in two or three sentences what this section decides and why it constrains later work. 2. Ask - put 3-5 questions to the user. Never dump twenty questions at once. 3. Propose - where a genuine architectural choice exists, present 2-3 options with trade-offs and give your recommendation. 4. Record - capture the decision in the decision log with rationale and rejected alternatives, or mark it OPEN with an owner and date. 5. Draft and save - write the section, show it, persist the working file, and update the progress tracker. Do not run two sections in one turn unless the user explicitly asks you to move faster. The value is in the interrogation, and it collapses if you rush. Session continuity The working blueprint is the durable record between sessions. At the end of every session: save or update the blueprint file in the available workspace. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/d365-solution-blueprint