# Management Report Generator

> Generate executive and change-control reports for AX 2012 performance findings with risk, impact, evidence, recommendations, and audit-ready action plans.

- Skill: `rweisssieker-xp/management-report-generator` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rweisssieker-xp/management-report-generator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rweisssieker-xp/management-report-generator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: rweisssieker-xp (https://skillmd.com/u/rweisssieker-xp)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rweisssieker-xp/management-report-generator

---


# Management Report Generator

Use this skill to turn technical AX/SQL performance findings into management summaries, change proposals, and regulated-environment documentation.

## Report Structure

- Executive summary: health score, top risks, business impact, and recommended decision.
- Top findings: ranked by impact, urgency, confidence, and implementation risk.
- Evidence summary: data sources, time windows, and measurement limitations.
- Action plan: owner, effort, risk, expected effect, validation metric, rollback option, and change category.
- Before/after section: baseline, post-change result, measured delta, and conclusion.
- Migration signal section: issues that are symptoms of structural legacy constraints rather than isolated tuning problems.
- Performance debt register: recurring open findings, age, owner, deferred risk, and next decision.
- SLA forecast: processes likely to breach target windows and the expected breach horizon.
- Environment drift section: why production behavior differs from test/pre-production.
- Ownership routing: business owner, technical owner, support queue, or vendor.
- Appendix: detailed SQL/AX evidence for technical reviewers.

## Executive Metrics

Use these metrics when evidence exists:

- Overall performance score.
- Number of critical/high findings.
- Batch SLA adherence.
- Top wait categories.
- Top business processes at risk.
- Change backlog by risk and effort.
- Improvement after implemented changes.
- Deferred-risk statement for unresolved findings.
- Module-specific health scores.
- SLA breach prediction count.
- Performance debt age and recurrence.
- Capacity-planning signals.
- Deployment regression count.

## Tone

Use clear business language. Avoid hiding uncertainty. Distinguish observed facts, likely causes, and recommendations.

## GxP / ITIL Considerations

- State that recommendations are advisory and require approval before implementation.
- Include audit trail references to the source exports and analysis timestamp.
- For each change, include risk assessment, test evidence needed, rollback guidance, and post-change monitoring criteria.
- Separate low-risk operational changes from validated changes requiring CAB, QA, or business-process owner approval.
- Preserve uncertainty: use "observed", "correlates with", "likely", and "requires validation" accurately.

## Finding Narrative Template

Use this structure for each management-facing finding:

- What happened.
- Why it matters.
- Evidence behind the conclusion.
- Recommended decision.
- Risk if deferred.
- Risk if implemented.
- Validation and rollback.

## Recommendation Modes

Use the requested mode explicitly:

- Observe only: summarize evidence and risks without recommendations requiring action.
- Advisory: produce findings and candidate actions.
- Change proposal: include owner, risk, approval path, test plan, validation, and rollback.
- CAB package: include evidence pack references, audit trail, implementation plan, validation criteria, and approval narrative.
- Post-change validation: compare baseline and post-change results, then state improved, unchanged, regressed, or inconclusive.