skill-forgelisted

# Skill Forge — Dynamic Agent & Skill Creation Create specialized agents and skills on the fly when existing ones don't fit the task. ## When to Forge - The current task requires domain-specific expertise not covered by existing agents/skills - A pattern emerges that will recur (e.g., "we keep doing Stripe integrations") - The user explicitly asks to create a specialized workflow - Post-task review reveals a reusable pattern worth capturing ## Forge Process ### 1. Gap Detection Before starting complex work, check: - `ls ~/.claude/agents/` — what agents exist? - `ls ~/.claude/skills/` — what skills exist? - Does the current task fit an existing agent's description? - If not, what specialty is missing? ### 2. Design the Agent/Skill Determine: - **Name**: Short, descriptive (e.g., `stripe-integrator`, `graphql-designer`) - **Type**: Agent (has tools, model tier, acts autonomously) vs Skill (workflow guide, no tools) - **Scope**: What does it handle? What does it NOT handle? - **Conventions**: What standards / patterns the agent should encode (these go directly in the system prompt — Claude Code does not persist agent state across invocations) ### 2a. Canonical-source lookup (H.6.7) + validation_sources (H.7.0-prep) Before generic internet research, consult the canonical-source registry for tech skills: ```bash # Read the registry once at forge time node ~/.claude/scripts/agent-team/kb-resolver.js cat hets/canonical-skill-sources ``` Look up the skill name in the `### Re