spec-engineer

Living specs act as the single source of truth for feature domains, maintaining alignment between architectural intent and implemented code. They remain stable references that can be created, updated, or reverse-engineered as your software design evolves.

Updating a living spec after design changes involves refreshing the existing specification document to reflect current reality. You describe the changes across the feature area, and the spec is updated to maintain its accuracy as the single source of truth.

Living specs codify architectural intent as a stable single source of truth, keeping teams aligned between design and implementation. You need them when feature requirements must remain synchronized with evolving source code across any software domain.

Yes, you can generate new specs directly from feature descriptions, requirements, or issue references. You provide the feature domain and intent, and the Spec Engineer creates a living specification aligned to the spec-anchored workflow.

Yes, spec-anchored workflow requires alignment to the specs/{feature-domain}/spec.md directory structure. This standardized path ensures the living specification remains discoverable and serves as the single source of truth for the feature area.