openspec-workflow

Spec-driven development clarifies requirements before coding through structured proposals, delta specifications, and design artifacts. It enforces artifact templates and structured verification to align outcomes with business goals, minimizing miscommunication and rework.

You manage parallel changes by creating individual proposals and delta specs for each change. The workflow enables multiple changes to progress concurrently with clear handoffs and structured task breakdowns to ensure smooth integration.

Yes, the workflow supports guided paths for both quick feature development and exploratory work. It accommodates fast iterations by allowing you to define delta specs, designs, and tasks without heavy overhead.

You enforce consistency by using provided artifact templates for specs, designs, and tasks. The workflow also mandates RFC 2119 keyword usage to clarify requirement levels and ensure structured verification across the team.

After creating a delta spec, the workflow guides you through designing architecture and breaking down tasks using structured templates. This ensures tasks align with the delta specification and business goals before coding begins.

You should avoid spec-driven workflows for trivial changes requiring no architectural decisions or when immediate ad-hoc fixes are necessary. The overhead of creating proposals, delta specs, and design artifacts outweighs the benefits for simple modifications.