Authentication/authorization module
Reusable identity verification and access control — with an explicit decision on whether it applies to this project.
Command: /sf:auth-module · Methodology: Is2Be Software · Phase: Phase 3 · Development
When to use it
Section titled “When to use it”Once, with the first module that needs to tell who is making a request and what they can do.
It’s working if
Section titled “It’s working if”- It makes explicit whether it applied to the project, and why.
- It tells ‘not authenticated’ apart from ‘not authorized’ — never the same message.
- It validates any identity coming from outside — never trusts a header without verifying it.
- In a mobile or desktop client it uses PKCE and never embeds a secret in the app.
Where it fits
Section titled “Where it fits”- Before: Test plan, PRD
- After: Backend module
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).