organon-tools-developer

To enforce Organon methodology constraints when adding CLI commands, load ETHOS.md and PHILOSOPHY.md before development, then validate work against the 6 invariants and 5 design principles to ensure schema fidelity, test coverage, and fail-fast behavior.

The core invariants for Organon verification gates and MCP tools require schema fidelity, mandatory command tests, gates that fail builds, machine-parsable output, idempotent operations, and major version bumps for breaking changes to ensure safe tooling evolution.

Organon tools development changes risk breaking methodology alignment when they diverge from ETHOS.md and PHILOSOPHY.md constraints, which this Skill prevents by requiring architecture docs to load first and validating invariants before new CLI commands or MCP tools are finalized.

You cannot safely evolve the Organon methodology specification without loading ETHOS.md, PHILOSOPHY.md, and related frontmatter specifications first, as this loading step is a strict prerequisite to ensure design principles like composability and testability are followed.

The best way to structure tests for Organon CLI commands and MCP tools is to apply the testability design principle alongside the invariant requiring every command to have tests, ensuring gates fail builds and operations remain idempotent during methodology evolution.

You should use Organon methodology enforcement whenever adding CLI commands, verification gates, or MCP tools, or evolving book-llms specs, to ensure structured guidance and tests validate invariants like machine-parsable output and breaking change version bumps.