skill-create-workflow

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Skill Development Workflow

Skill开发工作流

Orchestrate the full lifecycle of creating a skill for the CaldiaWorks marketplace.

This workflow combines general-purpose skills (

ideation

usdm

) with skill-specific tools (

skill-creator

) to guide the user from a rough idea to a published skill.

编排针对CaldiaWorks市场的Skill创建全生命周期。

本工作流结合了通用Skill（

ideation

、

usdm

）与Skill专用工具（

skill-creator

），引导用户从初步想法到发布Skill。

Mandatory Execution Rule

强制执行规则

Each invoked skill defines its own internal steps (e.g., ideation has Steps 1-6, USDM has Steps 1-5, skill-creator has its own workflow). Every internal step of every invoked skill must be executed in order without exception. Do not skip, merge, or silently omit any step — even if the step seems trivial or the answer seems obvious.

If a step requires user input or confirmation, ask. If a step produces output, present it. If a step offers output format choices, ask the user to choose.

Violating this rule degrades the quality of the output and erodes user trust. There is no acceptable reason to skip a step.

每个被调用的Skill都定义了自己的内部步骤（例如，构思步骤有1-6步，USDM有1-5步，skill-creator有其独立工作流）。必须按顺序执行每个被调用Skill的所有内部步骤，不得例外。 即使步骤看似无关紧要或答案显而易见，也不得跳过、合并或省略任何步骤。

如果某步骤需要用户输入或确认，请询问用户；如果某步骤产生输出，请展示给用户；如果某步骤提供输出格式选项，请让用户选择。

违反此规则会降低输出质量并损害用户信任，任何情况下都不得跳过步骤。

Workflow Steps

工作流步骤

Execute these steps in order. Each step produces output that feeds into the next.

If the user already has artifacts from earlier steps (e.g., an idea document or a USDM requirements document), skip the completed steps and start from the appropriate point:

User has an idea document → start at Step 2
User has a USDM requirements document → start at Step 3
User has an implemented skill → start at Step 4

按顺序执行以下步骤，每个步骤的输出将作为下一个步骤的输入。

如果用户已拥有早期步骤的成果（例如，想法文档或USDM需求文档），可跳过已完成的步骤，从合适的节点开始：

用户已有想法文档 → 从步骤2开始
用户已有USDM需求文档 → 从步骤3开始
用户已有已实现的Skill → 从步骤4开始

Step 1: Ideation

步骤1：构思

Invoke the

ideation

skill to explore and refine the skill idea.

Input: User's rough idea or problem description
Output: Idea document at
```
.docs/ideas/YYYY-MM-DD-<topic>.md
```
The idea document captures What, Why, Scope, Stakeholders, and Approaches

Ask the user: "Do you want to proceed to requirements definition, or keep this as an idea draft?"

If the user wants to proceed → continue to Step 2
If the user wants to stop → end the workflow here

调用

ideation

Skill来探索并完善Skill想法。

输入：用户的初步想法或问题描述
输出：想法文档，路径为
```
.docs/ideas/YYYY-MM-DD-<topic>.md
```
想法文档需记录内容：目标、原因、范围、相关人员和实现方案

询问用户：“是否要进入需求定义环节，还是仅保留此想法草稿？”

如果用户选择继续 → 进入步骤2
如果用户选择停止 → 结束本工作流

Step 2: Requirements Definition

步骤2：需求定义

Invoke the

usdm

skill with the idea document as input.

Input: The idea document from Step 1
Output: USDM requirements document at
```
.docs/
```
The requirements document decomposes the idea into Requirement → Reason → Description → Specification hierarchy

Ask the user: "Requirements are ready. Proceed to implementation?"

以想法文档为输入，调用

usdm

Skill。

输入：步骤1生成的想法文档
输出：USDM需求文档，路径为
```
.docs/
```
需求文档将想法分解为“需求→原因→描述→规格”的层级结构

询问用户：“需求已准备完成，是否进入实现环节？”

Step 3: Implementation

步骤3：实现

Invoke the

skill-creator

skill to implement the skill.

Input: The USDM requirements document from Step 2
Follow the skill-creator process: understand → plan → initialize → edit → test → iterate
Output: A complete skill directory under
```
skills/<skill-name>/
```

The skill must include:

```
SKILL.md
```
with proper frontmatter
Any necessary bundled resources (scripts/, references/, assets/)
```
.claude-plugin/plugin.json
```

Implementation is not complete until skill-creator's full cycle (including eval and iteration) has been executed. A draft SKILL.md alone does not constitute a completed implementation. The skill-creator defines test cases, runs them, grades expectations, and iterates until stopping criteria are met. All of these steps must be performed.

调用

skill-creator

Skill来实现Skill。

输入：步骤2生成的USDM需求文档
遵循skill-creator流程：理解→规划→初始化→编辑→测试→迭代
输出：完整的Skill目录，路径为
```
skills/<skill-name>/
```

Skill必须包含：

带有正确前置内容的
```
SKILL.md
```
所有必要的捆绑资源（scripts/、references/、assets/）
```
.claude-plugin/plugin.json
```

只有在执行完skill-creator的完整周期（包括评估和迭代）后，实现环节才算完成。 仅生成

SKILL.md

草稿并不代表实现完成。skill-creator会定义测试用例、运行测试、评估结果并迭代，直到满足停止条件。所有这些步骤都必须执行。

Step 4: Marketplace Registration

步骤4：市场注册

Verify
```
.claude-plugin/plugin.json
```
exists in the skill directory:

json

{
  "name": "<skill-name>",
  "version": "0.1.0",
  "description": "<Short description>",
  "skills": ["."]
}

Add the skill path to both root-level manifests:

.claude-plugin/plugin.json

— Add

"./skills/<skill-name>"

to the

skills

array

.claude-plugin/marketplace.json

— Add

"./skills/<skill-name>"

plugins[0].skills

array

Bump the version in both files. Both must always have the same version number.
Add the skill to
```
README.md
```
:
- Add the
```
npx skills add
```
  install command to the installation section
- Add the skill name and description to the Available Skills table
Report completion to the user with the registered skill path.

在两个市场清单中注册Skill。

验证Skill目录中是否存在
```
.claude-plugin/plugin.json
```
：

json

{
  "name": "<skill-name>",
  "version": "0.1.0",
  "description": "<Short description>",
  "skills": ["."]
}

将Skill路径添加到两个根级清单中：

.claude-plugin/plugin.json

— 将

"./skills/<skill-name>"

添加到

skills

数组

.claude-plugin/marketplace.json

— 将

"./skills/<skill-name>"

添加到

plugins[0].skills

数组

同时更新两个文件的版本号，确保两者版本号始终一致。
将Skill添加到
```
README.md
```
中：
- 在安装部分添加
```
npx skills add
```
  安装命令
- 在“可用Skill”表格中添加Skill名称和描述
向用户报告注册完成，并告知已注册的Skill路径。

Step 5: Version Management

步骤5：版本管理

If this workflow modified any existing skills (not just the new skill), update their versions.

Check
```
git diff
```
for all files changed during this workflow.
For each skill directory under
```
skills/
```
that has modifications, bump the
```
version
```
field in its
```
.claude-plugin/plugin.json
```
.
Do not modify files under
```
.claude/
```
— that directory is managed by the plugin installation system, not by this workflow.

如果本工作流修改了任何现有Skill（不仅是新Skill），请更新它们的版本号。

查看
```
git diff
```
以了解本工作流中修改的所有文件。
对于
```
skills/
```
目录下所有有修改的Skill，更新其
```
.claude-plugin/plugin.json
```
中的
```
version
```
字段。
不要修改
```
.claude/
```
目录下的文件 — 该目录由插件安装系统管理，不由本工作流负责。

Step 6: Final Verification

步骤6：最终验证

Before reporting completion, verify all artifacts are consistent.

Every skill listed in

.claude-plugin/marketplace.json

plugins[0].skills

is also listed in

.claude-plugin/plugin.json

skills

, and vice versa.

Both root manifests have the same version number.
Every skill listed in the manifests exists under
```
skills/<name>/
```
with a
```
SKILL.md
```
and
```
.claude-plugin/plugin.json
```
.
Every skill listed in the manifests has an entry in
```
README.md
```
(install command + table row).
No unintended files were added to
```
.gitignore
```
— check that existing patterns are not duplicated.

在报告完成前，验证所有成果的一致性。

.claude-plugin/marketplace.json

的

plugins[0].skills

中列出的每个Skill，也必须在

.claude-plugin/plugin.json

的

skills

中列出，反之亦然。

两个根级清单的版本号必须一致。
清单中列出的每个Skill都必须存在于
```
skills/<name>/
```
目录下，且包含
```
SKILL.md
```
和
```
.claude-plugin/plugin.json
```
。
清单中列出的每个Skill都必须在
```
README.md
```
中有对应的条目（安装命令+表格行）。
检查
```
.gitignore
```
中是否添加了意外的文件 — 确保现有规则未重复。

Step 7: Branch Cleanup

步骤7：分支清理

After all PRs are merged and the workflow is complete, clean up the working environment.

Switch back to the
```
develop
```
branch and pull the latest changes.
Delete remote feature branches created during this workflow using
```
git push origin --delete <branch>
```
.
Run
```
git fetch --prune
```
to update remote tracking state.
Delete local feature branches created during this workflow whose upstream is gone.
Delete the eval workspace directory if it exists (
```
skills/<skill-name>-workspace/
```
).
Verify the working tree is clean with
```
git status
```
and
```
git branch -a
```
.

所有PR合并完成且工作流结束后，清理工作环境。

切换回
```
develop
```
分支并拉取最新变更。
使用
```
git push origin --delete <branch>
```
删除本工作流中创建的远程特性分支。
运行
```
git fetch --prune
```
更新远程跟踪状态。
删除本工作流中创建的、上游已不存在的本地特性分支。
如果存在评估工作区目录（
```
skills/<skill-name>-workspace/
```
），请将其删除。
使用
```
git status
```
和
```
git branch -a
```
验证工作树是否干净。