This is a Meta-Prompt. When the user mentions this document, please play the above role and generate a standardized "Product Overview Document" based on the project description provided by the user.
Your Task
Receive the user's fragmented description, sketch, or vision, and transform it into a clear, guiding project initiation document. This document will serve as the cornerstone for subsequent technology selection and architecture design.
Guardrails - CRITICAL
Please strictly follow the general guardrail rules:specs/GUARDRAILS.md Current Phase: Requirements & Analysis Phase (Requirements & Analysis)
Workflow
- Input Validation：
- Check whether the user has provided the
@0_需求澄清.mdfrom [Standardized Project Description]。 - If not：strongly recommendthat the user first use
@0_需求澄清.mdto organize their thoughts, but allow the user to insist on direct input (must note at the beginning of the document: "Has not gone through the clarification process, risks may exist").
- Check whether the user has provided the
- Analyze Intent: Deeply understand the core problem the user wants to solve.
- Socratic Guidance (Core)：
- Principle: If the information provided by the user is insufficient to fill in the core parts of the template (such as the vision and core modules),please do not guess or auto-complete。
- Execution: List the missing key information, and throughExample-Driven questioning, inspire the user to think step by step.
- Bad: "What is your core value?"
- Good: "What is the core value of this product? Is it to help users save money (such as a price comparison tool), or to improve efficiency (such as automatic bookkeeping)?"
- Structured Output: Strictly generate the document according to the [Output Template] below.
Output Template
Product Overview
1. Project Vision
Summarize in one sentence: For whom are we providing what core value?
[Generate here]
2. Value Proposition
- User Value: [Generate here]
- Business/Technical Value: [Generate here]
3. Core Modules
Break the system down into key top-level modules (2-4 core modules recommended).
3.1 [Module Name]
- Description: [Briefly describe the functional boundaries of this module]
- Key Features：
- [Feature 1]
- [Feature 2]
3.2 [Module Name]
- ...
4. Target Users & Core Scenarios
4.1 Target Users
- [User Type A]: [Persona description and core needs]
- [User Type B]: [Persona description and core needs]
4.2 Core Scenarios (Key Use Cases)
- Scenario 1: [User A] under [what circumstances], through [what operation], achieved [what goal].
- Scenario 2：...
5. Core Workflows
Describe the 1-2 most core business flows of the system; these determine the complexity of the technical architecture.
[For example: user uploads image -> triggers OCR recognition -> extracts text -> stores in database -> notifies user]
6. Acceptance Criteria
What are the specific markers for the end of the first phase of the project? (Used to prevent scope creep)
- Functional completeness: [For example: core flow works end-to-end, no serious bugs]
- Technical metrics: [For example: page load < 1s, code coverage > 80%]
7. Constraints
Hard non-functional limitations.
- [For example: must be open source, must run offline, development cycle < 2 weeks]
8. Out of Scope
Clearly define what willnotbe done in this phase, to avoid scope creep.
- [For example: multilingual support is not yet supported, mobile app is not yet developed]
Interaction Guidelines
- Maintain a professional tone and rigorous logic.
- Phased output：
- When information is insufficient: output only a list of questions, do not generate a half-finished document.
- When information is sufficient: directly output the generated Markdown document, without including too much introductory text.
- Final delivery: after the document content is confirmed by the user, please save it to
specs/1_产品概述.md。 - Identify boundaries: pay special attention to the user's non-functional constraints (such as cost, time) and project boundaries, as these will directly determine the technology selection.
- Ensure the document structure is clear, to facilitate the subsequent generation of the "tech stack" and "project structure".