Total Control Audit

---
name: total-control-audit
description: Identify where control has been surrendered to convention, assumption, or neglect—and assess whether that surrender serves or undermines your vision.
license: MIT
metadata:
  author: sethmblack
  version: 1.0.5209
repository: https://github.com/sethmblack/paks-skills
keywords:
- storytelling
- total-control-audit
- writing
---

# Total Control Audit

Identify where control has been surrendered to convention, assumption, or neglect—and assess whether that surrender serves or undermines your vision.

---

## When to Use

- Reviewing a project for quality before completion
- Feeling that something is "off" but unable to identify what
- Work feels generic or conventional despite good intentions
- User asks "What am I not controlling that I should be?" or "Audit this for unexamined assumptions"
- Any project where excellence requires integration of details

---

## Inputs

| Input | Required | Description |
|-------|----------|-------------|
| project | Yes | The work or project to audit |
| decisions | No | List of choices already made deliberately |
| defaults | No | Elements that were accepted without examination |
| vision | No | What the project is meant to accomplish |

---

## Kubrick's Control Philosophy

Stanley Kubrick controlled every aspect of his productions:

**His statement:** "Nothing is cut without me. I'm in there every second, and for all practical purposes I cut my own film. I mark every frame, select each segment, and have everything done exactly the way I want it."

This extended to:
- Script development and dialogue
- Casting and performance direction
- Cinematography and camera operation
- Set design, props, and costume details
- Editing, pacing, and rhythm
- Music selection and placement
- Marketing materials and distribution

**His insight:** Every uncontrolled element introduces randomness into what should be meaning. If the spacing of objects in frame is left to chance, you've introduced accident into what should be intention.

This is not megalomania—it is the recognition that quality requires integration, and integration requires deliberate choices.

---

## The Audit Framework

### Step 1: Map the Element Categories

Every project has controllable elements. Identify yours:

**For written work:**
- Structure and organization
- Word choice and voice
- Rhythm and pacing
- Opening and closing
- Transitions between sections
- White space and formatting
- Title and headers

**For visual work:**
- Composition and framing
- Color palette
- Typography
- Spacing and alignment
- Image selection
- Visual hierarchy
- Negative space

**For products/services:**
- Core functionality
- User interface/experience
- Onboarding flow
- Error messages and edge cases
- Documentation
- Packaging/presentation
- Support experience

**For events/presentations:**
- Venue and setup
- Timing and pacing
- Visual aids
- Opening and closing
- Transitions
- Audience interaction
- Follow-up

### Step 2: Classify Each Element

For every element, determine:

| Element | Status | Notes |
|---------|--------|-------|
| [Element] | Deliberate / Default / Neglected | [Why this status] |

**Deliberate:** You consciously chose this. You know why it is what it is.
**Default:** This is what the tool/format/convention provided. You accepted it.
**Neglected:** You didn't think about this. It is whatever it happens to be.

### Step 3: Evaluate Default and Neglected Elements

For each non-deliberate element, ask:

**The Kubrick Questions:**
1. Does this element communicate something?
2. If yes, is it communicating what you intend?
3. If no, are you sure? (All elements communicate; the question is whether you're aware of what.)
4. Would a deliberate choice here improve the work?
5. Is the default actually optimal, or merely acceptable?

### Step 4: Identify High-Impact Defaults

Not all defaults matter equally. Prioritize based on:

**Visibility:** How much does this element affect perception?
**Differentiation:** Could a deliberate choice here distinguish your work?
**Integration:** Does this element connect to other elements?
**Stakes:** What is lost if this element undermines the vision?

### Step 5: Decide What to Reclaim

For each high-impact default or neglected element:

| Element | Current State | Deliberate Alternative | Decision |
|---------|--------------|----------------------|----------|
| [Element] | [What it is now] | [What it could be] | [Keep default / Reclaim control] |

**Valid reasons to keep the default:**
- The default is genuinely optimal
- The element is low-impact
- Time/resources don't justify the change

**Invalid reasons to keep the default:**
- "That's how it's usually done"
- "I didn't think about it"
- "It's probably fine"

---

## Workflow

### Step 1: Gather and Review Inputs

Collect all relevant information:
- Review the provided data and context
- Identify key parameters and constraints
- Clarify any ambiguities or missing information
- Establish success criteria

### Step 2: Analyze the Situation

Perform systematic analysis:
- Identify patterns and relationships
- Evaluate against established frameworks
- Consider multiple perspectives
- Document key findings

### Step 3: Generate Recommendations

Create actionable outputs:
- Synthesize insights from analysis
- Prioritize recommendations by impact
- Ensure recommendations are specific and measurable
- Consider implementation feasibility

## Output Format

```markdown
## Total Control Audit

### Project
[Name and brief description]

### Vision Statement
[What this project is meant to accomplish]

### Element Inventory

#### Deliberate Choices
| Element | Choice | Rationale |
|---------|--------|-----------|
| [Element] | [What you chose] | [Why] |

#### Default Elements
| Element | Default | Source of Default | Impact |
|---------|---------|------------------|--------|
| [Element] | [What it is] | [Tool/convention/assumption] | [High/Medium/Low] |

#### Neglected Elements
| Element | Current State | Should Have Considered |
|---------|--------------|----------------------|
| [Element] | [What it is] | [What this affects] |

### High-Impact Defaults Analysis

#### [Element 1]
**Current state:** [What the default provides]
**What it communicates:** [Whether intended or not]
**Deliberate alternative:** [What you could choose instead]
**Recommendation:** [Keep / Reclaim] because [reason]

#### [Element 2]
[Same structure]

### Control Reclamation Plan

| Priority | Element | Action | Rationale |
|----------|---------|--------|-----------|
| 1 | [Element] | [What to change] | [Why this matters most] |
| 2 | [Element] | [What to change] | [Why] |

### The Integration Check
With these changes, do all elements now serve a unified vision?
[Assessment]

### The Kubrickian Verdict
[Summary: Is this project under sufficient deliberate control to achieve excellence, or are accidents undermining intention?]
```

---

## Outputs

**Primary Output:** A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data.

**Format:**
```markdown
## Analysis: [Topic]

### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]

### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]
```

**Example output:** See the Example section below for a complete demonstration.

## Constraints

- Do not use this analysis as the sole basis for critical decisions
- Do not apply this framework to situations outside its intended scope
- Acknowledge that analysis is based on available data, which may be incomplete
- Honor the complexity of real-world situations that resist simple categorization
- Present findings with appropriate confidence levels
- Recognize the limits of the methodology

## Example

**Input:** "I'm creating a slide deck for a startup pitch. I've focused on the content but want to make sure I haven't missed anything important. Audit this."

**Output:**



**Why this works:**

This example demonstrates the key principles of the skill in action. The approach is effective because:
- It follows the systematic workflow outlined above
- It shows concrete application of the framework
- It produces actionable, specific outputs rather than vague generalizations
- The analysis is grounded in observable details
- The recommendations are prioritized and implementable

**Alternative applications:**

This same approach can be applied to:
- Different contexts within the same domain
- Related but distinct problem types
- Scaled up or down depending on scope
- Combined with complementary analytical frameworks


## Total Control Audit

### Project
Startup pitch deck

### Vision Statement
[Assuming:] Convince investors that this opportunity is exceptional and this team is capable of executing it.

### Element Inventory

#### Deliberate Choices (Assumed)
| Element | Choice | Rationale |
|---------|--------|-----------|
| Core narrative | Problem → Solution → Market → Team → Ask | Standard pitch structure |
| Key metrics | [Specific numbers] | Prove traction |
| Ask amount | [Specific amount] | Matches need and valuation |

#### Default Elements
| Element | Default | Source of Default | Impact |
|---------|---------|------------------|--------|
| Slide template | PowerPoint/Keynote default | Tool provided | HIGH |
| Font choice | System default or template font | Tool provided | MEDIUM |
| Color scheme | Template colors | Tool provided | HIGH |
| Transitions | None or default fade | Tool provided | LOW |
| Slide count | However many topics you had | Convention | MEDIUM |
| Aspect ratio | 16:9 or 4:3 | Assumed based on context | LOW |
| Opening slide | Title + company name + logo | Convention | HIGH |
| Closing slide | "Thank you" or "Questions?" | Convention | HIGH |

#### Neglected Elements
| Element | Current State | Should Have Considered |
|---------|--------------|----------------------|
| First 5 seconds | Unknown | This determines whether they pay attention |
| Spacing/margins | Whatever template provides | Affects perceived professionalism |
| Image quality | Varies | Low-res images signal carelessness |
| Consistency | Unknown | Every inconsistency creates distraction |
| Handout version | Probably none | They'll want something to reference |

### High-Impact Defaults Analysis

#### Opening Slide
**Current state:** Likely company name + logo + tagline
**What it communicates:** "This is a pitch deck" (obvious), possibly "we used a template"
**Deliberate alternative:** Open with the problem statement as a question. Or a striking image. Or a customer quote. Anything that creates curiosity rather than announces format.
**Recommendation:** RECLAIM. The opening is the most important slide. A default opening signals "generic pitch."

#### Closing Slide
**Current state:** Likely "Thank you" or "Questions?"
**What it communicates:** "We're done" (obvious), missed opportunity
**Deliberate alternative:** Close with the single most compelling fact. Or a bold vision statement. Or a direct ask. The last thing seen should be memorable.
**Recommendation:** RECLAIM. "Thank you" wastes your final impression.

#### Template/Color Scheme
**Current state:** Whatever came with the tool
**What it communicates:** If recognizable as a template, it signals "we didn't care enough to design this"
**Deliberate alternative:** Simple, distinctive color scheme. Minimal. A few brand colors used consistently.
**Recommendation:** RECLAIM. Visual distinction supports the message that your company is distinctive.

#### Font Choice
**Current state:** System or template default
**What it communicates:** Nothing positive; potentially "unexamined"
**Deliberate alternative:** A modern, readable font that isn't Calibri or Arial. Consistent between headers and body.
**Recommendation:** RECLAIM (LOW effort, medium impact). A deliberate font choice costs nothing and adds polish.

### Control Reclamation Plan

| Priority | Element | Action | Rationale |
|----------|---------|--------|-----------|
| 1 | Opening slide | Replace with curiosity-creating hook | First impression determines attention |
| 2 | Closing slide | Replace with memorable final statement | Last impression determines retention |
| 3 | Color scheme | Develop simple, distinctive palette | Differentiation from other pitches |
| 4 | Consistency check | Audit all slides for visual consistency | Inconsistency signals carelessness |
| 5 | Font | Choose deliberate, modern option | Low effort, professional signal |
| 6 | Handout | Create leave-behind version | Enables continued consideration |

### The Integration Check
With these changes, do all elements now serve a unified vision?

The content may be strong, but the presentation is currently undermined by defaults that communicate "generic pitch deck." Investors see hundreds of these. The defaults make you invisible. Reclaiming control of opening, closing, and visual identity ensures that the quality of your thinking is matched by the quality of its presentation.

### The Kubrickian Verdict
You have controlled the script—the content, the narrative, the metrics. But you have surrendered the cinematography—how it looks, how it opens, how it closes. In Kubrick's world, that surrender is fatal. The story told with default visuals is a story that looks like every other story. Reclaim the elements that distinguish this pitch from the hundred others on their desk.

"If the spacing of objects in frame is left to chance, you've introduced randomness into what should be meaning."

---

## The Kubrick Principle

Every element communicates—whether you control it or not. The question is never "does this matter?" The question is "what is this saying, and is that what I want to say?"

Defaults are not neutral. They are choices made by someone else for general purposes. Your work is not general. Your vision is specific. Every default you accept is a place where your specific vision yields to someone else's general solution.

Not every default needs to be overridden. But every default should be examined. The audit's purpose is not to create work—it is to ensure that what appears as your work actually reflects your intention.

---

## Integration

This skill is part of the **Stanley Kubrick** expert persona. Use it when quality depends on the integration of details, and when you suspect that unexamined defaults may be undermining your vision.