Add SpecBuddy to plugins and an OpenSpec walkthrough to articles

[alexander-shustanov]

Two entries. Disclosure: I'm SpecBuddy's author.

OpenSpec as Integration or Plugin

- [SpecBuddy](https://specbuddy.dev/#openspec) - JetBrains and VS Code plugin driving /opsx commands with in-IDE delta review and per-step gates.

SpecBuddy drives the /opsx:* commands against the openspec/ directory you already have — nothing to migrate, it just needs the openspec CLI on your PATH. What it adds is the part OpenSpec leaves to the terminal:

• a change is proposed from an editor tab (/opsx:explore, /opsx:propose), and shows up in a Spec Explorer as a unit of work with its state on the row — Draft, 3/7 tasks, Review;
• a delta spec is read beside the main spec it modifies: a gutter marker on a MODIFIED requirement jumps to the original in openspec/specs/, or shows both as a diff, and a main spec lists the active changes targeting it;
• tasks.md runs a group at a time behind a review gate, so you see a diff per step instead of one diff at the end;
• WHEN/THEN scenarios get line comments the way you'd review a pull request;
• archive writes back what actually shipped.

Ships for JetBrains IDEs and for VS Code / Open VSX. The section already lists intellij-openspec and several VS Code extensions, so this sits alongside those; the difference is that the review surface, not the spec browser, is the point.

Articles & Tutorials

- [OpenSpec with SpecBuddy](https://specbuddy.dev/blog/openspec-with-specbuddy/) - Reviewing an OpenSpec change step by step inside your IDE.

Walkthrough of the same loop on a real change — where /opsx:apply leaves you as a passenger, and what a step boundary with a human at it looks like.

Checks

• Both entries inserted in alphabetical order within their sections (after opsx-feature-dev, and after OpenSpec on IntentDriven).
• npm run lint — no new warnings. The one that remains (README.md:105, 164 chars on openspec-ui-vscode) is pre-existing on main; I left it alone rather than touch an unrelated line.
• Lines are 145 and 141 characters, both under the 150 limit.
• Links checked: both return 200.

Happy to drop the article entry and keep only the plugin, or to reword either description.

[mipmip]

Nice website. Please remove the article/tutorial entry. This is only for generic contributions, and not to promote products other stuff besides the OpenSpec project itself.

Before I want to add this, you should make clear on your website if your product is a commercial or open source product now and in the future. It says it's free but it is unclear if this is a freemium, a cloud service, or a product in beta stage which will cost money in the future. Because I don't see a github or other project page it is unclear how populair and relevant this is.

I'm not against commercial products but intention of software should be very clear before I can add links to this awesome list.

[alexander-shustanov]

Hello, thank you for the reply! The product is free, but I’m not ruling out switching to a freemium model in the future. At the very least, I don’t have any such plans right now.