What's new

October 2026 · Is2Be 1.1

The architecture starts by asking what it needs (app type, users, cloud or provider, what your team can run, budget), each question with a recommended answer, and fits the detail to your project: a small app with its API gets two options in a few minutes.
Separate decisions: topology, internal architecture (layers, hexagonal, clean, vertical slices), communication, client type, hosting and provider with its managed services, on any cloud. The result is a decision sheet that development, testing and deployment follow.
Mobile apps, native or cross-platform: permissions, secure storage, offline and notifications; tests on emulators or devices; signing and app store publishing.
The PRD captures channels and non-functional requirements, and infrastructure as code is part of deployment.

First stable version, the launch one.

Connect your AI with your key and you’re done: steps are served live, always in the version your plan gives you.
Is2Be Software goes from 22 to 27 steps: acceptance scenarios (tests check the result the business approves, not what the code already does), functional flow and technical sequence diagrams, technical stories, an auth module and end-to-end tests with no UI. The backend module and its tests work with any kind of interface (HTTP, GraphQL, gRPC, events, jobs or CLI).
The backend module also covers adding an entity to an existing system: one step for new projects and for systems that already have code.
Is2Be Process: the same 37 steps.

Every step checks its own work: before handing over, the assistant checks the result against that step’s “It’s working if” criteria.
Interview mode for the charter and the PRD: if you have little information, it asks one thing at a time, with a recommended answer, before writing.

FAQ and requirements on the main skill pages.
Spec-First now has 22 steps: an E2E testing step already covered by the test plan has been retired.

Commands in English (/ef:discovery-synthesis, /sf:test-plan…). The content is still in Spanish.
Less always-on context: in Claude Code, each step’s skill only loads when you type the command.
The support skills are now called start, setup and reference.

The methodologies as skills: a Claude Code plugin and the same collection for other assistants that support Agent Skills.
setup: sets up the project by asking in rounds, with a recommended answer for every question.
Route guide: which mode and which commands to follow for your situation.

First version of the kit: the version for the client’s AI and the project template, adaptable to each organization.
First example case, with a 30-minute demo script.