identify-drivers

Identify 6–8 mutually exclusive, collectively exhaustive drivers for an analytical question.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/jordangaston/claude-plugins --skill identify-drivers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: identify-drivers
Source: https://github.com/jordangaston/claude-plugins/tree/main/plugins/head/skills/identify-drivers
Command: npx skills add https://github.com/jordangaston/claude-plugins --skill identify-drivers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps analysts identify the 6–8 categorical drivers that will determine the answer to an analytical question, ensuring a clear, structured problem space.

Core Features & Use Cases

  • Proposes 6–8 drivers that are mutually exclusive and collectively exhaustive.
  • Presents drivers in a table with a concise description and rationale.
  • Supports iterative refinement by accepting user feedback and updating the driver set.
  • Used after an approved analytical question to frame the HEAD Step 2 analysis.

Quick Start

Provide an approved analytical question and then run the driver-definition step to generate the 6–8 drivers.

Frequently Asked Questions about identify-drivers

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

FAQPage Schema
How do I identify mutually exclusive drivers for an analytical question?▼

To identify mutually exclusive drivers, you define 6 to 8 categorical dimensions that collectively exhaust the problem space, ensuring a structured framework for subsequent validation and analysis.

What is the best way to structure categorical dimensions for decision support analysis?▼

The best way to structure categorical dimensions is generating a table of 6 to 8 drivers with concise descriptions and rationales, allowing iterative refinement through user feedback to shape the analytical answer.

How many drivers should I define to frame a HEAD framework analysis?▼

You should define 6 to 8 drivers to frame a HEAD framework analysis, as this range provides a mutually exclusive and collectively exhaustive structure to guide the Step 2 validation process.

Do I need an approved analytical question before defining categorical drivers?▼

Yes, you need an approved analytical question and a defined scope before defining categorical drivers, as these prerequisites are required to produce a coherent driver set for structuring the problem space.

Can I refine the proposed categorical dimensions after the initial generation?▼

Yes, you can refine the proposed categorical dimensions after generation by providing user feedback, which updates the driver set to ensure the 6 to 8 identified drivers accurately shape the analytical answer.