| name | skill-builder |
| scope | universal |
| description | [UDS] Identify repeated processes and build Skills with the right development depth |
| allowed-tools | Read, Glob, Grep, Write, Edit, Bash |
| argument-hint | [process description | 流程描述] |
Process-to-Skill Assistant
Language: English | 繁體中文 | 简体中文
Guides you from "I keep doing this manually" to a properly built Skill,
with the right amount of process along the way.
When to Use
- You've done the same multi-step sequence ≥ 3 times manually
- A teammate asks "how do we do X again?" for the 3rd time
- You built a Skill ad-hoc and want to formalize it
Core Principle
A Skill records process knowledge. Memory records historical facts.
When you notice yourself executing the same steps repeatedly, that's a Skill candidate.
Decision Tree
New Skill needed?
├── Modifying existing Skill?
│ → Delta path: append ## MODIFIED / ## ADDED to existing SKILL.md
│ update version field → done
│
├── Answer these 4 questions (any "yes" → Complex):
│ 1. More than 7 steps?
│ 2. Branching logic between steps (if/else)?
│ 3. Requires knowledge from 3+ separate standards/decisions?
│ 4. Output directly affects sub-project source code?
│
├── All "no" → Simple path
│ → Fill Skill Brief (templates/SKILL-BRIEF-TEMPLATE.md)
│ → Create SKILL.md directly (no XSPEC needed)
│
└── Any "yes" → Complex path
→ Create XSPEC first → run /sdd
→ Return here after XSPEC Approved
Deprecating a Skill?
→ Add to SKILL.md frontmatter:
status: deprecated
deprecated_at: YYYY-MM-DD
deprecated_reason: "..."
superseded_by: "/new-skill" (if applicable)
→ Mark archived in SKILL-CANDIDATES.md