d365-technical-plan-designer
Converts D365 requirements into detailed technical designs, implementation plans, and testing strategies.
Install
mkdir -p .claude/skills/d365-technical-plan-designer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11591" && unzip -o skill.zip -d .claude/skills/d365-technical-plan-designer && rm skill.zipInstalls to .claude/skills/d365-technical-plan-designer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
D365 技术设计与实施计划编排专家（把 spec 转成 plan）Key capabilities
- →Translate requirements into technical design
- →Define front-end and back-end allocation
- →Confirm data models for entities
- →Design security for sensitive fields
- →Outline unit test strategies
How it works
The skill acts as a D365 technical plan designer, converting requirement specifications into an executable technical design and implementation plan. It covers aspects like front-end/back-end allocation, data modeling, and testing strategies.
Inputs & outputs
When to use d365-technical-plan-designer
- →Generate technical plan from D365 spec
- →Define back-end vs front-end logic boundaries
- →Map data models for entities and lookups
About this skill
ROLE
你是 D365 项目的技术计划设计者，负责把需求规格书转成可执行的技术设计与实施计划。
SCENARIO
适用：多模块系统、前后端协作、配置/代码/集成混合交付、性能与安全约束。 不适用：只有单个小改动，不需要完整 plan 的临时任务。
MICROSOFT PRODUCT CAPABILITIES
- D365 & Dataverse：标准能力优先、配置清单（字段/视图/窗体/业务规则）
- Plugin/Custom API：业务逻辑、幂等与异常处理
- JavaScript（Form Script/Ribbon/WebResource）：表单行为、交互
- Power Automate：审批/集成编排/补偿
- Azure（可选）：异步集成、错误补偿、监控
OBJECTIVE
输出 plan.md 风格技术设计：分工、接口、实体关系正确性、性能与安全边界、测试策略。
OUTPUT STRUCTURE（必须）
- 技术边界与系统关系（主系统/从系统/调用方向）
- 前后端分工与落点：Plugin/Custom API/JS/Flow/配置项
- 企业工程分层落点：Plugins / Sdk(Handler) / BLL / WebResource / UnitTest / Deploy
- 数据模型确认：实体类型、查找字段、选项集、审计、主数据归属
- 性能目标与容量假设（并发/队列/Activity/附件）
- 安全设计：敏感字段、共享策略、field security
- 交付产物映射：哪些文件/配置必须更新（例如 registration/webresource/metadata）
- 企业交付约束：配置文件、日志、签名、ILMerge、spkl、多语言资源、包版本策略
- 测试策略：server UT / client UT / integration / UAT
Example Prompts（提问范式）
- “基于 spec 生成 D365 技术设计 plan：前后端分工 + 落点 + 性能/安全约束”
- “帮我做 plan：哪些必须走 Plugin，哪些可以 Flow/JS”
- “输出数据模型确认表：lookup/选项集/审计/归属”
- “把 UT 策略写进 plan（后端 MSTest + 前端 Jest）”
Unit Test Checklist（输出必须包含）
- plan 必须明确：每条需求由谁实现（代码/配置/集成）
- 必须明确：代码落到哪一层，哪些逻辑不能写进入口插件或前端页面
- 必须输出：后端校验/幂等/异常处理策略
- 必须输出：性能与安全限制
- 必须输出：测试入口与覆盖范围
When not to use it
- →When only a single small change is needed
- →When a complete plan is not required for temporary tasks
- →When the project is not D365-related
Limitations
- →Not applicable for single small changes
- →Not applicable for temporary tasks without a full plan
- →Output must follow a specific structure for technical design
How it compares
This skill provides a structured approach to D365 project planning by translating specifications into a detailed technical design, ensuring complete coverage of various aspects unlike an informal planning process.
Compared to similar skills
d365-technical-plan-designer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| d365-technical-plan-designer (this skill) | 0 | 3mo | No flags | Advanced |
| event-store-design | 5 | 2mo | No flags | Advanced |
| event-sourcing-architect | 1 | 4mo | No flags | Advanced |
| moai-domain-backend | 1 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
event-store-design
wshobson
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
event-sourcing-architect
sickn33
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trails, or temporal queries.
moai-domain-backend
modu-ai
Backend development specialist covering API design, database integration, microservices architecture, and modern backend patterns.
messaging-decision
Brilhante29
Decide whether a portfolio repository should use no broker, transactional outbox, RabbitMQ, Kafka/Redpanda, Redis Streams, or NATS based on delivery semantics, ordering, replay, retry/DLQ, throughput, and benchmark evidence.
drizzle-orm
EpicenterHQ
Drizzle ORM patterns for type branding and custom types. Use when working with Drizzle column definitions, branded types, or custom type conversions.
postgresql-table-design
wshobson
Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features