| name | d365-requirements-analysis |
| description | 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 module/entity/feature, and produce `Documentation/requirement-profile.md` and `Documentation/requirement-matrix.json`. This is Phase 1 Step 1.1 of the implementation lifecycle. |
Requirements Analysis (Phase 1.1)
Cardinal rule: Think first, write continuously. No deployment happens until Phase 1 is complete and approved.
Inputs
- All files in
Requirements/ (Word, PDF, Excel, text — anything readable).
- Module knowledge files (use the
d365-knowledge-routing skill to find paths).
Modules/dmf_odata_mapping.json (entity mapping).Business Process/ProcessCatalogue.json (5,767-item APQC tree).
Pre-flight gate (mandatory) — source-document-validator
Before reading any requirement, invoke the source-document-validator skill on the entire Requirements/ folder. That skill writes Documentation/source-document-validation.json and Documentation/source-document-validation.md.
If summary.gateStatus == "blocked" (any document failed extraction — encrypted PDF, password-protected docx, scanned image, corrupt file, etc.), STOP. Surface the blocker list with remediation tips and ask the user to re-supply readable versions. Do not proceed to Step 1 (Ingest) until the gate is open.
This is non-negotiable. Trust in the requirement matrix depends entirely on having read the source documents fully.
Outputs
| Artefact | Location | Format |
|---|
| Requirement Profile | Documentation/requirement-profile.md | Markdown |
| Requirement Matrix | Documentation/requirement-matrix.json | JSON (see schema) |
| Gap Analysis | embedded in profile | Markdown table |
Schema reference: requirement-matrix.schema.json.
Procedure
1. Ingest
Read every file in Requirements/ whose entry in source-document-validation.json shows status ∈ {ok, warning}. Skip any document where the user explicitly waived a blocker, but include the waiver note in the requirement profile so reviewers see the gap. Extract every functional requirement, constraint, and assumption. Identify the business processes being described.
2. Map to D365 capabilities
For each requirement:
- Which module(s) can fulfil it? (use keyword router in
d365-knowledge-routing)
- Which specific entity, parameter, or feature?
- Standard config, data migration, or genuine gap?
3. Classify
| Category | Meaning | Action |
|---|
| ✅ Standard Config | Out-of-box D365 capability | Map to module phase + entity |
| 📦 Data Migration | Requires data load | Map to DMF template + entity |
| ⚙️ Parameter Setting | Form-driven toggle/value | Map to form + field |
| 🔄 Workflow / Process | Workflow or business rule | Map to workflow type + conditions |
| 🔌 Integration | External connection | Map to OData / dual-write / API |
| ⚠️ Gap | No standard capability | Document gap + proposed approach |
| ❓ Clarification | Ambiguous | Flag for user input |
4. Build the requirement profile
Documentation/requirement-profile.md structure:
- Executive summary — scope, modules, timelines.
- Requirement matrix —
ID | Description | Category | Module | Entity | Status.
- Gap analysis — gaps + proposed solutions.
- Assumptions & constraints.
- Open questions for the client.
Continuous-documentation rule
After every mapping decision, update requirement-profile.md immediately. Never batch.
Hand-off
Before signalling Phase 1.2, if any Finance module (GL/AP/AR/FA/Cash/Tax/Budget/Project Accounting/Expense) is in scope, invoke financial-compliance-guard Step A to capture every applicable accounting and regulatory framework (US GAAP, IFRS, SOX, ASC 606, ASC 842, local GAAPs, SAF-T, GoBD, etc.) directly from the customer. Frameworks are recorded in Documentation/compliance-validation.json and referenced throughout subsequent phases. Do not assume frameworks — escalate if the customer cannot answer.
When complete, signal that Phase 1 Step 1.2 (config building) can begin — invoke the d365-config-builder skill.
