client-reporting-pdca
A PDCA skill for weekly client engagement status reporting at a consulting firm. Covers data pull, cross-reference, draft generation, account lead review, and client delivery. Built to ensure risks are never undersold and the review step is never rushed.
When to Use
Invoke this skill each week when preparing a client status report. It applies to any week where you need to pull from TargetProcess, BillQuick, and Jira, write a status report with a risks section, route it through account lead review, and deliver it to the client by Friday noon.
What This Skill Does
- Guides data collection and cross-referencing across three source systems
- Generates a complete draft status report including a fully-specified risks section
- Flags data anomalies and discrepancies for human review before drafting begins
- Enforces four explicit human approval gates before client delivery
- Captures a per-cycle retrospective to improve risk calibration and process timing over time
Human Responsibilities (Non-Delegable)
- Interpreting data anomalies that exceed the 10% threshold
- Confirming every High-severity risk before it enters the draft
- Approving the complete draft before it goes to the account lead
- Incorporating the account lead's review comments
- Final approval and clicking Send to the client
AI Responsibilities
- Structuring raw CSV exports and Jira ticket lists into formatted tables
- Generating first-draft risks section with severity, mitigation, and owner for each risk
- Drafting accomplishments and upcoming milestones sections from Jira data
- Flagging discrepancies between TargetProcess, BillQuick, and Jira
- Drafting the review-request email to the account lead
- Formatting the final report consistently for client delivery
Workflow Overview
PLAN — Data collection checklist and anomaly review (Tuesday AM)
DO — Draft generation: metrics table, risks section, exec summary (Tuesday PM)
CHECK — Account lead review loop and feedback incorporation (Wednesday–Thursday)
ACT — Final approval, delivery, and cycle retrospective (Friday)
Four Mandatory Gates
| Gate | When | Who | What |
|---|---|---|---|
| 1 | Tuesday PM | Human | Reviews AI-flagged anomalies; authorizes drafting |
| 2 | Wednesday AM | Human | Approves complete draft; authorizes review request to Sarah |
| 3 | Thursday PM | Human | Confirms Sarah's feedback is incorporated; report is final |
| 4 | Friday 10am | Human | Final approval before client send |
Reference Files
references/working-agreements.md— Division of labor, escalation rules, non-negotiablesreferences/phase-prompts.md— Prompts for each PDCA phasereferences/quality-gates.md— Gate criteria, pass/fail conditions, and retro format
Anti-Patterns
- Sending the report before Gate 4 is explicitly passed
- Accepting a risks section with zero entries — every engagement has risks
- Writing risks as "monitoring situation" without mitigation action and named owner
- Letting Sarah's review window shrink below 24 hours
- Including sprint jargon or acronyms in the executive summary
Version
v1.0.0 — Generated by pdca-scaffold from discovery session 2026-05-05