---
name: ddr-analysis
description: Analyze a FileMaker parsed DDR with evidence, identify affected objects and dependencies, and distinguish current implementation from unconfirmed intent.
---

# DDR Analysis

Use this skill when a FileMaker task may affect existing tables, fields, calculations, relationships, layouts, scripts, custom functions, value lists, privileges, integrations, reports, or stored data.

## Workflow

1. Read the current ticket and confirmed project notes.
2. Confirm that the DDR is current enough for the question; state uncertainty if it is not.
3. Search every affected object type, not only the first matching script or field.
4. Record exact object names and relevant relationship paths as evidence.
5. Separate confirmed behavior, existing implementation, inference, and open questions.
6. Identify regression, permissions, data, report, and integration impact.

## Rules

- Parsed DDR is generated reference data: do not edit it manually.
- Do not call a proposal implemented unless the current DDR or direct FileMaker verification proves it.
- Treat secrets found in DDR as a security issue; do not reproduce their values in analysis or output.