01 · Vendor lock-in
Am I locked into Anthropic / OpenAI / Google?
No. SpecLeap is provider-agnostic by construction, not as a later add-on. The framework makes no calls to any model API: zero traffic to api.anthropic.com, api.openai.com or any other provider.
All the project's "knowledge" lives in .md and .sh files inside your repo. Each assistant reads its own instruction file: Claude reads CLAUDE.md, Cursor reads .cursorrules, GitHub Copilot reads .github/copilot-instructions.md, and so on across 9+ supported assistants.
The specification is the asset, not the model that processes it.
02 · SDD vs vibe coding
Why SDD if "vibe coding" with AI is faster?
Vibe coding is fast at the start and expensive at the end. After 50-100 iterations the AI loses context, contradicts existing patterns, reinvents utilities. You become the long-term memory system.
SDD captures the project's intent once, in an immutable CONTRACT. The AI can iterate 1000 times but always returns to the same north. Vibe coding scales with developer time; SDD scales with spec quality.
03 · Project size
Is it for small projects or only enterprise?
There's a minimum where SpecLeap pays off: roughly one week of real work.
- → Weekend side-project: probably not — the initial survey is overhead you won't recover.
- → 1-4 week project: yes, clearly — a single "no, this isn't what I meant" cycle already costs more than the 20-min survey.
- → Multi-month with several contributors: fundamental.
- → Enterprise / regulated: especially — versioned spec traceability is what audits ask for.
04 · Without Claude Code
Does it work without Claude Code? What do I lose?
Yes, it works with Cursor, Continue.dev, GitHub Copilot, Gemini, Codeium, Tabnine, Cline and any assistant that reads project instruction files.
What you lose without Claude Code: native integration with the 34 Agent Skills (in other assistants the .md files remain accessible but don't auto-load) and the spec-guard.sh hook that ties into the Claude Code runtime (the equivalent protection is covered by the independent pre-push git hook).
What you DON'T lose: CONTRACT, agents, commands, memory-bank, specs, Asana/CodeRabbit integration, the survey, the openspec CLI — all the same.
05 · Switching provider
What if I want to switch AI provider mid-project?
You do it without losing anything. But the "how" depends on your setup, because AI provider, assistant and IDE are three distinct layers:
AI Provider
Anthropic, OpenAI, Google, Meta
Assistant
Claude Code, Continue.dev, Copilot, Cmd-K
IDE
VSCode, Cursor, JetBrains, Vim
If you use Cursor or Continue.dev, switching provider is a click in their settings. If you use Claude Code and want to move to OpenAI, you swap extensions (not necessarily IDEs). If you switch IDE entirely, you open the repo in the new IDE and the full context is still there. The .md and .sh files stay intact no matter what.
06 · Asana
Do I need Asana mandatorily?
For some commands yes (crear-tickets, planificar, status updates inside implementar). For the bulk of the framework, no.
Without Asana these still work: survey, CONTRACT, agents, commands refinar / documentar / explicar / compliance / adoptar, the 34 Agent Skills, the full openspec CLI, memory-bank, global standards and the 3-layer validation pipeline. If your team uses Linear, Jira, Notion or GitHub Issues, you can manage the backlog manually.
07 · Team + CONTRACT
How does it scale with a team? Conflicts on CONTRACT?
The CONTRACT is immutable by design, so classic conflicts on that file don't exist. Changes to the original scope go to ANEXOS.md (append-only, versioned). Technical decisions go to context/decisions.md with date and author.
Each feature in its branch feature/<project>-<ticket>-<desc>, PR against stage, then PR against main. CodeRabbit reviews against CONTRACT + standards. The 3-layer pipeline validates before merge.
08 · TDD / Agile
Does it replace TDD / Agile / Scrum?
No, it complements them. Each operates at a different layer:
- → SDD (SpecLeap): project's long-term memory — what's being built and why.
- → TDD: how you write code (test first).
- → Agile / Scrum: how you organize work over time.
SpecLeap is the missing layer in the methodology stack now that AI writes the code. They coexist without friction: your CONTRACT doesn't clash with your sprint board, your TDD tests don't clash with your specs, and your Scrum Definition of Done is enriched by SpecLeap's 3-layer validation pipeline.
Question not covered? Write to info@specleap.com or open an issue on GitHub.