Install SpecBuddy, write your first spec, and learn the primitives you'll use every day. Short pages, no filler — if it's not here, open an issue.
The loop you'll run every day — describe, propose, review, run one task at a time, review the diff, finish the change.
Install the plugin, connect a coding agent, and make sure OpenSpec is initialised in your project.
One OpenSpec change from a two-paragraph idea to a merged branch, step by step.
The left tool window — every change, spec and agent in the project, with their state at a glance.
Propose or explore from a draft, then review the proposal, spec deltas and tasks before anything runs.
One section of tasks.md at a time, or a chain of them — what a run is, how to start it, and what each state means.
What happens when a run stops — reading the diff, commenting, refining, rolling back, or moving on.
The editor tab where the agent's session lives — what it is doing, what it asks, and the chat to steer it.
Where the agent's code goes, how to keep working while it runs, and how to commit and merge when the change is done.
Sync the deltas into the main specs, archive the change, and merge — with the history kept.
The right tool window — the current change's actions, tasks, diff, documents, comments and history in four tabs.
Use the session's chat for questions, follow-up fixes and running tasks by name — without losing the review.