skill-spec-generator

# Skill Spec Generator

Generate a set of skill specifications that independent skill creators can implement without coordination. Each spec must be self-contained; list-level context explains how specs relate.

## Process

### 1. Analyze Input

Inputs vary. Identify what's provided and what needs discovery:

| Input Type | What to Extract |
|------------|-----------------|
| Domain description | Core workflows, tools, file types, pain points |
| Gap analysis | Existing coverage, missing capabilities, overlap risks |
| Pain points | Repetitive tasks, error-prone steps, knowledge gaps |
| Workflow description | Sequential steps, decision points, variations |
| Existing skills list | Patterns, naming conventions, granularity level |

Ask clarifying questions only for critical ambiguities. Prefer generating specs with stated assumptions over excessive back-and-forth.

### 2. Identify Skill Boundaries

Good skill boundaries:
- **Single responsibility**: One clear purpose, describable in one sentence
- **Natural triggers**: Obvious when to use it (file type, task verb, domain term)
- **Standalone value**: Useful even if other skills don't exist
- **Composable**: Can combine with other skills without overlap

Watch for:
- Skills too broad (should be split)
- Skills too narrow (should be merged or dropped)
- Overlapping triggers (will confuse skill selection)

### 3. Generate Specifications

For each skill, produce a spec block:

```
## Skill: [name]

**Description**: [Triggering description - what it does AND when to use it]

**Rationale**: [Why this skill is needed, what problem it solves]

**Example triggers**:
- "[example user request 1]"
- "[example user request 2]"

**Expected components**:
- scripts/: [what executable code, if any]
- references/: [what documentation, if any]
- assets/: [what templates/files, if any]

**Complexity**: [Low/Medium/High] - [brief justification]

**Dependencies**: [other skills from this list, or "None"]

**Notes for implementer**: [any