Spec Kit and OpenCode: setup and spec-driven development

This tutorial follows GitHub's Spec Kit workflow to build a task management app with OpenCode. The speaker presents specifications as a way to reduce the unstated assumptions a coding assistant turns into code. Setup starts with installing specify-cli through uv, creating a project, selecting an agent, and choosing shell scripts.

A project constitution records guiding principles and app-specific rules. The first specification describes the application's features. The clarify step checks for gaps and conflicts with the constitution or earlier specs, then asks the developer to resolve ambiguities. Planning produces documents covering requirements and decisions; the tasks step breaks that plan into phased work for the AI agent.

The demonstration then moves through implementation on a feature branch and a converge review. The speaker describes converge as a check of completed work that can append tasks for another implementation pass. He reports 70 passing tests and demonstrates task creation, editing, status changes, tags, and due dates. He also notes that the initial interface looks rough because he did not specify its design.

Further features use new specs and repeat the workflow. The speaker's tradeoff is explicit: planning and documentation take longer than a quick one-shot attempt, but retain a decision history that can support later development and bug reports.