Before execution, read Workflow Execution Conventions: first read the user materials, locate resources from this installation location, and work according to the real tool capabilities.
Trigger Scope
Used to turn a business idea into a BRD, interview for business requirements, or organize existing business materials. When only modifying an existing document fragment, handle only the specified fragment and do not restart the full interview. Not used to replace API/HLD/LLD design or business approval.
Mandatory Constraints
- Preserve the original intent; the BRD focuses on WHAT/WHY, target users, scope, definition of success, dependencies, and constraints.
- Cite known facts directly; mark uncertain information as assumptions, and do not decide or approve on the user's behalf.
- Each interview round has at most 2-3 key questions; respect the checkpoints specified by the user.
- First follow Interview Modes and Fact Standards to choose
interview/synthesis/gap_followup. Quantification is not a hard gate for all tasks; measurements, estimates, measurement plans, and discrete acceptance are recorded separately. - By default follow the user's language; explicit language requirements take priority. Field names, enums, IDs, and comment markers remain in English, see Language Rules。
Minimal Workflow
- Read the specified materials, original goals, and existing approval basis; do not treat a filename or label as approval.
- Determine whether this needs a local edit, interview, or material organization; do not repeatedly ask the user for content they already have.
- If the materials are sufficient, organize them directly; if there is only local ambiguity, ask only about the gap. When an interview is needed, complete it according to the relevant stage of the Interview Question Bank , without reading every question from the start.
- When generating a document, read the Chinese template or English templateaccording to the user's language. Use the path the user has specified; if there is no path, choose a reasonable default within the workspace and explain it.
- Check scope, definition of success, dependencies, and assumptions. If historical values are missing, you can still deliver a clearly marked draft; do not guess numbers and do not block on the number of assumptions. If only a draft is requested, keep it as a draft; formal approval must have a real basis in the corresponding version/scope.
- Return the actual files, sources, open items, and delivery status, and do not proactively proceed to implementation or release.
On-Demand Resources
| Situation | Resource |
|---|---|
| Need specific questions, branches, or the current exit checklist | Interview Question Bank |
| Need a method for organizing questions | Interview Framework |
| Need communication techniques | Consultant Style |
| Involves industry-specific requirements | Fintech、Healthcare、B2B SaaS、Retail、Manufacturing, read only the relevant branch |
Technical suggestions can be retained in an appendix with a note that they are pending evaluation; do not derive business thresholds the user did not provide from technical names. Interface contracts, architecture, and implementation details are left to the API/HLD/LLD responsibilities respectively.
Usage Examples
- "The boss wants to build a membership system, but the goals are still unclear": first interview for the key business gaps.
- "Organize a BRD based on these meeting notes": first read the notes, reuse known facts, and do not ask all the questions again.
- "Only change the product name in the BRD": make a local modification and check the diff, without loading the industry questionnaire or reopening the exit criteria.