From yuque-group
Generates structured technical design documents from user requirements using a standard template and saves them to a Yuque group knowledge base for team review. Useful for formalizing features into RFCs.
npx claudepluginhub yuque/yuque-ecosystem --plugin yuque-groupThis skill uses the workspace's default tool permissions.
Help the user write a structured technical design document following a standard template, then save it to the team's Yuque knowledge base for group review.
Generates structured technical design documents from user requirements using a standard template and saves them to group Yuque knowledge bases for team review. Triggers on tech scheme or RFC requests.
Creates detailed technical specifications, requirements documents, design documents, and system architecture specs. Use for feature specs, PRDs, ADRs, RFCs, API designs, and database schemas.
Generates structured RFCs, technical proposals, design docs, architecture docs, and one-pagers for software projects. Covers planning new systems, documenting existing codebases, and small changes.
Share bugs, ideas, or general feedback.
Help the user write a structured technical design document following a standard template, then save it to the team's Yuque knowledge base for group review.
All tools are from the yuque-mcp server:
yuque_search — (Optional) Search for related existing docs for contextyuque_list_books — Find the target group knowledge baseyuque_create_doc — Create the design documentThe full template is in references/template.md. Load it when generating the document.
Gather from the user:
| Field | Required | Description |
|---|---|---|
| 项目/功能名称 | Yes | What is being designed |
| 背景与问题 | Yes | Why this is needed, what problem it solves |
| 目标 | Yes | What success looks like |
| 约束条件 | No | Technical constraints, timeline, budget |
| 已有方案 | No | Any existing approaches or prior art |
| 团队标识 (Group login) | Yes | The team's Yuque group login |
If the user provides a brief description, ask clarifying questions:
If the user hasn't specified a group login, ask: "请告诉我团队的语雀团队标识(group login),我来把技术方案存到团队知识库。"
If relevant, search Yuque for related existing documents:
Tool: yuque_search
Parameters:
query: "<related keywords>"
type: "doc"
This helps:
Load the template from references/template.md and fill in each section based on the user's input and your technical analysis.
Key sections to fill:
Present the draft to the user before saving. Ask:
Tool: yuque_list_books
Parameters:
login: "<group_login>"
type: "group"
Find or ask for the target group repo (often "技术方案" or "设计文档" or "RFC").
Tool: yuque_create_doc
Parameters:
repo_id: "<namespace>" # e.g., "my-team/tech-docs"
title: "[技术方案] <项目名称>"
body: "<formatted design document>"
format: "markdown"
✅ 技术方案已创建(草稿状态)!
📄 **[[技术方案] 项目名称](文档链接)**
📚 已保存到:「团队知识库名称」
### 文档结构
- 背景与目标
- 方案设计(含 X 个核心模块)
- 技术选型对比
- 排期(预计 X 周)
- 风险评估(X 个风险点)
💡 文档为草稿状态,请团队评审后发布。
tech-design skill in the yuque-personal plugin| Situation | Action |
|---|---|
| User provides very vague requirements | Ask 2-3 targeted questions before generating |
yuque_search finds conflicting existing designs | Mention them and ask user how to reconcile |
yuque_create_doc fails | Show error, offer to output the markdown for manual copy |
| User wants to update an existing design doc | Use yuque_search to find it, then suggest creating a v2 or appendix |
| Group login not provided | Ask user for the team's group login |
| Team Token not configured | Inform user that group repos require a team-level Token |