To-be architecture options
Asks what is missing and proposes target architectures on six axes (topology, internal architecture, communication, client type, hosting, provider), with the detail the scale calls for and a decision sheet.
Command: /sf:to-be-architecture · Methodology: Is2Be Software · Phase: Phase 2 · Design
When to use it
Section titled “When to use it”With the Phase 1 PRDs (and the as-is, if there is an existing system). For a small app with its API, in its minimal version.
It’s working if
Section titled “It’s working if”- It asks before proposing and doesn’t assume what nobody answered: it marks it as an assumption.
- It treats topology, internal architecture, communication, client, hosting and provider as separate decisions.
- The detail matches the scale: a small app doesn’t get ten pages.
- It ends with a decision sheet that ADR-001 can fix as is.
Where it fits
Section titled “Where it fits”- Before: User stories, As-is architecture
- After: ADR (Architecture Decision Record)
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).
What if my project is small, a mobile app with its API?
One round of five questions with recommended answers, two options and a short recommendation. A few minutes.
Does it force a specific cloud provider?
No. It asks whether you already have one and compares services by category; provider names are only examples.