OpenSpec tutorial: setup and spec-driven development

This beginner tutorial explains how OpenSpec organizes requirements and implementation plans for a coding assistant. The speaker uses Claude Code in Android Studio to build a two-screen to-do app for Android and iOS, with Compose Multiplatform, a Material 3 theme and a local Room database. Following along requires an agent harness and a terminal; an IDE or code editor is recommended.

Setup covers installing the CLI through npm, or Homebrew on macOS, then initializing the project and selecting supported agent tools. The walkthrough uses exploration to clarify requirements before creating a proposal. One concrete revision replaces autosave with an explicit save button after the discussion exposes awkward empty-title behavior.

The generated Markdown files separate capability requirements, the overall proposal, technical design and an ordered task checklist. The speaker explains how project conventions belong in config.yaml and shows a fresh session using the saved documents to implement the change. Delta specs record changes to existing requirements.

The comparison favors OpenSpec's lighter workflow over GitHub Spec Kit's verbosity and Kiro's dedicated IDE, reflecting the speaker's preferences. Verification remains limited: he skips automated tests for the example and stops the agent's final checks to try the app manually. He closes by recommending unit tests, end-to-end tests and verification for larger projects.