skillify

# Skillify

Extract reusable modules from instruction files into skills. Also amplify terse instructions (e.g., "use Chrome DevTools MCP") into comprehensive skills via web research. The original file is preserved but trimmed down with skill references.

## Core Principles

1. **Keep originals, extract modules, reference skills** - Don't delete files; extract bloated sections into focused skills, then reference them
2. **Amplify terse instructions** - Brief "use X" mentions become comprehensive guidance through research
3. **Project-local skills** - Skills go in `./.claude/skills/`, focused on reducing context rather than cross-project reuse

## Arguments

**TARGET**: `$ARGUMENTS`

- **No arguments**: Process CLAUDE.md and AGENTS.md in project root
- **File path(s)**: Specific files to process (space-separated)

## Edge Case: Skillifying a SKILL.md

When target is itself a SKILL.md file, **decompose into supporting files** within the same directory instead of extracting to separate skills.

**See `references/skill-decomposition-guide.md`** for the complete decomposition workflow.

---

## Standard Workflow

For commands, agents, CLAUDE.md files - follow this 6-step process.

### Step 0: Create Task List

Create all 6 tasks upfront for visibility. **See `references/task-orchestration-patterns.md`** for the pattern.

```
TaskCreate(subject="Analyze target files", activeForm="Analyzing files")
TaskCreate(subject="Plan extraction & amplification", activeForm="Planning")
TaskCreate(subject="Research amplifications", activeForm="Researching")
TaskCreate(subject="Create skills", activeForm="Creating skills")
TaskCreate(subject="Update original files", activeForm="Updating files")
TaskCreate(subject="Generate summary report", activeForm="Generating report")
```

### Step 1: Read and Analyze

1. **Read target file(s)** fully
2. **Identify extractable modules** - self-contained reference material, templates, patterns, verbose sections (>30 lines)
3. **Identify amplification c