AI workflows just clicked.
Imagine this: you’re knee-deep in a project, requirements swirling like a brainstorm gone wild, but instead of typing cryptic slash commands into a chat window, a sleek sidebar lights up—phases glowing, approvals waiting, documents streaming live from your LLM of choice. That’s Caramelo, the VS Code extension that finally makes spec-driven development feel like the future it is.
And here’s the thing—it’s not locked to one AI overlord. Plug in GitHub Copilot, fire up local Ollama, or hit Claude through your company’s proxy. Freedom, baby.
Why Ditch GitHub’s Spec Kit for This?
Spec Kit? Solid start. You define needs, AI spits out specs, plans, tasks. But it’s all text in a chat—/speckit.specify, paste output, /speckit.plan. No visuals. No tracking. Feels like coding in the ’90s, command-line only.
Kiro from Amazon? Visual, sure—but fork VS Code, tie to their LLM. Nah.
Caramelo nails it: native VS Code, any LLM, visual from top to bottom. Click a preset, enter creds (or none for Copilot), boom—workflow alive.
Phases lock step-by-step. Approve Requirements (spec.md streams in), unlock Design (plan.md, research.md, data-model.md). Tasks next. Edit, regenerate, stale flags pop. It’s like a video game level-up, but for code.
Each phase must be approved before the next unlocks: Requirements → generates spec.md; Design → generates plan.md + research.md + data-model.md; Tasks → generates tasks.md.
That’s straight from the builder’s notes—pure gold.
Your project’s constitution? Non-negotiables like “TDD or bust” or “Error handling everywhere.” AI generates it if you describe the project. Injected into every prompt. Genius guardrails.
One paragraph wonder: Teams, rejoice—Jira sync.
How Does Caramelo Tame Any LLM?
Multi-provider madness. “Claude Personal” vs. “Claude Corp”—different keys, endpoints, even custom auth headers for Azure or AWS gateways. Dot-indicator switch. Models auto-fetch or manual, validated.
No bloat: 170KB bundle. Native fetch + SSE parser. vscode.lm for Copilot. No React, no CLI. WebviewView crushes it—forms, progress rings, checklists in HTML/CSS.
Streaming? 150 lines cover OpenAI/Anthropic + Copilot. Corporate hacks? Configurable headers fix the mess.
But wait—state-driven UI. Early postMessage hacks broke on refresh. Now? editingState re-renders full HTML. Reliable as a Swiss watch.
Will Jira + Caramelo End Spec Hell?
“From Jira” button. Search boards (even 2000+), grab issue PROJ-123. Title, desc, ACs, comments → spec input. Badge links back. Tasks? Actionable—Run Task (LLM codes it), Run All (parallel [P] respected), output channel watches reasoning, progress %, inline checklists.
Verify? Clarify ambiguities (QuickPicks), Analyze consistency (severity reports), Fix Issues (one-click), checklists galore. All from cat-icon dropdown. Toolbar stays clean.
Proved in wild: Built Caramelo with Caramelo. Specify → clarify → plan → tasks → implement. Loop closed.
Look, here’s my bold take—and it’s fresh: This echoes the IDE revolution. Remember punch cards to Turbo Pascal? Visual feedback exploded productivity. Caramelo’s the Turbo Pascal for AI agents—specs as blueprints, visuals as the canvas. In five years, spec-driven won’t be optional; it’ll be how humans direct AI swarms. Hype? No—Spec Kit’s success proves demand. Caramelo just scales it.
Energy building? Yeah.
Short burst: Install now—VS Code marketplace, “Caramelo.”
Deeper dive: No external deps. Syncs Spec Kit templates. specs/ folder compatible. WebviewView replaced three TreeViews—pure power.
SSE simple. Providers: 95% covered.
Enterprise? Headers configurable—essential.
Wander a sec: Ever regen a spec, watch downstream flag stale? Chef’s kiss.
Tasks aren’t lists—they’re buttons to code. Progress rings fill. Checklists toggle. Output streams reasoning—trust the black box less.
Why This Matters for Every Dev
Spec-driven shifts AI from toy to teammate. Define first, generate structured. No hallucinated rabbit holes.
Visuals? Pace accelerates. Approvals force think-time. Constitutions curb over-engineering.
Prediction: Devs using this hit 2x velocity. Why? Friction gone. Like autocomplete on steroids, but for whole projects.
Skepticism? It’s indie—~170KB screams lean. No vendor lock. Open? Check marketplace.
And teams—Jira bridge means no more copy-paste hell.
One sentence: Future’s visual, flexible, yours.
🧬 Related Insights
- Read more: Python Dev’s Laravel IAM Gambit: Fixing RBAC or Just Another Package?
- Read more: SonarQube’s Free Community Build: 5,000 Rules, Zero Branch Analysis – The Real 2026 Tradeoff
Frequently Asked Questions
What is Caramelo VS Code extension? Caramelo’s a free extension for visual spec-driven development in VS Code, supporting any LLM for generating specs, plans, and tasks with approvals and Jira integration.
Does Caramelo work with local LLMs like Ollama? Yes—plug-and-play with Ollama, LM Studio, no API keys needed, plus cloud options like Claude or Copilot.
How does Caramelo improve on GitHub Spec Kit? Visual UI, progress tracking, any-LLM support, Jira sync—turns chat commands into a smooth, approving workflow.
