seed-spec

Immutable core specification documents are locked baseline requirements that enforce structural consistency. They prevent unapproved modifications to core elements while allowing controlled additions to specific sections during the product lifecycle.

To create a core specification document, generate a new spec from Socratic interview outputs. The skill processes the interview data to structure your initial requirements into a formalized, verifiable baseline specification.

You verify specification completeness by validating the document against structural rules to detect missing sections and ambiguous language. This verification ensures the requirements are precise enough before locking the document for immutability.

You can modify a locked specification through controlled evolution. The core elements remain immutable, but the lifecycle management process allows controlled additions or modifications to specific non-core sections according to defined rules.

The best way to manage specification version control is to enforce immutability on locked core elements while defining strict rules for evolution. This controlled lifecycle approach maintains document integrity across product updates.

You should not use an immutable specification approach when core requirements are highly volatile and undefined. The immutability constraints are designed for stable baselines, making it unsuitable for early-stage unstructured exploration.