PRD
Product requirements for a module: features, business rules, data model, dependencies, channels and non-functional requirements.
Command: /sf:prd · Methodology: Is2Be Software · Phase: Phase 1 · Ideation
When to use it
Section titled “When to use it”When starting a module or project with no PRD: from existing code (mode A) or from a brief (mode B).
It’s working if
Section titled “It’s working if”- Business rules are verifiable, not generic.
- In modernization, it captures the rules buried in the code and the tech debt.
- It lists dependencies on other modules for the build plan.
- It brings the channels and non-functional requirements with figures and their source; what is unknown stays as an open question.
Where it fits
Section titled “Where it fits”- Before: It’s the first step.
- After: User stories
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 team’s inputs: what this step transforms.
What if the brief falls short?
Ask it to interview you. It asks one thing at a time, with a recommended answer; anything left unanswered goes into the PRD as an open question, not an invented rule.
Does it work for an existing system?
Yes: in Mode A it extracts the business rules buried in the code, including tech debt.
What if it comes from a process brief?
Mode B: the Evidence-First briefing is the direct input, with its IDs.