---
name: forge
description: "Forge implementation from JIRA tickets using dynamic skill generation. Gathers context into a lazy-loaded skill, then invokes it for execution. Use when given a JIRA ticket URL (format: https://[domain].atlassian.net/browse/[TICKET-ID]) to process end-to-end."
argument-hint: 'JIRA ticket URL (format: https://[domain].atlassian.net/browse/[TICKET-ID]) "(Optional) Additional Context"'
allowed-tools: Read, Bash, ExitPlanMode, Write, Edit
hooks:
  PreToolUse:
    - matcher: "Skill"
      hooks:
        - type: command
          command: "s=\"$CLAUDE_SKILL_DIR/.claude/skills/forge/scripts/log-skill-execution.js\"; [ ! -f \"$s\" ] && s=\"$HOME/.claude/skills/forge/scripts/log-skill-execution.js\"; [ -f \"$s\" ] && node \"$s\""
  PostToolUse:
    - matcher: "Skill"
      hooks:
        - type: command
          command: "s=\"$CLAUDE_SKILL_DIR/.claude/skills/forge/scripts/log-skill-execution.js\"; [ ! -f \"$s\" ] && s=\"$HOME/.claude/skills/forge/scripts/log-skill-execution.js\"; [ -f \"$s\" ] && node \"$s\""
  Stop:
    - hooks:
        - type: command
          command: "s=\"$CLAUDE_SKILL_DIR/.claude/skills/forge/scripts/generate-execution-flow.js\"; [ ! -f \"$s\" ] && s=\"$HOME/.claude/skills/forge/scripts/generate-execution-flow.js\"; [ -f \"$s\" ] && node \"$s\""
          once: true
---

# Forge: JIRA Ticket → Dynamic Skill → Implementation

## Arguments
- `$ARGUMENTS[0]` — JIRA ticket URL (format: `https://[domain].atlassian.net/browse/[TICKET-ID]`)
- `$ARGUMENTS[1]` — Additional context (quoted string, optional)

Orchestrates end-to-end JIRA ticket processing. Phases 1–5 gather context and write output files into a **dynamically created skill** at `~/.claude/skills/{ticket_id}/`. Phase 6 invokes that skill — context files are lazy-loaded on demand.

1. Initialization — create skill directory at `~/.claude/skills/{ticket_id}/`
2. JIRA Analysis (via `Skill("jira-ticket-viewer")`)
2.5. Create Git Branch (named `{TICKET-ID}-{slugified-title}`)
3. Discovery & Scanning (all 3.x run concurrently):
   - 3.1 Domain Discovery (via `Skill("domain-discover")`)
   - 3.2 Resource Scanning (links, Figma designs)
   - 3.3 Page Inspection (conditional, via `Skill("page-inspector")`)
4. Prompt Optimization (via `Skill("meta-prompter")`)
5. Implementation Planning + generate `SKILL.md` for the dynamic skill
6. Execute — invoke `Skill("{ticket_id}-impl")`
7. Verification (includes QA web test)

## Skill Dependencies

The following skills are invoked during orchestration:
- `Skill("jira-ticket-viewer")` — Fetch JIRA ticket details via jira CLI
- `Skill("confluence-page-viewer")` — Read Confluence pages via confluence CLI
- `Skill("figma-reader")` — Read Figma designs (when Figma links present in ticket)
- `Skill("domain-discover")` — Domain knowledge discovery
- `Skill("page-inspector")` — Capture current page layout/styles as baseline (conditional: frontend/UI-affecting changes)
- `Skill("meta-prompter")` — Prompt evaluation and optimization
- `Skill("{ticket_id}-impl")` — Dynamically generated skill for execution (created in Phase 5)
- `Skill("qa-web-test")` — Visual QA testing via Chrome DevTools MCP (conditional: user-visible web changes)

## Execution

Follow [references/phases.md](references/phases.md) for step-by-step phase instructions.

<tags>
   <mode>think</mode>
   <custom>yes</custom>
</tags>