Acceptance scenarios
Concrete examples of every business rule (boundary values, rule combinations) with their expected result, traced to the PRD and the stories, in the format the team chooses.
Command: /sf:acceptance-scenarios · Methodology: Is2Be Software · Phase: Phase 1 · Ideation
When to use it
Section titled “When to use it”Once the PRD and user stories have been reviewed, before design.
It’s working if
Section titled “It’s working if”- Every critical business rule has at least one scenario in the coverage table.
- Every threshold is tested at its boundary, on both sides, and every value says why it was chosen.
- No expected result is made up: what the PRD doesn’t answer stays as an open question.
- The business can read every scenario and confirm the result without technical knowledge.
Where it fits
Section titled “Where it fits”- Before: User stories
- After: Test plan, Unit tests
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).
Why in Phase 1 and not in testing?
Because the business sets the expected result before any code exists, so tests check what the system should do, not what it already does.
Do I have to use Gherkin?
No. The default is structured Markdown; the team can ask for Gherkin, their test manager’s template or another format, with the same fields.