Workflow
Step 1: Parse requirement input
Process according to the input type:
- Requirement analysis report: Read the report file, extract requirement background, feature points, and constraints
- Verbal description: Directly understand the user's description; if the information is insufficient to support writing the solution, ask for the following key information:
- What are the core features?
- Which systems/modules are involved?
- Are there any special performance/security requirements?
- What is the expected data scale?
Step 2: Load solution template
Read the general technical solution template:references/general.md
Step 3: Write the technical solution
Generate the technical solution according to the template structure, noting:
- Use Mermaid syntax uniformly for architecture diagrams, flowcharts, and sequence diagrams
- Sections not involved (such as rollout strategy and third-party dependencies) should be deleted directly rather than filled in forcibly
- If a section lacks sufficient information, mark it as "To be supplemented" and explain what information is needed
- Estimated data in the solution (performance metrics, data volume, etc.) must be annotated with their source or basis of assumption
Step 4: Save the document
Save the generated technical solution as a Markdown file:
- If the user has specified an output path, save to the specified path
- If the user has not specified a path, ask for the save location
- Suggested file name:
tech-design-[需求名称].md
Notes
- The solution content should be specific and actionable, avoiding vague descriptions
- Key technical decisions need to explain "why this one was chosen and why that one was not"
- For complex solutions, prefer diagrams for expression, with text as supplementary explanation