pantheon

What problem does it solve? When facing a design fork—module boundaries, abstraction urges, dependency choices, scope cuts, or state modeling—engineers often lack a consistent decision framework. This Skill maps the current design problem to a curated registry of sixteen software engineering ancestors (Ousterhout, Pike, Dijkstra, Hickey, Lamport, and others) and returns a compressed, greppable doctrine verdict. ## Core Features & Use Cases - Persona Selection: Matches the task at hand to the appropriate ancestor doctrine, such as Ousterhout for boundary design, Meyer for validation contracts, or Dijkstra for state enumeration. - Conflict Arbitration: Resolves colliding doctrines with explicit domain-owner rules, for example Pike vetoes cleverness and Brooks governs dependency decisions. - Decision Audit Trail: Emits greppable PANTHEON: verdict lines that can be mined into akatsuki project notes as lightweight ADR material. - Use Case: When debating whether to add a new abstraction layer, invoke the Skill to receive a verdict like PANTHEON: McIlroy — wait for the third identical occurrence before abstracting. ## Quick Start Ask the agent to invoke pantheon and arbitrate which ancestor doctrine applies to your current design decision, such as choosing between a new dependency and a stdlib solution.