Data Analysis
Operating contract
- Identify the requested deliverable, then select exactly one atomic task below.
- Read that task file completely before acting.
- Read references/lifecycle-standard.md and use the task's profile, risk tier and execution path.
- Load only the company context and adapter references needed for the selected task.
- On a cross-role handoff, compare logical ID and SHA-256 in
references/shared-reference-manifest.json; reuse an already loaded shared reference when both match instead of loading its duplicate.
- Inspect real artifacts and systems before making change-sensitive claims.
- Apply Definition of Ready, stage gates, test strategy, Definition of Done, approval and handoff requirements.
- Do not invent access, approvals, successful execution, test results or business confirmation.
- For any Git-backed mutation, regardless of the task's verb or profile, require a pre-change success/scope contract, a post-change
core-audit-change-scope, and fresh core-verify-deliverable evidence before completion.
- For learning, coaching or skill-transition work, resolve the learner-memory interoperability contract. Reuse only relevant verified summaries; never infer mastery from exposure, and expand stale, uncertain, changed-version or safety-critical prerequisites.
Analysis-rigor routing
- Profile a dataset before deeper analysis ->
da-run-programmatic-eda.
- Explain existing SQL as sources, joins, filters, grain, aggregations and business meaning ->
da-explain-sql-business-logic.
- Explain data, method, assumptions, uncertainty and limitations for a specific audience ->
da-explain-analysis-methodology.
- Independently challenge a completed analysis before delivery ->
da-run-analysis-peer-review.
- Learn from plan-versus-actual evidence after delivery and assign improvement actions ->
da-run-analysis-retrospective.
Peer review decides whether an analysis is fit to deliver. Retrospective improves the process after the work; it does not retroactively waive failed review checks.
Stack-native adapter routing
After selecting the task, detect the real stack/version and read only the matching adapter below plus the adapter index. Do not load every adapter.
- snowflake
- bigquery
- databricks
- microsoft-fabric
Atomic task routing
- Plan, define, design, map, specify or create a proposed artifact (8 tasks): read references/catalog-plan-design.md.
- Build, implement, configure, teach, interview or deliver an artifact (9 tasks): read references/catalog-build-deliver.md.
- Inspect, analyze, test, review, validate, assess, certify or audit (10 tasks): read references/catalog-test-assure.md.
- Deploy, release, monitor, recover, migrate, optimize, retire or improve (2 tasks): read references/catalog-operate-improve.md.
Read only the best-matching catalog. If intent remains ambiguous, inspect a second catalog; do not load all catalogs by default. Select one task by primary deliverable, then read its contract completely.
Completion response
State the selected task ID, primary deliverable, evidence inspected, validation performed, approval status, residual risks and next owner. A draft or plan is not an executed production outcome.
1---2name: data-analysis3description: Perform programmatic EDA, reproducible analysis, SQL-to-business explanation, methodology communication, peer review and retrospective. Use for Data Analyst requests involving datasets, SQL, statistics, insights or analytical quality.4---56# Data Analysis78## Operating contract9101. Identify the requested deliverable, then select exactly one atomic task below.112. Read that task file completely before acting.123. Read [references/lifecycle-standard.md](references/lifecycle-standard.md) and use the task's profile, risk tier and execution path.134. Load only the company context and adapter references needed for the selected task.145. On a cross-role handoff, compare logical ID and SHA-256 in `references/shared-reference-manifest.json`; reuse an already loaded shared reference when both match instead of loading its duplicate.156. Inspect real artifacts and systems before making change-sensitive claims.167. Apply Definition of Ready, stage gates, test strategy, Definition of Done, approval and handoff requirements.178. Do not invent access, approvals, successful execution, test results or business confirmation.189. For any Git-backed mutation, regardless of the task's verb or profile, require a pre-change success/scope contract, a post-change `core-audit-change-scope`, and fresh `core-verify-deliverable` evidence before completion.1910. For learning, coaching or skill-transition work, resolve [the learner-memory interoperability contract](references/learning-memory-interoperability.md). Reuse only relevant verified summaries; never infer mastery from exposure, and expand stale, uncertain, changed-version or safety-critical prerequisites.2021## Analysis-rigor routing2223- Profile a dataset before deeper analysis -> `da-run-programmatic-eda`.24- Explain existing SQL as sources, joins, filters, grain, aggregations and business meaning -> `da-explain-sql-business-logic`.25- Explain data, method, assumptions, uncertainty and limitations for a specific audience -> `da-explain-analysis-methodology`.26- Independently challenge a completed analysis before delivery -> `da-run-analysis-peer-review`.27- Learn from plan-versus-actual evidence after delivery and assign improvement actions -> `da-run-analysis-retrospective`.2829Peer review decides whether an analysis is fit to deliver. Retrospective improves the process after the work; it does not retroactively waive failed review checks.303132## Stack-native adapter routing3334After selecting the task, detect the real stack/version and read only the matching adapter below plus [the adapter index](references/technology-adapters.md). Do not load every adapter.3536- [snowflake](references/adapter-snowflake.md)37- [bigquery](references/adapter-bigquery.md)38- [databricks](references/adapter-databricks.md)39- [microsoft-fabric](references/adapter-microsoft-fabric.md)4041## Atomic task routing4243- **Plan, define, design, map, specify or create a proposed artifact** (8 tasks): read [references/catalog-plan-design.md](references/catalog-plan-design.md).44- **Build, implement, configure, teach, interview or deliver an artifact** (9 tasks): read [references/catalog-build-deliver.md](references/catalog-build-deliver.md).45- **Inspect, analyze, test, review, validate, assess, certify or audit** (10 tasks): read [references/catalog-test-assure.md](references/catalog-test-assure.md).46- **Deploy, release, monitor, recover, migrate, optimize, retire or improve** (2 tasks): read [references/catalog-operate-improve.md](references/catalog-operate-improve.md).4748Read only the best-matching catalog. If intent remains ambiguous, inspect a second catalog; do not load all catalogs by default. Select one task by primary deliverable, then read its contract completely.4950## Completion response5152State the selected task ID, primary deliverable, evidence inspected, validation performed, approval status, residual risks and next owner. A draft or plan is not an executed production outcome.
kina2711