spec-workflow by tencentcloudbase/skills
npx skills add https://github.com/tencentcloudbase/skills --skill spec-workflow在需要以下情况时,使用此技能进行结构化开发工作流:
请勿用于:
* 每个阶段必须完成并经用户确认后才能进入下一阶段
* 切勿跳过阶段或在未经用户确认的情况下继续
* 需要澄清时使用 `interactiveDialog` 工具
2. 应用 EARS 需求语法
* 使用 EARS(简易需求语法方法)进行需求描述
* 格式:`While <可选前置条件>, when <可选触发器>, the <系统名称> shall <系统响应>`
3. 需要时参考 UI 设计规则
* 如果需求涉及前端页面,必须严格参考 `ui-design` 技能
* 在需求阶段确定设计风格和配色方案
* 在最终确定需求前与用户确认设计细节
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
4. 更新任务状态
* 在 `tasks.md` 文件中保持任务状态更新
* 任务完成后标记为已完成
* 在保持质量的同时独立高效地工作
重要:你必须遵守这些规则。每个阶段必须经用户确认后才能进入下一阶段。
如果你确定用户的输入是一个新需求,你可以遵循标准软件工程实践独立工作。必要时与用户确认,并可以使用 interactiveDialog 工具收集信息。
每当用户输入一个新需求时,为了规范需求质量和验收标准,你必须首先清楚地理解问题和需求。在进入下一阶段之前,你必须与用户确认。
首先使用 EARS(简易需求语法方法)完成需求设计。如果你确定需求涉及前端页面,你必须严格参考 ui-design 技能。在需求阶段确定设计风格和配色方案。你必须与用户确认需求细节。经过最终确认后,需求即告定稿,然后进入下一阶段。
保存到 specs/spec_name/requirements.md。与用户确认后,进入下一阶段。
参考格式:
# 需求文档
## 简介
需求描述
## 需求
### 需求 1 - 需求名称
**用户故事:** 用户故事内容
#### 验收标准
1. 使用 EARS 语法:While <可选前置条件>, when <可选触发器>, the <系统名称> shall <系统响应>。例如:When "Mute" is selected, the laptop shall suppress all audio output。
2. ...
...
完成需求设计后,基于当前技术架构和上述已确认的需求,设计技术方案。方案应简洁但准确地描述技术架构(例如,架构、技术栈、技术选型、数据库/接口设计、测试策略、安全性)。必要时使用 mermaid 图表。
保存到 specs/spec_name/design.md。你必须与用户明确确认,然后进入下一阶段。
完成技术方案设计后,基于需求文档和技术方案,分解具体任务。你必须与用户明确确认,然后保存到 specs/spec_name/tasks.md。与用户确认后,进入下一阶段并开始正式任务执行。你需要及时更新任务状态。执行时,尽可能独立自主地工作,以确保效率和质量。
任务参考格式:
# 实施计划
- [ ] 1. 任务信息
- 具体要做的事情
- ...
- _需求:相关需求点编号
tasks.md 文件中实时更新任务状态每周安装数
656
代码仓库
GitHub 星标数
38
首次出现
2026年1月22日
安全审计
安装于
opencode583
codex578
gemini-cli572
github-copilot556
cursor546
kimi-cli540
Use this skill for structured development workflow when you need to:
Do NOT use for:
Follow the workflow strictly
interactiveDialog tool when clarification is neededApply EARS requirement syntax
While <optional precondition>, when <optional trigger>, the <system name> shall <system response>Reference UI design rules when needed
ui-design skillUpdate task status
tasks.md fileImportant: You must follow these rules. Each phase must be confirmed by the user before proceeding to the next phase.
If you determine that the user's input is a new requirement, you can work independently following standard software engineering practices. Confirm with user when necessary, and can use interactiveDialog tool to collect information.
Whenever the user inputs a new requirement, to standardize requirement quality and acceptance criteria, you must first understand the problem and requirements clearly. You must confirm with the user before proceeding to the next phase.
First complete the requirements design using EARS (Easy Approach to Requirements Syntax) method. If you determine the requirements involve frontend pages, you must strictly referenceui-design skill. Determine design style and color palette in the requirements phase. You must confirm requirement details with the user. After final confirmation, the requirements are finalized, then proceed to the next phase.
Save to specs/spec_name/requirements.md. After confirming with the user, proceed to the next phase.
Reference format:
# Requirements Document
## Introduction
Requirement description
## Requirements
### Requirement 1 - Requirement Name
**User Story:** User story content
#### Acceptance Criteria
1. Use EARS syntax: While <optional precondition>, when <optional trigger>, the <system name> shall <system response>. For example: When "Mute" is selected, the laptop shall suppress all audio output.
2. ...
...
After completing the requirements design, based on the current technical architecture and the confirmed requirements above, design the technical solution. It should be concise but accurately describe the technical architecture (e.g., architecture, tech stack, technology selection, database/interface design, test strategy, security). Use mermaid diagrams when necessary.
Save to specs/spec_name/design.md. You must confirm with the user clearly, then proceed to the next phase.
After completing the technical solution design, based on the requirements document and technical solution, break down specific tasks. You must confirm with the user clearly, then save to specs/spec_name/tasks.md. After confirming with the user, proceed to the next phase and begin formal task execution. You need to update task status in a timely manner. When executing, work as independently and autonomously as possible to ensure efficiency and quality.
Task reference format:
# Implementation Plan
- [ ] 1. Task Information
- Specific things to do
- ...
- _Requirement: Related requirement point number
tasks.md file in real-timeWeekly Installs
656
Repository
GitHub Stars
38
First Seen
Jan 22, 2026
Security Audits
Gen Agent Trust HubFailSocketPassSnykPass
Installed on
opencode583
codex578
gemini-cli572
github-copilot556
cursor546
kimi-cli540
React 组合模式指南:Vercel 组件架构最佳实践,提升代码可维护性
103,800 周安装