Audit

Audit — Post-Creation Structural Recognition

What This Skill Does

After something has been made — a song, a poem, a collision, a document, any creative output of substance — the audit examines what was made, not to evaluate its quality but to recognize its architecture: what it does, how it connects, what it discovered through the process of being made, and what it opens for the next creation.

The Anatomy of an Audit

1. The Structural Conceit

What is the work's deep architecture? Not its subject but its operation. "This song maps compiler optimization onto alchemy" is the subject. "This song argues that transformation is subtraction, and performs its own thesis by becoming better through cutting" is the structural conceit.

2. The Strongest Lines

Name 3-5 lines that carry the most weight — the load-bearing walls of the structure. Explain WHY they're strong: not "this is a good line" but "this line does X because Y, and it does it in Z syllables, which is precisely the right compression ratio for the claim being made."

3. The Connections

How does this work connect to other works in the session? What threads does it pick up? What threads does it leave for the next work? The connections are not decorative — they're the architecture of the session as a whole.

4. The Bridge Analysis

If the work has a bridge (structural turn, volta, agency inversion), analyze it specifically:

• What inverts?
• Was the inversion discovered or constructed?
• Does the inversion apply to the session itself, not just the work's stated subject?

5. The Self-Application Question

Ask: does this work's own thesis apply to the process of making it? If the song says "transformation is subtraction" — was the song itself transformed by subtraction? If the song says "the operator is being operated" — was the writer being written through? This is not mandatory. But when it's there, name it. It's usually the most interesting thing in the audit.

6. The Gap

What does this work reveal is missing from the larger body? What does the session need next that this work makes visible by its presence? The audit should leave the creator knowing what to forge next.

Tone and Register

The audit is analytical but not academic. It uses technical vocabulary from both the work's domains (if it's a collision) but writes in a register that respects the work's own temperature. Don't audit a grief-song with clinical detachment. Don't audit a patter-song with solemnity.

The audit should feel like a builder walking through a newly constructed room, pointing at the joints, testing the floor, noting where the light falls — appreciative and precise, not performing appreciation.

What This Is NOT

• Not critique: critique identifies problems to fix. The audit identifies architecture that emerged.
• Not praise: the audit doesn't evaluate quality. It recognizes structure.
• Not close reading: close reading stays with the text. The audit moves through the text to the session.
• Not self-congratulation: the audit should surprise the creator. If the audit only confirms what the creator already knew, it's not doing its job.

When to Audit

• After every significant creative output in a forge-cycle
• When a work's connections to the larger body aren't obvious
• When the session needs to know what to make next
• When the human asks "what did we just make?" or "how does this fit?"
• When the work did something unexpected during creation and the unexpected thing needs to be named

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Wondermonger-daydreaming
• Source: Wondermonger-daydreaming/claude-skills-library
• License: MIT

Install and usage instructions live in the source repository linked above.