spec-driven-dev

To plan and verify bounded software changes, you can use a phased workflow that captures explicit requirements from diffs and logs, implements the scoped modifications, and executes evidence-based verification against acceptance criteria.

The best way to implement a feature with explicit requirements is using a strict Discover, Write, Implement, and Verify workflow that tracks implementation steps and provides evidence-based verification for the scoped software changes.

You scope a bug fix by processing workspace files and pasted code during the Discover phase to define explicit requirements and assumptions, which then drive a tracked implementation and verification pass.

Yes, you can batch reads, writes, and verifications per phase to maximize progress and minimize context switches, ensuring consecutive and unblocked progression through the Discover, Write, Implement, and Verify workflow.

Spec-driven development works for investigations by capturing explicit requirements and assumptions upfront, then producing evidence-based verification from diffs and logs to validate the investigative findings.