メニュー
Post-analysis learning and process improvement. Use when completing major analysis projects, documenting lessons learned, or improving team analytical practices.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create standardized metadata for data assets. Use when documenting new datasets, building data catalogs, improving data discoverability, or creating data dictionaries for teams.
Structure analysis approach before starting work. Use when receiving new analysis requests, breaking down complex questions into steps, or planning iterative analysis workflows.
Comprehensive data quality assessment against business rules, schema constraints, and freshness expectations. Activate when validating production pipelines, onboarding new data sources, or when stakeholders report data quality concerns.
Identify distinct customer or user segments based on behavior, attributes, or value. Activate when you need to answer "who are our best customers?" or "what distinct groups exist in our user base?" and need data-driven profiles to inform strategy.
Create effective, publication-ready data visualizations. Use when choosing chart types, designing presentation visuals, building dashboard charts, or applying visual design best practices to data output.
Create a clear, transparent explanation of analytical methodology for any audience level. Activate when you deliver findings that require the audience to trust the method — A/B tests, attribution models, forecasts, statistical analyses, or anything where "how did you get that?" is a likely question.
| name | analysis-retrospective |
| description | Post-analysis learning and process improvement. Use when completing major analysis projects, documenting lessons learned, or improving team analytical practices. |
Within one week of completing a significant analysis project — while the details are still fresh. Also use after an analysis that went wrong (late delivery, stakeholder rejection, data error discovered post-delivery) to prevent recurrence. Run team retros quarterly even without a specific incident.
references/retro_frameworks.md to stay focused (Start/Stop/Continue or 4Ls: Liked/Lacked/Learned/Longed for).references/learning_capture.md to decide which learnings belong in: templates, reference docs, checklists, or team norms.assets/retrospective_template.md with owners and due dates; log durable learnings in assets/learnings_log_template.md.retrospective_template.md) with what-went-well, issues, root causes, and action itemslearnings_log_template.md) for reusable insights