d8maldon/council-skills

Behavioural guidelines for software engineering, named after the master craftsman of Greek mythology. Ships the tenets skill: think before coding (state assumptions, present multiple interpretations, ask when unclear), simplicity first (minimum code, no speculative features or abstractions), surgical changes (touch only what the request requires, match existing style, clean up only your own mess), and goal-driven execution (define success criteria so the loop can verify independently). Bias toward caution over speed.

Five-council audit protocol named after the divine assembly: athena (currently-active math + controls), mnemosyne (historical math + control-theory founders + estimation classics), hephaestus (present-day engineering authorities), prometheus (founders + modern leaders of AI/ML/CS), hermes (founders + modern leaders of vehicle dynamics). Each skill carries the Step-0 council-log discipline (read notes/council-log.md before any audit) to prevent compounding review loops.