sap-iac.next
Summary
Role: Utility — run any time. · Reads: local project files · Writes: nothing
Inspects the local project state and recommends the next command in the workflow. It is a read-only helper: it looks only at which specification files exist on disk and never invokes a BTP CLI command or BTP MCP tool.
When to run it
Whenever you lose track of where you are in the flow — after a break, when picking up someone else's project, or before deciding what to run next. It has no prerequisites and changes nothing.
Inputs and outputs
| Reads | The presence of memory/governance.md, specs/scenario.md, specs/landscape.md, specs/services.md, specs/trust.md, specs/connectivity.md, specs/tasks.md, and any terraform/**/*.tf. |
| Writes | Nothing — it only prints a state summary and a recommendation. |
Behaviour
- Walks up from the working directory to find the project root (a directory with
specs/,memory/, andterraform/). If none is found, it tells you to run it from inside asap-iac initproject and stops. - Checks each workflow output file in dependency order and picks the first missing one to recommend. Missing governance is always the first recommendation, although governance remains optional.
- When both
specs/connectivity.mdandspecs/tasks.mdare missing, it recommends/sap-iac.connectivity. You can skip that optional command by running/sap-iac.tasksdirectly. - Once at least one
terraform/**/*.tffile exists, it prints a Done completion message ("Terraform code is interraform/. Review, commit, and apply.") instead of a next-step recommendation. - Prints all rows so you can see your full position in the flow, with
✓for files that exist and✗for those that do not.
Example
/sap-iac.next
For a project that has completed through accounts but not services, next prints:
BTP IaC — Project State
───────────────────────
✓ memory/governance.md
✓ specs/scenario.md
✓ specs/landscape.md
✗ specs/services.md
✗ specs/trust.md
✗ specs/connectivity.md
✗ specs/tasks.md
✗ terraform/**/*.tf
Next: /sap-iac.services — resolve which BTP services each subaccount needs.
Related
- Recommends the next step in the workflow — see the command overview.
- For the full sequence end to end, see the usage walkthrough.