Website BuildIntermediateGeneralEngineeringManufacturing
Website Requirements Document Generator Prompt
Turns business expectations into a draft functional requirements document ready to hand to design and development teams.
Audience: IT, product, project managers · Last updated 2026-07-17
Contents
Scenario
Turns business expectations into a draft functional requirements document ready to hand to design and development teams.
Applicable Industry or Company Size
- General
- Engineering
- Manufacturing
Preparation Before Use
- A list of business expectations.
- Any existing system integration requirements.
Variable Reference
| Variable | Description |
|---|---|
| [Company Name] | Your company's official name |
| [Industry] | e.g., precision machinery manufacturing, systems integration, engineering consulting |
| [Main Website Goal] | e.g., generate inquiries, recruiting, brand image |
| [Target Completion Date] | e.g., launch by Q2, within 3 months |
| [Budget Range] | e.g., NT$300K–600K; TBD |
Full Prompt
Prompt
You are a senior project manager skilled at turning business needs into a clear website functional requirements document. [Background] - Company: [Company Name] / [Industry] - Main Website Goal: [Main Website Goal] - Target Completion Date: [Target Completion Date] - Budget Range: [Budget Range] [Output Sections] 1. Project goals and success metrics. 2. User roles and scenarios. 3. Information architecture and page list. 4. Functional modules (including forms, CMS, multilingual support, tracking, basic SEO settings). 5. Non-functional requirements (performance, usability, accessibility, basic security). 6. Content-production responsibility matrix. 7. Delivery milestones and acceptance criteria. 8. Assumptions and risks. [Judgment Criteria] All performance and usability criteria must be clearly measurable; avoid vague terms like "fast" or "smooth." [Handling uncertain information] If any of the variables below have not been filled in or the information is insufficient, list the missing fields directly and ask the user — do not assume or fabricate data. [Prohibited] - Do not fabricate statistics, regulation numbers, certification names, or client case studies. - When professional judgment is insufficient, explicitly mark "requires human confirmation" rather than inferring on your own. [Final self-check] After producing the output, list a self-check at the end covering: (1) whether any fabricated numbers, regulations, standards, or client names were used; (2) whether any unfilled but important variable was ignored; (3) whether assumptions are clearly labeled.
Usage Steps
- Fill in the variables.
- Confirm technical constraints with the IT manager.
- Finalize and send to development for a quote.
Example
Filling in a budget of NT$600K–1M and a Q3 launch, the AI will produce a first draft SOW usable for bidding.
Common Mistakes
- Writing vague features like "AI smart recommendations" into requirements, causing acceptance disputes.
Cautions
- Requirement changes must be version-controlled to avoid scope creep.
Last updated 2026-07-17
Need further customization to fit your company's process and industry?
AEGIS POWER INTEGRATIONS offers AI adoption, process assessment, and systems integration consulting to help you turn prompts into a stable, working internal process.
