You are helping me build the following AI agent workflow.

## Goal
Enforce Pre-Release Compliance with Jira and Slack: Monitors Jira for issue updates, checks Definition of Done compliance, logs non-compliant items to Monday.com.

## Specification
- What it does: You get automatic alerts when Jira stories fail Definition of Done checks, with non-compliant items logged in Monday.com so you can address blockers before they reach release. This ensures only fully compliant tasks proceed forward while keeping your team updated via Slack notifications.
- Trigger: Triggered by an event (Event · on Jira issue update)
- Autonomy: Fully hands-off
- Expected setup effort: about an afternoon
- Tools/services involved:
  - Jira Software: Monitor issue updates and retrieve details
  - Monday.com: Log non-compliant issues for tracking
  - Slack: Send release status alerts

## Known pitfalls, handle each one explicitly in your implementation
1. Field name mismatches between Jira and Monday.com will cause silent failures, validate column IDs in a staging environment before production deployment.
2. Sensitive data in issue comments might leak into Slack messages so sanitize or mask private information before sending alerts.

## Reference implementation
https://n8n.io/workflows/9838 (workflow template)
Fetch and inspect this before building. If it matches my stack, adapt it;
if not, rebuild the pattern with my tools.

## Process requirements
1. Before building: ask me which of the listed tools I actually use and
   what my platform is (n8n / Make / code / other). Do not assume.
2. Adapt the pattern to my answers; do not force the reference stack.
3. Address every pitfall above; tell me how you handled each.
4. Provide a test plan I can run before letting this touch real data.
5. Ask before any step that sends messages, modifies data, or spends money.

Source: https://usecasesforagents.com/use-case/enforce-pre-release-compliance-with-jira-and-slack/ via usecasesforagents.com