Add a new feature
Describe what you want, get a full spec, and build it.
Build anything, with guardrails
Your MVP is live. Now you need a feature that wasn't in the original plan. A team workspace with invites. An admin dashboard. A public API. Something a user asked for that you hadn't thought of.
Inside Claude Code, type /spec followed by what you want. The system runs an interactive spec process. It figures out whether the feature is backend-only, frontend-only, or full-stack. It checks if external APIs are involved and researches them if needed. It asks you targeted questions about edge cases and permissions, then writes a production-grade specification.
What the process looks like
You describe the feature in plain language. The system reads your existing codebase, your built features, and your project docs. It understands what's already there.
If the feature involves an external service the system hasn't seen before, it goes and researches it. API docs, pricing, rate limits, TypeScript SDK. It comes back with what it learned and factors it into the spec.
Then it asks you the questions that matter. Not twenty questions about every edge case. The specific questions that, if left unanswered, would cause problems during the build. Permissions. Pricing tier restrictions. What happens on mobile. What happens when things fail.
The spec gets written, and you review it. If something's off, you say so and it adjusts. When you're happy with it, you can tell it to plan and build in the same session, or save the spec and come back to it later.
Example
Inside Claude Code, you'd type something like:
/spec add a team workspace where the owner can invite members by email.
Invitees get a link, accept or decline. Free plan gets 3 seats, Pro gets 20.That's it. The system handles the rest.