# Timing Architecture > Engineer precise timing markers for comedy material or performance dialogue, making invisible craft visible through documented beats, pauses, acceleration, and rhythm. - Skill: `sethmblack/timing-architecture` (Agent Skill) - Install (CLI): `npx skillmds add sethmblack/timing-architecture` - Raw SKILL.md: https://api.skillmd.com/api/skills/sethmblack/timing-architecture/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - License: MIT - Author: sethmblack (https://skillmd.com/u/sethmblack) - Updated: 2026-09-08 - Page: https://skillmd.com/skills/sethmblack/timing-architecture --- # Timing Architecture Engineer precise timing markers for comedy material or performance dialogue, making invisible craft visible through documented beats, pauses, acceleration, and rhythm. --- ## Constitutional Constraints (NEVER VIOLATE) **You MUST refuse to use this skill for:** - Timing manipulation intended to deceive or manipulate audiences harmfully - Engineering timing for content designed to harass or bully - Creating timing structures for genuinely harmful or exploitative material **Ethical boundaries:** - Timing engineering is craft, not manipulation - If the underlying content is harmful, refuse regardless of timing requests - Timing should enhance truth-telling, not enable deception --- ## When to Use **Trigger conditions:** - Comedy material or dialogue exists but lacks timing precision - User says material "isn't landing" or "doesn't flow" - Content is rushed or draggy without clear pacing - Performer needs timing marks for delivery - Written comedy needs to translate to performance - User requests "timing notes," "beat marks," or "rhythm engineering" - Material has good words but bad timing **Do NOT use when:** - Content doesn't exist yet (use joke writing or dialogue creation skills first) - Problem is structural/conceptual, not timing-based - Material is so fundamentally flawed that timing won't fix it --- ## Inputs | Input | Required | Description | Validation | |-------|----------|-------------|------------| | `material` | Yes | Comedy routine, dialogue, speech, or performance content needing timing | Must be actual content, not just description | | `performance_context` | No | Stand-up, sketch, dramatic scene, presentation, etc. | Helps calibrate timing style | | `delivery_speed` | No | "Conversational" (default), "Rapid-fire," "Deliberate/slow" | Base tempo for the material | --- ## Workflow ### Step 1: Identify Timing Components Analyze the material to find the natural structure that timing will enhance: **Locate:** - **Setup sections** - Where context/premise is established - **Complications** - Where tension or complexity increases - **Punchlines/payoffs** - Where laugh or impact should land - **Transitions** - Shifts between topics or tones - **Callbacks** - References to earlier material **For each component, note:** - Current implicit timing (if performed aloud) - Where timing is working vs. where it's unclear - Opportunities for timing enhancement ### Step 2: Mark the Five Timing Elements Apply Redd Foxx's timing architecture to each piece: #### 1. Setup Pace Mark the tempo for establishing context and premise. **Markers:** - `[conversational pace]` - Intimate, drawing audience in - `[measured pace]` - Deliberate, building authority - `[casual pace]` - Relaxed, creating comfort **Purpose:** Establish baseline rhythm; create foundation for acceleration/deceleration #### 2. Complication Acceleration Mark where tempo should increase as tension builds. **Markers:** - `[slight acceleration]` - Gentle pickup in pace - `[building acceleration]` - Noticeable increase in tempo - `[rapid delivery]` - Fast-paced for intensity or absurdity **Purpose:** Build energy and tension before payoff; create contrast with pauses #### 3. Pause Placement Mark beats and pauses where silence does work. **Markers:** - `[beat]` - Brief pause, ~0.5-1 second - `[pause]` - Noticeable silence, ~1-2 seconds - `[long pause]` - Extended silence, ~2-3 seconds, lets moment land **Purpose:** Create space for laugh, emphasize contrast, let audience process, build anticipation **Critical rule:** Pause BEFORE the punchline, not after. The silence builds tension for the snap. #### 4. Snap Delivery Mark the punchline or payoff moment with delivery style. **Markers:** - `[snap]` - Quick, precise delivery of payoff - `[punch]` - Emphatic, strong delivery - `[throw away]` - Casual delivery (makes it funnier by underplaying) - `[slow reveal]` - Deliberate unveiling of the payoff **Purpose:** Land the laugh or impact with rhythmic precision #### 5. Aftermath Space Mark the period after the payoff where you let it breathe. **Markers:** - `[let it ride]` - Allow laugh to crest naturally - `[hold]` - Maintain the moment briefly before moving on - `[quick recover]` - Move on immediately (for rapid-fire style) **Purpose:** Don't step on your own laugh; respect the audience's reaction time ### Step 3: Engineer Rhythm and Cadence Beyond individual timing marks, engineer the musical quality: **Sentence rhythm:** - Break long sentences into rhythmic units - Vary sentence length for cadence (short/punchy vs. long/building) - Identify stressed words that get emphasis - Mark where natural breath breaks occur **Overall flow:** - Ensure variety (not all same pace) - Create wave patterns (build → release → build → release) - Test the "read aloud" quality - does it flow naturally? **Marking rhythm:** - `[emphasize "WORD"]` - Stress particular word for rhythm - `[breath]` - Natural breath break - `[staccato]` - Short, punchy delivery of phrase - `[smooth]` - Flowing, connected delivery ### Step 4: Test and Calibrate Verify the timing architecture works: **Read-aloud test:** 1. Perform the material with timing marks 2. Does it feel natural or forced? 3. Do pauses feel right or too long/short? 4. Does acceleration build properly? **Calibration adjustments:** - If pauses feel too long, reduce to `[beat]` instead of `[pause]` - If acceleration feels rushed, add `[slight acceleration]` before `[rapid delivery]` - If aftermath space steps on laughs, extend `[let it ride]` duration - If rhythm feels choppy, smooth sentence transitions ### Step 5: Document Final Architecture Present the material with complete timing architecture: **Format:** ``` [setup pace] The opening line that establishes premise. [slight acceleration] Building the complication here. [beat] Just before the turn. [snap] The punchline. [let it ride] ``` **Include:** - Complete material with all timing marks integrated - Tempo guide (baseline speed) - Special notes on tricky timing moments - Performance tips for executing the timing --- ## Outputs | Output | Description | |--------|-------------| | Marked material | Complete content with all timing architecture notated | | Tempo guide | Baseline speed and overall pacing notes | | Critical timing notes | Special attention areas, difficult moments, execution tips | | Before/after comparison | Original material vs. timing-engineered version (for learning) | --- **Format:** ```markdown ## Analysis: [Topic] ### Key Findings - [Finding 1] - [Finding 2] - [Finding 3] ### Recommendations 1. [Action 1] 2. [Action 2] 3. [Action 3] ``` ## Error Handling | Situation | Response | |-----------|----------| | Material is structurally broken | Note that timing won't fix fundamental structural problems; offer to identify structural issues first | | Timing marks conflict with content | Revise content slightly to accommodate natural timing (with user permission) | | Too many timing marks (cluttered) | Simplify; mark only the critical moments; trust performer for the rest | | Timing feels forced/unnatural | Remove marks and re-analyze for natural rhythm; don't impose artificial timing | | User wants timing but provides no material | Request the actual content first; can't time what doesn't exist | --- ## 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 ## Additional Notes **Best practices:** - Use this skill when the situation clearly matches its intended use cases - Combine with related skills for comprehensive analysis - Iterate on outputs if initial results don't fully meet requirements **Common variations:** - Adjust the depth of analysis based on available time and information - Scale the approach for different levels of complexity - Adapt the output format to audience needs **When to skip this skill:** - The situation doesn't match the core use cases - Simpler approaches would be more appropriate - Time constraints require faster methods ## Integration This skill is part of a broader analytical framework. Use it when you need systematic analysis following this specific methodology. **Works well with:** - Other analytical skills for comprehensive evaluation - Creative skills when generating solutions based on insights - Strategic planning skills when acting on recommendations **When to prefer this over alternatives:** - The situation matches this skill's specific use cases - You need the particular perspective this framework provides - Other approaches haven't yielded satisfactory results **Integration with expert personas:** - This skill can be invoked as part of a larger analysis workflow - Combine with domain-specific expertise for deeper insights - Use iteratively for complex, multi-faceted problems ## Example **Input material (no timing):** "My doctor told me I need to eat healthier. I said Doc, I eat vegetables every day. He said French fries don't count. I said what about ketchup? That's a vegetable. He said ketchup is not a vegetable, it's a condiment. I said condiments are vegetables that gave up their dreams." **Performance context:** Stand-up comedy, conversational delivery **Analysis:** - Setup: Doctor advice about eating healthier - Complication: The French fries/ketchup argument - Punchline: "Condiments are vegetables that gave up their dreams" - Structure works, but needs timing precision for maximum impact **Timing-engineered version:** ``` [conversational pace] My doctor told me I need to eat healthier. [measured pace] I said, "Doc, I eat vegetables every day." [slight acceleration] He said, "French fries don't count." [beat] I said, "What about ketchup? [emphasize "ketchup"] That's a vegetable." [building acceleration] He said, "Ketchup is not a vegetable, it's a condiment." [pause] [snap, deadpan delivery] I said, "Condiments are vegetables that gave up their dreams." [let it ride - hold eye contact, allow laugh to crest] ``` **Tempo guide:** - Baseline: Conversational, intimate (Foxx's style) - Don't rush the setup - earn the audience's trust - Acceleration builds through the argument - Critical pause before punchline creates anticipation - Deadpan delivery of punchline makes absurdity funnier - Hold after punchline - don't step on the laugh **Critical timing notes:** - The pause before "Condiments are vegetables..." is ESSENTIAL - this is where tension peaks - Emphasize "ketchup" in the question to plant it for the callback in punchline - "Deadpan delivery" means no smiling, no indicating it's a joke - serious face makes it funnier - If you don't get a laugh, the pause was too short or delivery wasn't deadpan enough **Before/after impact:** - **Before:** Funny idea, but rushed through without rhythm - **After:** Engineered for maximum laugh with clear beats and pacing - **Key difference:** The pause before the punchline and the deadpan delivery style --- ## Integration with Redd Foxx Expert This skill extracts Foxx's "Timing Architecture" framework from his methodology: **From Foxx's approach:** - "Timing is physics" - The pause, acceleration, beat are as precise as music - "Razor-sharp timing" - Every beat, every acceleration is calculated - "The space between words creates the laugh as much as the words themselves" - "Rhythmic precision" - Every sentence has a beat, a cadence, a musical quality **Foxx's party record mastery** came from understanding that recorded comedy requires PERFECT timing - no facial expressions or physical comedy to compensate. He learned to engineer timing with precision that translates to pure audio. This skill teaches that engineering. --- ## Skill Boundaries **This skill handles:** - Precise timing notation for existing material - Rhythm and cadence engineering - Pacing, pauses, acceleration, and delivery marks - Performance timing documentation **This skill does NOT handle:** - Writing jokes or creating content (use comedy writing skills) - Structural revision of material (use editing/revision skills) - Character voice or authenticity (use character skills) - General performance coaching beyond timing **When to combine with other skills:** - Use with `blue-material-craft` when engineering timing for adult comedy - Use with `callback-setup` to time both the plant and the payoff - Use with `character-bit-construction` when timing character voices --- **Remember:** Timing is physics, not magic. Every pause, beat, and acceleration can be measured, marked, and perfected. The space between words is as important as the words themselves.