Backend module
A complete domain module (new project or an entity in an existing system), with any kind of input interface.
Command: /sf:backend-module · Methodology: Is2Be Software · Phase: Phase 3 · Development
When to use it
Section titled “When to use it”When building each module or entity identified in Phase 1 — in a new project or an existing system.
It’s working if
Section titled “It’s working if”- It preserves the PRD’s business rules exactly.
- Its entry layer adapts to the interface type, without forcing an HTTP controller where there isn’t one.
- It ships with tests and coverage from the first commit.
- In an existing system, the result is indistinguishable in style from the rest of the system.
- No operation exists just because “CRUD asks for it”: each one answers a rule from the PRD or the stories.
- It is organised according to the chosen internal architecture (layers, hexagonal, clean or vertical slices).
Where it fits
Section titled “Where it fits”- Before: Test plan, PRD, Authentication/authorization module
- After: Unit tests, Integration tests, Code review
Requirements
Section titled “Requirements”-
Your AI connected to the service with your licence key (how to connect).
-
The project set up once with
/sf:setup. -
The outputs of the previous steps (see Where it fits).