designing-analytics-projects

Create an Analytics Project Brief defining problem, metrics, stakeholders, and methodology.

1|1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/b0glarka/la-wildfire-vulnerability-index --skill designing-analytics-projects
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: designing-analytics-projects
Source: https://github.com/b0glarka/la-wildfire-vulnerability-index/tree/main/.claude/skills/designing-analytics-projects
Command: npx skills add https://github.com/b0glarka/la-wildfire-vulnerability-index --skill designing-analytics-projects

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting a clear Analytics Project Brief helps teams scope, align, and de-risk analytics work before any code or models are built. It captures the problem, stakeholders, metrics, guardrails, and success criteria in a single, shareable artifact.

Core Features & Use Cases

  • Structured, one-page brief that defines Problem, Metrics, Counter-Metrics, Stakeholder Map, Methodology, Scope & Deliverables, Risk & Assumptions, Ethics & Privacy, and Pre-Mortem.
  • Includes templates and examples (e.g., analytics_project_brief.md and snippets/brief_template.md) to ensure consistency and prevent scope creep.
  • Useful for drafting, reviewing, or critiquing analytics projects across teams and domains, and for onboarding stakeholders.

Quick Start

Open the analytics project brief template and draft a scoped brief for your scenario.

Frequently Asked Questions about designing-analytics-projects

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an analytics project brief and why do I need one?▼

An analytics project brief scopes, aligns, and de-risks your work before any code is built by capturing the problem, metrics, stakeholders, and guardrails in a single shareable artifact to prevent scope creep.

How do I scope an analytics project to prevent scope creep?▼

Scope an analytics project by mapping stakeholders, defining counter-metrics, and running a pre-mortem using a structured brief template that establishes clear guardrails and success criteria before analysis begins.

How do I write a pre-mortem for a data analytics project?▼

Write a pre-mortem for a data analytics project by identifying risks and assumptions within a structured project brief, ensuring ethics, privacy constraints, and methodology are evaluated before executing any analysis.

Can I use this analytics brief template for onboarding stakeholders?▼

Yes, you can use the analytics brief template for onboarding stakeholders because it provides a structured one-page overview of the problem, methodology, scope, and deliverables across teams and domains.

What should be included in a data analytics project scope document?▼

A data analytics project scope document should include the problem definition, metrics, counter-metrics, stakeholder map, methodology, scope and deliverables, risk and assumptions, ethics and privacy, and a pre-mortem.

When should I draft an analytics project brief?▼

Draft an analytics project brief before any code or models are built, applying it during scoping, reviewing, or critiquing analytics projects to align teams and establish guardrails early.