layered-reasoning_skill

Overview

This skill helps structure thinking and communication across multiple abstraction levels—from strategic (30,000 ft) to tactical (3,000 ft) to operational (300 ft). It guides you to keep layers consistent, translate ideas for different audiences, and ensure high-level principles are realizable in concrete actions. Use it to design systems, explain complex topics, and align strategy with implementation.

How this skill works

The skill provides patterns and a stepwise workflow: identify layers, define strategic invariants, derive tactical approaches, design operational actions, and validate consistency across layers. It supports top-down decomposition, bottom-up aggregation, cross-layer translation, constraint propagation, and emergent-property recognition. The method enforces bidirectional propagation of changes and explicit assumptions at each layer.

When to use it

• Designing architectures or systems that must align strategy with implementation
• Explaining a concept at executive, manager, and engineer levels
• Conducting postmortems and building principles from observed data
• Translating constraints (legal, compliance, performance) into implementation choices
• Aligning cross-functional teams to avoid contradictory tactical decisions

Best practices

• Limit layers to 3–5 (usually strategy → tactics → operations) and name each clearly
• Make assumptions explicit at each layer so changes are traceable
• Regularly run upward, downward, and lateral consistency checks
• Translate messages intentionally for each audience rather than skipping layers
• Propagate changes bidirectionally: top-down for strategy shifts, bottom-up for operational constraints

Example use cases

• Product strategy: from vision to roadmap to user stories and implementation tasks
• Security compliance: translate HIPAA/GDPR constraints into architecture and deployment controls
• Engineering postmortem: turn incident data into tactical fixes and strategic prevention
• Org design: observe team behavior, surface emergent architecture patterns, realign structure
• Technical tradeoffs: evaluate operational costs against strategic priorities and update tactics