craft-skill-spec

Purpose

Design a new skill spec using CraftKit's current canonical view of good skill-authoring patterns.

This is not a generic skill-creation walkthrough. It is the decision layer that turns a rough skill idea into a concrete, reviewable spec: what the artifact should do, what patterns it should adopt or avoid, how much freedom it should allow, what files it needs, and how it should be evaluated.

Use it when the question is not just "how do I write a skill?" but "what kind of artifact should this become right now?"

The common path is intentionally light: classify the artifact, define its wedge, choose the smallest useful file shape, draft the trigger surface, and name the first eval checks. The radar exists to sharpen those decisions, not to turn every run into research.

Use this when

• a rough skill idea needs a concrete, reviewable spec before writing SKILL.md
• the artifact class is unclear — single skill, skill suite, subagent, or plugin
• an existing skill needs reshaping before a redraft, not a tuning pass
• trigger wording, file shape, or eval-plan decisions need CraftKit's current radar judgment
• the user asks for a "meta-skill" or explicitly wants a skill designed, not written