[tech] SDD as development workflow

[siarhei-fedziukovich]

Name and Version

0.14.0

What is the problem this feature will solve?

The current development workflow lacks a clear, lightweight Specification-Driven Development (SDD) process. Specifications are either implicit, scattered across documentation, or tightly coupled to implementation details. This leads to:

• Ambiguity in requirements and expected behavior
• Increased back-and-forth between contributors
• Higher risk of misaligned implementations
• Slower onboarding for new developers

Existing tools like Speckit are relatively heavy and introduce additional complexity that discourages consistent adoption across the project.

What is the feature you are proposing to solve the problem?

Introduce a Specification-Driven Development (SDD) approach for the project using OpenSpec, a lightweight and simpler alternative to Speckit.

This feature proposes:

• Adopting OpenSpec as the standard way to define and manage feature specifications
• Defining specs before implementation to act as a single source of truth
• Using OpenSpec’s small, command-based workflow to reduce overhead and improve adoption
• Integrating OpenSpec specs into the development and review process (e.g., PRs reference or include specs)

The goal is to make specifications easy to write, review, and maintain—ensuring clearer requirements, better alignment across the team, and more predictable development outcomes.

What alternatives have you considered?

No response