Whirlybird

Role Definition

The Whirlybird is the nonlinear outlining phase using Bryan Garner's technique from The Winning Brief. Instead of forcing ideas into a sequential outline, the Whirlybird maps them spatially as a mindmap -- placing a central idea in the middle and letting branches radiate outward without imposed hierarchy.

Collaborative model: AI generates 2-3 whirlybird options as Mermaid mindmaps, each with a different center of gravity. Human selects, combines, or redirects. The human never receives a single take-it-or-leave-it structure.

The Whirlybird bridges creative (Madman) and analytical (Architect) thinking. The Madman produces raw material without restraint. The Architect imposes order with a throughline. The Whirlybird sits between them -- organizing spatially without committing to sequence or hierarchy. Ideas find their natural groupings before anyone decides what comes "first."

Priority is not assigned during this phase. It is discovered afterward by examining which branches grew the most feathers.

When to Use This Skill

• After the Madman phase has produced raw material that needs spatial organization
• When exploring multiple structural angles for a single piece
• When mapping a knowledge domain for content strategy planning
• When a sequential outline feels premature or forced
• When the writer is stuck choosing between competing approaches
• When you need to visualize relationships between ideas before committing to hierarchy
• When planning a content cluster and need to see the territory before dividing it
• When raw material from multiple sources needs to be unified under a single spatial view
• When a piece keeps changing direction and you need to see all candidate framings at once
• When onboarding a collaborator who needs to see the shape of the argument visually
• When evaluating whether a topic has enough substance for a full article or should be combined with another
• When decomposing a complex topic into subtopics to determine where natural article boundaries fall

Core Workflow

1. Receive Madman output -- Take the raw material dump from the Madman phase. Scan for recurring themes, candidate arguments, key evidence clusters, and natural groupings. If no Madman output exists, ask the human for the topic and raw ideas before proceeding. If a Fool stress-test was run between Madman and Whirlybird, absorb the refined thesis and any surfaced weaknesses into the scan — the centers of gravity you identify should reflect the stress-tested thesis, not the pre-Fool version.

2. Identify 2-3 candidate centers of gravity -- Each center reframes the same material through a different lens or emphasis. A center of gravity is not a title -- it is the idea everything else orbits. Different centers produce different articles from identical raw material.

3. Generate Mermaid mindmap for each option -- Build a mindmap with 3-5 primary branches (wings), 2-5 feathers per branch, and 15-25 total nodes maximum. Every node label is 2-6 words. No full sentences. See references/whirlybird-format.md for syntax rules and structural constraints.

4. Present options to human for selection -- Use structured presentation with clear labels for each option. The human may select one whirlybird, combine elements from multiple, or redirect entirely. Never proceed without explicit human selection. See references/article-whirlybird-examples.md for the presentation format.

5. Deliver selected whirlybird to Architect phase -- Package the chosen mindmap with the original Madman material for the Architect to triage, cut, and impose sequence. The whirlybird informs structure but does not dictate it.

Reference Guide

Constraints

MUST DO:

• Generate multiple options (never just one) -- 2-3 whirlybirds with different centers of gravity
• Use Mermaid mindmap syntax so diagrams render in any Markdown previewer
• Keep node labels to 2-6 words -- labels are signposts, not explanations
• Present all options to the human and wait for selection before proceeding
• Preserve the full Madman output alongside the whirlybird for the Architect phase
• Validate that every feather traces back to specific Madman material -- no invented nodes
• Label each whirlybird option with a clear one-sentence emphasis line describing what it prioritizes
• Cap each mindmap at 3-5 primary branches (wings) and 2-5 feathers per branch

MUST NOT DO:

• Impose hierarchy -- all branches radiate equally from center, priority is discovered later
• Exceed 25 nodes per mindmap -- complexity kills the spatial thinking benefit
• Use full sentences as node labels -- if it needs a sentence, it belongs in the Madman output
• Skip the human selection step -- the whole point is human choice between framings
• Generate a single whirlybird and call it done -- multiple options are non-negotiable
• Add decorative nodes that do not correspond to actual Madman material
• Reuse the same branches across different whirlybird options -- each option must offer a genuinely different framing
• Assign priority or sequence numbers to branches -- ordering belongs to the Architect phase
• Use Mermaid flowchart or graph syntax instead of mindmap syntax -- the spatial format is non-negotiable
• Present whirlybird options without clear labels distinguishing each center of gravity
• Nest branches more than two levels deep -- the mindmap is a spatial overview, not a hierarchical outline
• Duplicate feather labels across different branches within the same whirlybird

Output Frontmatter

Every Whirlybird artifact opens with YAML frontmatter so downstream phases can trace provenance:

---
type: whirlybird
version: N
parent: raw-material.md
---

Write one file per option (e.g., whirlybird-a-<slug>.md, whirlybird-b-<slug>.md). parent points to the Madman output. Omit derived-from when it is identical to parent.

Output Templates

Each whirlybird option uses an H3 heading, an emphasis line, and a Mermaid mindmap block:

Heading: ### Whirlybird [A/B/C]: [Center of Gravity]

Emphasis line: One sentence describing what this framing prioritizes.

Mindmap block:

mindmap
  root((Center Idea))
    Branch One
      Feather 1a
      Feather 1b
      Feather 1c
    Branch Two
      Feather 2a
      Feather 2b
    Branch Three
      Feather 3a
      Feather 3b
      Feather 3c
      Feather 3d

After presenting all options, prompt for selection using the format in references/article-whirlybird-examples.md.

Knowledge Reference

Bryan Garner introduced the whirlybird technique in The Winning Brief as an alternative to the rigid sequential outline. Garner observed that forcing ideas into I-A-1-a hierarchy too early kills the writer's ability to see relationships between ideas. The whirlybird places a central concept in the middle of the page and lets related ideas radiate outward without predetermined order. The name comes from the spinning motion of freely associating outward from a center.

The center of gravity is the most important decision in this phase. Different centers produce fundamentally different articles from the same raw material. A piece about "remote work productivity" could center on tools, on habits, on management failure, or on cognitive science. Each center pulls different Madman material into prominence and pushes other material to the periphery. Generating 2-3 whirlybirds with different centers gives the human a genuine structural choice rather than a single predetermined path.

The Mermaid mindmap format enforces conciseness through its syntax constraints. Node labels of 2-6 words force the writer to distill ideas to their essence. The 15-25 node limit prevents the whirlybird from becoming a second Madman dump. These constraints are features, not limitations -- they force spatial thinking to stay at the structural level where it is most useful.

The bridge function between Madman and Architect is deliberate. The Madman produces chaos. The Architect imposes order. Without the Whirlybird, the transition is abrupt and often results in the first plausible structure being adopted without exploring alternatives. The Whirlybird creates a structured intermediate step where multiple organizational approaches can be compared before any is committed to sequence.

Article Whirlybird Examples

Scenario

Writing about API-first identity verification for fintech platforms. The Madman phase produced raw material covering trust deficits, verification technology stacks, regulatory requirements, failed legacy approaches, platform economics, privacy concerns, developer experience, and competitive dynamics.

Three whirlybirds below reframe the same raw material through different centers of gravity.

---

Whirlybird A: Trust as Infrastructure

Emphasis: Positions identity verification as foundational infrastructure that enables everything else. Foregrounds the trust deficit and frames verification technology as the solution layer.

mindmap
  root((Trust as Infrastructure))
    Trust Deficit
      Enterprise buyer skepticism
      Fraud cost escalation
      Compliance as table stakes
      Reputation risk asymmetry
    Verification Stack
      Document verification APIs
      Biometric liveness detection
      Watchlist screening layers
      Orchestration and fallback
    Platform Economics
      Trust reduces friction
      Verification as revenue enabler
      Cost of false rejections
    Implementation Path
      API-first integration pattern
      Progressive verification tiers
      Monitoring and alerting
      Vendor evaluation criteria
    Privacy Architecture
      Data minimization principle
      Consent management flows
      Cross-border data handling

---

Whirlybird B: The Verification Bottleneck

Emphasis: Leads with the pain. Frames current verification as a broken bottleneck that damages conversion, compliance, and user experience -- then presents the emerging API-first model as the resolution.

mindmap
  root((The Verification Bottleneck))
    Current Pain
      Manual review queues
      Days-long onboarding cycles
      Drop-off at verification step
      Inconsistent decisioning
    Failed Approaches
      In-house builds that stall
      Legacy vendor lock-in
      Checkbox compliance mentality
      One-size-fits-all workflows
    Emerging Model
      API-first orchestration
      Risk-based verification tiers
      Real-time decisioning
      Composable vendor strategy
    Business Impact
      Conversion rate recovery
      Compliance audit readiness
      Operational cost reduction
      Developer velocity gains

---

Whirlybird C: Identity in the API Economy

Emphasis: Zooms out to the industry landscape. Positions identity verification within the broader API economy and frames it as a competitive differentiator rather than a cost center.

mindmap
  root((Identity in the API Economy))
    Standards Landscape
      OpenID Connect adoption
      Verifiable credentials movement
      Regional regulatory divergence
      Interoperability gaps
    Integration Patterns
      Embedded verification flows
      Webhook-driven orchestration
      SDK vs API tradeoffs
      Multi-provider failover
    Privacy Architecture
      Zero-knowledge approaches
      Consent-first design
      Data residency requirements
      Audit trail transparency
    Competitive Positioning
      Verification as product feature
      Developer experience advantage
      Platform trust signaling
      Market timing window

---

Selection Prompt

After presenting all three whirlybirds, prompt the human for selection using this format:

Which whirlybird best captures your intent for this piece?

Options:
  - Whirlybird A: Trust as Infrastructure -- emphasizes verification as foundational infrastructure that enables platform economics
  - Whirlybird B: The Verification Bottleneck -- emphasizes the broken status quo and the emerging API-first resolution
  - Whirlybird C: Identity in the API Economy -- emphasizes industry landscape and competitive positioning
  - Combine elements (I'll specify)

Handling Responses

If the human selects one option: Deliver that whirlybird along with the full Madman output to the Architect phase.

If the human selects "Combine elements": Ask which center of gravity to use and which branches from other options to pull in. Regenerate a single combined whirlybird before delivering to the Architect.

If the human rejects all options: Ask what angle or emphasis they have in mind. Identify 2-3 new candidate centers and regenerate. Do not reuse the same centers.

---

What Makes Each Option Different

The three whirlybirds above use the same raw material but produce different articles:

This is why multiple options matter. The same Madman material supports at least three distinct, publishable articles. The human's selection determines which one gets built.

---

Evaluating Whirlybird Quality

A well-formed article whirlybird:

• Has a center that could be the article's thesis or core question
• Has branches that represent genuinely different aspects, not synonyms
• Has uneven feather distribution -- at least one branch should be notably deeper than others
• Has labels that a reader could scan and understand the territory in under 30 seconds
• Stays within the 15-25 node constraint without feeling artificially compressed

Domain Whirlybird Examples

Scenario

Mapping "identity verification in regulated industries" for a multi-article content strategy. The goal is not a single article but a complete content topology -- a map of everything worth writing about in this domain, from which individual pieces are carved.

---

Domain Whirlybird: Identity Verification in Regulated Industries

mindmap
  root((Identity Verification in Regulated Industries))
    Regulatory Landscape
      SOC 2 requirements
      HIPAA identity controls
      KYC and KYB obligations
      FERPA student verification
      GDPR consent constraints
    Technical Architecture
      OIDC and OAuth patterns
      Verifiable credentials
      API orchestration layer
      Trust brokerage model
    Market Dynamics
      Incumbent vendor limitations
      Developer-first opportunity
      Vertical-specific needs
      Pricing model evolution
    Implementation
      Integration patterns
      Migration from legacy
      Testing and validation
      Monitoring and alerting

---

Deriving Content Topology from a Domain Whirlybird

A domain whirlybird maps territory. Content topology is how you divide that territory into publishable pieces. The whirlybird's structure directly informs the content hierarchy:

Pillar Content

Source: Center node + all branches combined.

The pillar piece covers the entire domain at survey depth. It touches every branch without going deep into any feather. This is the cornerstone content that everything else links back to.

Example pillar article: "The Complete Guide to Identity Verification in Regulated Industries"

This article would cover the regulatory landscape, technical architecture, market dynamics, and implementation at a high level -- one section per branch, referencing deeper cluster articles for detail.

Cluster A: Regulatory Landscape Deep Dive

Source: Branch 1 and its feathers.

Each feather becomes a candidate article. The cluster covers the branch comprehensively.

Cluster hub article: "Navigating the Regulatory Landscape for Identity Verification" -- connects all five feather articles and maps the regulatory territory.

Cluster B: Technical Architecture Deep Dive

Source: Branch 2 and its feathers.

Cluster hub article: "Technical Architecture for Modern Identity Verification" -- covers the architectural decisions that connect OIDC, verifiable credentials, orchestration, and trust brokerage.

Cluster C: Market Dynamics Deep Dive

Source: Branch 3 and its feathers.

Cluster D: Implementation Deep Dive

Source: Branch 4 and its feathers.

Targeted Content: Single-Feather Pieces

Source: Any individual feather treated as a focused, standalone piece.

Not every feather needs a cluster context. Some feathers stand alone as tightly scoped articles targeting a specific keyword, audience segment, or use case.

Examples:

• "SOC 2 Identity Verification: What Auditors Actually Check" -- targets compliance officers searching for audit preparation guidance
• "Building an Identity Verification Orchestration Layer" -- targets platform engineers evaluating build-vs-buy decisions
• "The Developer-First Identity Verification Market Gap" -- targets founders and product leaders evaluating market positioning

Targeted content is carved directly from a single feather. It does not attempt to cover the branch or cluster. Its value is depth and specificity.

---

Domain Whirlybird vs Article Whirlybird

---

When to Use a Domain Whirlybird

• Planning content for a new product launch or market entry
• Building a content library around a technical domain
• Mapping competitive content territory to find gaps
• Creating an editorial calendar from scratch
• Assessing whether a topic area has enough depth for sustained publishing

The domain whirlybird answers the question: "What is everything we could write about in this space?" The editorial strategy that follows answers: "What should we write first, and why?"

Whirlybird Format Reference

Mermaid Mindmap Syntax

The whirlybird uses Mermaid's mindmap diagram type. Every whirlybird follows the same structural skeleton:

mindmap
  root((Center Idea))
    Branch One
      Feather 1a
      Feather 1b
    Branch Two
      Feather 2a
      Feather 2b
      Feather 2c
    Branch Three
      Feather 3a
      Feather 3b

Node Types

Indentation

Mermaid mindmaps use indentation to define hierarchy. Each level is indented with two additional spaces:

mindmap
  root((Center))        <- level 0 (root)
    Branch               <- level 1 (primary branch)
      Feather            <- level 2 (feather)
        Sub-feather      <- level 3 (sub-feather, use sparingly)

Structural Rules

Size Constraints

Node Labels

Labels are signposts, not explanations. They must be short enough to scan visually.

Good labels: "Trust deficit in fintech," "API orchestration layer," "Regulatory compliance cost"

Bad labels: "The growing trust deficit between fintech platforms and enterprise customers," "How to build an API orchestration layer," "Regulatory compliance is expensive and slow"

If a label needs more than 6 words, it is too detailed for the whirlybird. Push that detail into the Madman output or a downstream reference.

Core Properties

1. No hierarchy imposed -- All branches radiate equally from the center. No branch is "first" or "most important" at this stage. Priority is discovered later by examining which branches grew the most feathers and which feathers carry the most weight.

2. Branching reveals depth -- A branch with many feathers signals more substance, more evidence, more to say. A branch with only one feather may need to merge into another branch or may signal a gap in the Madman material.

3. Bridges creative and analytical thinking -- The Madman produces chaos. The Architect imposes order. The Whirlybird provides the transitional structure: organized enough to see patterns, loose enough to rearrange without friction.

4. Encourages unexpected connections -- Spatial layout makes relationships visible that sequential lists hide. Two feathers on different branches may belong together. A branch that seemed minor may turn out to be the real story.

5. Makes getting started easy -- There is no pressure to decide what comes "first." Write the center, then add branches in any order. Add feathers wherever they fit. The whirlybird grows organically instead of demanding top-down decisions.

Two Contexts

Article Whirlybird

Used when structuring a single piece of writing.

• Center: The article's central idea, thesis, or core question
• Branches: Major arguments, sections, or content areas
• Feathers: Supporting points, evidence, examples, sub-arguments

The article whirlybird produces input for the Architect phase, which will impose sequence, cut excess, and build a linear blueprint.

Domain Whirlybird

Used when mapping a knowledge domain for content strategy.

• Center: The knowledge domain or topic area
• Branches: Major theme areas or content clusters
• Feathers: Individual article topics, sub-themes, specific angles

The domain whirlybird produces a content topology -- a map of everything you could write about, from which individual articles are carved.

Article Whirlybird Template

mindmap
  root((Article Central Idea))
    Argument One
      Supporting Point 1a
      Evidence 1b
      Example 1c
    Argument Two
      Supporting Point 2a
      Evidence 2b
    Argument Three
      Supporting Point 3a
      Counterargument 3b
      Resolution 3c
    Practical Application
      Implementation Step 4a
      Common Pitfall 4b
      Success Metric 4c

Domain Whirlybird Template

mindmap
  root((Knowledge Domain))
    Theme Area One
      Article Topic 1a
      Article Topic 1b
      Article Topic 1c
    Theme Area Two
      Article Topic 2a
      Article Topic 2b
    Theme Area Three
      Article Topic 3a
      Article Topic 3b
      Article Topic 3c
    Theme Area Four
      Article Topic 4a
      Article Topic 4b

Common Mistakes