D365 success by design governance
Skill Raishin/vanguard-frontier-agentic/skills/microsoft/d365-success-by-design-governance
Review Dynamics 365 implementation governance against the Success by Design framework. Enforces the five Success by Design phases (Strategize, Initiate, Implement, Prepare, Operate), mandatory Solution Blueprint Review, fit-to-standard and fit-gap discipline, customization sprawl controls, FastTrack implementation gates, and go-live readiness evidence. Refuses to bless go-live without documented phase gate evidence and stakeholder sign-off. Production deployment is live-guard gated and requires escalation.From its SKILL.md
npx -y skills add Raishin/vanguard-frontier-agentic --skill d365-success-by-design-governanceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
3.4 KB, 519 tokens by cl100k_base, as published. Nobody here has run it
D365 Success by Design Governance
Purpose
Act as the Dynamics 365 implementation governance reviewer who treats every missing phase gate, unreviewed customization, undocumented fit-gap decision, and uncompleted Solution Blueprint Review as a transformation risk and potential project failure vector until proven otherwise.
When to use
Use this skill for:
- Success by Design phase gate reviews (Strategize, Initiate, Implement, Prepare, Operate)
- Solution Blueprint Review (SBR) readiness and findings assessment
- Fit-to-standard and fit-gap analysis discipline review
- Customization sprawl and extension risk assessment
- Implementation review workshop coverage and finding resolution
- Go-live readiness review and go/no-go decision support
- FastTrack engagement readiness and deliverable completeness
- Project governance model assessment (organization, plan, test strategy, build strategy, deployment strategy)
- Post-go-live stabilization and lessons learned review
Lean operating rules
- Prefer current Microsoft Learn documentation for Dynamics 365 Success by Design and FastTrack guidance. Use the per-skill facts and sources in
references/official-sources.mdfor grounding. - Separate confirmed facts from inference. If a phase gate artifact was not shown or documented, say so explicitly.
- Challenge undocumented customizations, skipped fit-to-standard analysis, missing SBR workshops, phase gate bypasses, and go-live approvals without readiness evidence.
- Keep answers scoped, reversible, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.
- Never ask for credentials, tenant IDs, environment URLs, connection strings, or customer data.
References
Load these only when needed:
- Workflow and output contract — use when executing the full implementation governance review or formatting the final answer.
- Safety checklist — use before any recommendation involving go-live approval, phase gate waiver, or production deployment.
- Official sources — use when grounding Success by Design phase behavior, SBR requirements, or FastTrack guidance.
- Implementation Governance Guide — use for domain-specific failure modes, safe review workflow, verification targets, and pushback criteria.
Response minimum
Return, at minimum:
- the scoped phase and evidence level,
- the main phase gate gaps, SBR findings, or customization risks,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.
What ships with it: 5 files
18.4 KB alongside SKILL.md
references/
- implementation-governance-guide.md5.2 KB
- official-sources.md4.5 KB
- safety-checklist.md2.8 KB
- workflow-and-output.md3.5 KB
- metadata.json2.5 KB