Briefing for Spec-First
The bridge to software: turns the part of the To-Be that needs development into the PRD’s input.
Command: /ef:sdlc-briefing · Methodology: Is2Be Process · Phase: Phase 6 · Implementation
When to use it
Section titled “When to use it”Only if the team decides the To-Be needs software.
It’s working if
Section titled “It’s working if”- It makes sense without knowing BPMN or the process documentation.
- It copies business rules verbatim and keeps the IDs.
- It describes the what, not the technical how.
- It brings the non-functional requirements and channels with their source (baseline, simulation) or as an open question.
Where it fits
Section titled “Where it fits”- Before: To-Be model
- After: It’s the last step on its path.
Requirements
Section titled “Requirements”-
Your AI connected to the service with your licence key (how to connect).
-
The project set up once with
/ef:setup. -
The outputs of the previous steps (see Where it fits).
Why doesn’t it propose the architecture?
Because that’s decided in Spec-First’s Phase 2, with its options and ADR. The briefing describes the what, not the how.
Will a team that doesn’t know BPMN understand it?
Yes: it’s written in business language and stands on its own.