---
name: tech-design
description: 通用技术方案撰写技能。根据需求输入（需求分析报告或口头描述）自动生成结构完整的技术方案 Markdown 文档。当用户说"帮我写技术方案"、"出一个技术设计文档"、"写一份 design doc"、"给这个需求出方案"时使用本技能。
title: tech-design
canonical_url: https://skilld.dev/gh/tencent/loopforge/tech-design
last_updated: 2026-11-15T23:15:55.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/general.md](https://skilld.dev/api/skills-raw/tencent/loopforge/tech-design/references/general.md).
>
> If the user asked to install this Skill, run `npx skilld install tencent/loopforge/tech-design`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/tech-design`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/tencent/loopforge/tech-design) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/tech-design`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/tech-design --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/tech-design --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 技术方案撰写技能

## 工作流程

### 第一步：解析需求输入

根据输入类型进行处理：

- **需求分析报告**：读取报告文件，提取需求背景、功能点、约束条件
- **口头描述**：直接理解用户描述，若信息不足以支撑方案撰写，追问以下关键信息：
  - 核心功能是什么？
  - 涉及哪些系统/模块？
  - 有无性能/安全特殊要求？
  - 预计数据量级？

### 第二步：加载方案模板

读取通用技术方案模板：[references/general.md](https://skilld.dev/api/skills-raw/tencent/loopforge/tech-design/references/general.md)

### 第三步：撰写技术方案

按照模板结构生成技术方案，注意：

- 架构图、流程图、时序图统一使用 Mermaid 语法绘制
- 不涉及的章节（如灰度策略、第三方依赖）直接删除，不强行填写
- 若某章节信息不足，标注"待补充"并说明需要哪些信息
- 方案中的估算数据（性能指标、数据量等）需标注来源或假设依据

### 第四步：保存文档

将生成的技术方案保存为 Markdown 文件：

- 若用户已指定输出路径，保存到指定路径
- 若用户未指定路径，询问保存位置
- 文件名建议：`tech-design-[需求名称].md`

## 注意事项

- 方案内容应具体、可落地，避免空泛描述
- 关键技术决策需说明"为什么选这个，为什么不选那个"
- 复杂方案优先用图表表达，文字辅助说明
