openspec-writing-guide

User-facing specifications should organize content by UI context and express validations as user interactions while avoiding technical implementation details in the spec body. This approach ensures clarity and consistency across project specifications.

An OpenSpec file separates functional and non-functional content by structuring user scenarios around UI context organization and keeping technical implementation details out of the specification body. This maintains canonical style and improves spec maintainability.

Canonical Klabis OpenSpec style emphasizes user-facing scenarios, UI-context organization, and clear separation of functional versus non-functional content. The reference example of this correct style is found in the user-groups spec.md file.

Validations are expressed as user interactions by framing them within user-facing scenarios organized by UI context rather than describing technical validation logic. This ensures specifications remain clear and focused on user experience.

You need the OpenSpec writing guide when drafting, reviewing, or rewriting openspec/specs files in the Klabis project to ensure canonical style, UI-context organization, and appropriate separation of functional and non-functional content.

Avoiding technical implementation details in the specification body ensures the spec remains user-facing and clear. Separating functional and non-functional content improves collaboration, reviews, and maintainability across the project.