methodology-spec-evolution

Propagate methodology specification changes across related organon files.

Updated Feb 8, 2026

Search Tags:#versioning #documentation #consistency #terminology #evolve #organon

Ready to run

npx skills add https://github.com/VledicFranco/organon --skill methodology-spec-evolution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: methodology-spec-evolution
Source: https://github.com/VledicFranco/organon/tree/main/.claude/skills/methodology-spec-evolution
Command: npx skills add https://github.com/VledicFranco/organon --skill methodology-spec-evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides the evolution of book-llms/ methodology specification files to maintain cross-file consistency, govern version bumps, propagate terminology, and enforce backward compatibility during changes.

Core Features & Use Cases

Ensures propagated changes across ETHOS.md, PHILOSOPHY.md, overview.md, CLAUDE.md and related frontmatter invariants whenever a file in book-llms/ is modified.
Coordinates version bumps, terminology propagation, and compatibility checks to reduce drift and errors in methodology evolution.
Acts as a governance guardrail for high-risk specification changes in book-llms/.

Quick Start

Review the affected files, propagate changes across related organon files, and verify invariants to prevent drift.

Frequently Asked Questions about methodology-spec-evolution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain cross-file consistency when updating methodology specifications?▼

Methodology specification evolution propagates changes across related organon files like ETHOS.md and PHILOSOPHY.md, coordinating version bumps and terminology to prevent cross-file drift.

What is the best way to propagate terminology changes across book-llms documentation files?▼

The best way to propagate terminology changes across book-llms files is by loading core documents like overview.md and CLAUDE.md to enforce invariants and apply updates via frontmatter and templates.

Why does methodology specification drift occur in cross-file documentation?▼

Methodology specification drift occurs when modifying files in book-llms/ without coordinating version bumps, terminology propagation, and backward-compatibility checks across related organon files.

How do I enforce backward compatibility when modifying methodology specs?▼

Enforce backward compatibility when modifying methodology specs by applying governance guardrails that verify invariants and check compatibility across ETHOS.md, PHILOSOPHY.md, overview.md, and CLAUDE.md before finalizing changes.

Can I use frontmatter and templates to govern specification version bumps?▼

Yes, you can use frontmatter and templates to govern specification version bumps by propagating methodology changes across related organon files and enforcing invariants loaded from core documents.

When do I need cross-file methodology specification governance?▼

You need cross-file methodology specification governance when modifying any file in book-llms/ to ensure high-risk specification changes maintain consistency, propagate terminology, and enforce compatibility across the documentation suite.