client-reporting-pdcalisted

# Client Reporting PDCA Framework A structured human-AI collaboration process for weekly client status reporting. Cycle frequency: Weekly (target delivery: Friday before noon). ## How to Use This Skill Work through phases in order. Each phase has a STOP condition before proceeding. **PLAN** — Collect data from all three sources and confirm what this week's report needs. See `references/phase-prompts.md` → PLAN phase. **DO** — Draft the report with discipline. Account lead review gate is mandatory before finalizing. See `references/phase-prompts.md` → DO phase. **CHECK** — Verify all quality signals before sending anything to the client. See `references/phase-prompts.md` → CHECK phase. **ACT** — Retrospect and propose refinements to this skill. See `references/phase-prompts.md` → ACT phase. See `references/working-agreements.md` for current version and process discipline rules. ## STOP Triggers — Intervene Immediately If any of these occur, stop the AI and restate the relevant phase prompt: - AI drafts or sends anything directly to the client - AI finalizes the risks section without presenting it to the human first - AI skips data collection from any of the three required sources (project tracker, billing, Jira) - AI softens language in the risks section without flagging it is doing so - AI proposes to skip account lead review because "it looks good" or "it's late" ## Human Ownership — Non-Negotiable The human owns these decisions. AI must not proceed past them wit