ApertureOscillation

Identify design tensions and coherence issues by oscillating analysis across narrow, wide, and synthesis scopes.

17.4k|2.3k|Updated Sep 8, 2025
One-click install
npx skills add https://github.com/danielmiessler/LifeOS --skill apertureoscillation-danielmiessler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ApertureOscillation
Source: https://github.com/danielmiessler/LifeOS/tree/main/LifeOS/install/skills/ApertureOscillation
Command: npx skills add https://github.com/danielmiessler/LifeOS --skill apertureoscillation-danielmiessler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies design tensions and coherence issues in a system by oscillating the scope of analysis, revealing insights that are invisible at any single zoom level.

Core Features & Use Cases

  • Scope Oscillation: Analyzes the same question at different zoom levels (narrow, wide, synthesis) to reveal hidden issues.
  • Design Tensions: Identifies discrepancies between local and system-level views.
  • Coherence Assessments: Validates that the component aligns with the system's vision.
  • Use Case: When designing a feature within a larger system, use this Skill to ensure the feature serves both its own purpose and the system's.

Quick Start

Run the ApertureOscillation skill with the input 'Analyze the feature "Session Data Caching" across tactical and strategic scopes.'

Frequently Asked Questions about ApertureOscillation

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

FAQPage Schema
How do I identify design tensions between a local feature and overall system architecture?

Identify design tensions by oscillating analysis scope across narrow tactical, wide strategic, and synthesis passes. This reveals hidden discrepancies between local feature design and overall system architecture, validating component alignment with the system vision.

What is scope oscillation in system coherence analysis?

Scope oscillation is an analysis technique that examines the same architectural question at different zoom levels to reveal hidden coherence issues. By applying narrow, wide, and synthesis passes, it exposes design tensions invisible at any single scope.

How do I perform a design analysis for a feature within a larger system?

Perform a design analysis by running the skill with a tactical target and strategic context. It executes three structured passes to assess feature design, identify local versus system-level discrepancies, and validate overall system coherence.

Does architecture coherence checking require specific dependencies or environments?

Architecture coherence checking requires no external dependencies, relying solely on internal scripts. Users must provide input formatted as a tactical target and strategic context to properly execute the scope oscillation analysis.

When should I use scope oscillation instead of standard architecture reviews?

Use scope oscillation instead of standard architecture reviews when you need to validate that a specific feature serves both its own tactical purpose and the broader strategic system vision. It specifically surfaces design tensions invisible at a single zoom level.

What limitations exist when checking system coherence through scope oscillation?

A key limitation is that scope oscillation requires both a tactical target and strategic context as input. Without properly defined architectural parameters for both levels, the analysis cannot accurately synthesize design tensions or assess system coherence.