Every OpenSpec command is ultimately working with these three things. Understand what specs are, what changes are, and what each artifact represents — and everything that follows will make sense.
From 'I have an idea' to 'implementation done, spec archived' — walk through OpenSpec's three core commands, what each one does, what you need to verify, and when to move forward.
You've learned the workflow — but how do you apply it when real work starts? This article walks through the three most common scenarios: new feature development, bug fixes, and bringing OpenSpec into a legacy project.
For everyone who keeps going in circles when asking AI to write code — this is the OpenSpec series overview, taking you from 'why write specs at all' to 'running a complete workflow,' all in five articles.
You ask AI to add a feature, it works hard, but the result keeps drifting — not because the model isn't smart enough, but because nobody clearly stated what needed to be done. This article explains what problem OpenSpec solves.
Install OpenSpec, initialize your project, and understand the directory structure — this article is pure action. Once done, your codebase can start using spec-driven AI development.
A series overview for developers new to CMUX — quickly understand what problem it solves, how to learn it, and the recommended reading order.
CMUX is a lightweight native macOS terminal built on Ghostty, designed specifically for managing multiple AI agents. This article explains what problem it solves, how it differs from tmux, and who it's for.
Complete CMUX installation guide: choose between DMG or Homebrew, set up the CLI symlink, verify the installation, and understand the auto-update mechanism.
CMUX is built around three core layers: Workspace, Pane, and Surface. Understanding these three layers is what lets you allocate AI agents, switch contexts, and make sense of CMUX's visual interface.