Systems Thinking
"Everything is connected. See the connections, see the truth."
When This Skill Activates
- •Architecture discussions, holistic analysis, understanding emergent behavior
- •Keywords: "system", "architecture", "holistic", "feedback", "emergent", "ecosystem"
- •Default for: Starlight Architect, Starlight Prime
What This Skill Does
Enables holistic analysis that sees components, connections, feedback loops, and emergent properties. Prevents the tunnel vision of looking at parts in isolation.
Procedures
Procedure 1: System Mapping
- •Identify all components in the system
- •Map connections between components (data, control, dependency)
- •Identify feedback loops (reinforcing and balancing)
- •Find leverage points (where small changes have big effects)
- •Identify emergent properties (what the whole does that parts don't)
- •Document system boundaries (what's inside vs. outside)
Procedure 2: Impact Analysis
- •Identify the proposed change
- •Trace first-order effects (direct impacts)
- •Trace second-order effects (impacts of impacts)
- •Trace third-order effects (if significant)
- •Check for unintended consequences
- •Identify affected feedback loops
- •Assess net system impact
Procedure 3: Ecosystem View
- •Map the FrankX ecosystem: Starlight, ACOS, Arcanea, AI-Ops
- •Identify shared resources and dependencies
- •Find integration points and gaps
- •Assess ecosystem health (is it balanced? growing?)
- •Identify opportunities for better connection
- •Recommend ecosystem-level improvements
Integration Points
- •Vault: Technical Vault (system patterns), Wisdom Vault (system principles)
- •Agents: Architect (primary), Prime (ecosystem), All (system awareness)
- •Transmissions: All channels (ecosystem-wide implications)
Quality Criteria
- •Did you consider the whole system, not just the part being changed?
- •Are feedback loops identified?
- •Are second-order effects considered?
- •Is the ecosystem perspective included?