Step 3: Map to Existing Tools vs. New Builds
For each automatable process, check if an existing system component already handles it before building something new.
Check Existing System First
| Existing Component | Check |
|---|---|
Slash commands (~/.claude/commands/) | Does a command already do this or something close? |
Agents (~/.claude/agents/) | Is there an agent with the right expertise? |
Scripts (~/.claude/scripts/) | Is there a data collector/processor for this source? |
Skills (~/.claude/skills/) | Is there a multi-step skill that covers this workflow? |
Gap Analysis Table
| Process | Existing Tool | Gap | Build Required |
|---|---|---|---|
| Name | What exists (or “None”) | What’s missing | Agent / Script / Command |
Build Classification
| Type | When to Build | Characteristics |
|---|---|---|
| Script | Deterministic, no reasoning needed | Python, runs on schedule, clear I/O |
| Agent | Needs LLM judgment/creativity | .md persona, spawned by Claude |
| Command | User-triggered workflow | .md file, multi-step instructions |
| Skill | Complex multi-step automation | Directory with tools + workflows |
Last updated on