Flywheel Sync (ORBIT System)

A meta-skill that operates above all other skills in the launch engine, auditing the health of skill-to-skill connections, identifying broken handoffs, redundant outputs, and bottlenecks, then generating a continuous improvement roadmap. ORBIT ensures the entire product launch system functions as an integrated flywheel rather than a collection of disconnected processes.

When to Use

• Auditing whether the launch engine skills are working together effectively
• Diagnosing why a launch process feels slow, disconnected, or redundant
• Identifying gaps where important outputs are missing or not being consumed
• Checking if skill cadences are aligned with business rhythms
• Building a continuous improvement roadmap for the overall launch system
• Onboarding new team members to understand how skills interconnect
• Preparing for a major launch by verifying all system connections are healthy

What You'll Need

Critical inputs (ask if not provided):

• List of active skills and their current usage status
• Recent outputs from each skill (or confirmation that skills have been run)
• Known pain points or friction in the current launch process
• Team structure and ownership map across skills
• Launch cadence (how often launches occur, what types)

Nice-to-have:

• Outputs from the most recent run of each skill
• Timestamps of last skill execution
• Team feedback on handoff quality and timing
• Historical launch debriefs (from launch-debrief)
• Current launch calendar and upcoming milestones

Process

Step 1: Map the Full Skill Connection Graph

Document every skill-to-skill connection in the launch engine with its expected data flow.

Skill Connection Matrix:

Step 2: Score Each Connection (Orchestration Audit)

For every connection in the matrix, score its health on a 0-3 scale.

Connection Health Scale:

Connection Audit Table:

Overall Orchestration Health = (Sum of connection scores) / (Number of connections x 3) x 100%

Step 3: Redundancy and Gap Analysis

Identify outputs that overlap, outputs that are missing, and outputs that are produced but never consumed.

Output Inventory:

Classification Key:

Redundancy and Gap Findings:

Step 4: Bottleneck Identification

Score each skill as a potential bottleneck based on three factors.

Bottleneck Scoring Model:

Bottleneck Score Formula:

Bottleneck_Score = (Delay_Impact x 0.40) + (Quality_Impact x 0.35) + (Confusion x 0.25)

Factor Definitions:

Bottleneck Classification:

Step 5: Tempo Alignment Check

Verify that each skill runs at the appropriate cadence relative to the business rhythm.

Skill Tempo Map:

Tempo Misalignment Patterns:

Step 6: Generate the Integration Health Dashboard

Compile all analyses into a single health view.

System Health Summary:

Overall System Health Calculation:

System_Health = (Orchestration_Health x 0.35) + (Gap_Score_Inverse x 0.25)
             + (Bottleneck_Score_Inverse x 0.25) + (Tempo_Alignment x 0.15)

Critical Path Identification: Map the longest dependency chain through the skill graph and identify which skills are on the critical path for each launch.

Step 7: Build the Continuous Improvement Roadmap

Prioritize all identified issues into a phased improvement plan.

Improvement Roadmap:

Output

Save to outputs/flywheel-sync/

Deliverables:

1. System Health Dashboard -- Overall system health percentage, orchestration health, gap/redundancy count, average bottleneck score, tempo alignment, and critical path identification with visual dependency map
2. Gap and Redundancy Report -- Every output classified as active, redundant, gap, waste, or orphan with recommended consolidation, creation, or deprecation actions
3. Bottleneck Analysis -- Every skill scored on delay impact, quality impact, and confusion with bottleneck classification (Critical/Moderate/Minor/Healthy) and specific remediation plans
4. Continuous Improvement Roadmap -- Phased plan (Quick Wins through Scale) with timeline, key actions, success metrics, and owners for each improvement initiative

Chain Connections

• Receives from: All skills (outputs, timing data, quality feedback, connection health signals)
• Feeds back into: All skills (health assessments, improvement priorities, tempo recommendations, integration fixes)
• Enhanced by: launch-debrief (systemic patterns across launches), launch-command (critical path data), signal-radar (external timing pressures)