القائمة
Complete customer-base audit orchestrator -- runs all lenses with parallel sub-agents and review
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Turn completed audit outputs into an executive-ready document (Word/PDF) organized by insight, not by lens -- Pyramid Principle, SCQA, action titles, embedded exhibits
Lens 4 -- Compare two acquisition cohorts side-by-side using left-aligned analysis
Lens 3 -- Track a single cohort's behavior over time (activity, frequency, value decay)
Lens 5 -- Assess overall customer base health via C3 chart, acquisition flow, and repeat rates
Lens 1 -- Analyze customer heterogeneity via profit decomposition, distributions, and deciles
Load, validate, and aggregate transaction data for customer-base audit
| name | full-audit |
| description | Complete customer-base audit orchestrator -- runs all lenses with parallel sub-agents and review |
Invoke this skill to run a complete customer-base audit from raw data to final report. This is the top-level orchestrator that coordinates all other CBA skills.
./audit_output/)Invoke customer-base-audit:data-prep and wait for completion. All subsequent stages depend on prepared data. If quality gates fail with errors, stop the entire audit and report to the user.
Outputs: prepared_data.parquet, customer_summary.parquet, period labels, cohort assignments.
Launch sub-agents in parallel, one for each lens:
Each sub-agent works independently on the shared prepared data. Wait for all to complete.
Invoke customer-base-audit:review to validate cross-lens consistency, verify arithmetic identities, scan for pitfalls, and check completeness. If critical inconsistencies are found, flag them prominently in the final report.
Write the final audit report directly in markdown. Structure:
# Customer-Base Audit: [Company Name]
## Executive Summary
Answer the key questions from ${CLAUDE_PLUGIN_ROOT}/references/executive_questions.md:
- How many active customers? Is it growing or shrinking?
- How concentrated is value? (top decile share)
- Is customer quality improving or declining? (cohort comparison)
- Where is profit coming from? (C3 chart interpretation)
- What is the product dimension story? (if applicable)
## Validation Summary
**Status: PASSED/FAILED**
[Include any cross-check failures, pattern flags, or pitfall warnings]
## Lens 1: Customer Heterogeneity
[Decomposition table, distribution charts, decile analysis, key findings]
## Lens 2: Period Comparison
[Segment analysis, migration matrix, up-down analysis, key findings]
## Lens 3: Cohort Evolution
[Activity decay, buying patterns, time-to-nth, key findings]
## Lens 4: Cohort Comparison
[Left-aligned charts, 2nd purchase CDF comparison, key findings]
## Lens 5: Customer Base Health
[C3 chart, acquisition flow, repeat rates, key findings]
## Product Dimension
[Category decomposition, co-purchasing, sole buyers, entry categories]
## Recommended Actions
[3-5 actionable recommendations based on findings]
Invoke customer-base-audit:executive-report to produce the stakeholder-facing deliverable. The markdown report from Stage 4 is the analytical record; executives get a separate document organized by insight (Pyramid Principle, action titles, 6–8 embedded exhibits) rather than by lens. Output: executive_report.docx (or .pdf).
When the user does not specify parameters:
All results saved to the output directory:
executive_report.docx (or .pdf) -- insight-organized executive deliverable with embedded exhibitsaudit_report.md -- final synthesis report (analytical record, lens-by-lens)validation_report.md -- cross-lens validation results${CLAUDE_PLUGIN_ROOT}/references/methodology.md -- audit methodology and definitions${CLAUDE_PLUGIN_ROOT}/references/expected_patterns.md -- expected patterns and benchmarks${CLAUDE_PLUGIN_ROOT}/references/common_pitfalls.md -- known pitfalls to avoid${CLAUDE_PLUGIN_ROOT}/references/executive_questions.md -- key questions the audit should answer