organon-file-creation

You can generate organon documentation with correct frontmatter by running this skill, which automates the creation of ETHOS.md, PHILOSOPHY.md, PROTOCOL.md, and README.md files while enforcing placement and reference integrity.

Organon documentation files drift from parent scope constraints when created ad hoc without enforcing inheritance. This skill solves the problem by automating validation and ensuring bidirectional references and constraints are never relaxed.

The best way to add a new domain to organon documentation is to run this skill, which generates a complete file set with standardized templates, protocol mappings, and required toolchain commands for formal scope creation.

You do not need external templates to create valid organon documentation, because this skill integrates built-in loading guides, validates frontmatter, and enforces reference integrity through defined protocol mappings automatically.

You can use this workflow to add a new feature scope without breaking references, as it enforces bidirectional references and parent-scope inheritance to ensure all documentation artifacts remain structurally valid.

The limitations of ad hoc organon file creation include inconsistent structure, missing references, and drift from parent scope constraints, which this skill resolves through enforced templates, validations, and required toolchain commands.