Skill Designer

Problem

When you want to turn a workflow you have already run into a reusable Skill, the hard part is not generation. It is producing a specification with trigger boundaries, validation, and negative constraints, so the model does not misfire, drift, or package a one-off script as a Skill. Skill Designer is for engineers who need a structured way to turn experience into a checkable Skill.

How it works

It routes the request into A task execution, B habit building, or C tool usage, then walks through requirement clarification, workflow design, principle checks, and deliverables:
- Define description, when_to_use, and non-trigger boundaries instead of collecting keywords;
- Keep long docs in references/, scripts in scripts/, and SKILL.md concise;
- Generate REQUIREMENTS.md, SOLUTIONS.md, and a mistake ledger that records failure patterns in an append-only way;
- For habit-building Skills, check action tiers, feedback templates, and adjustment mechanisms.

Boundaries

It fits cases where you already have a validated path and need it standardized as a reusable Skill. It does not invent unvalidated methodology, auto-publish, or guarantee platform scores. If the request is vague, it first narrows trigger conditions and output format, and may start with an MVP.