plugin-forge

Stage 3 — execute a filled <topic>-plugin-prompt.md to build the actual Claude Code plugin.

Stage 2 — research a service and fill the plugin-builder template into a runnable prompt.

Run the full docs→plugin pipeline (map-docs → build-prompt → build-plugin) from a documentation URL.

Stage 1 — interactively map a documentation site into a complete coverage roadmap.

This skill should be used when the user asks to "run the plugin-prompt", "execute the builder prompt", "create the expert plugin from this prompt", or wants the actual Claude Code plugin built from an already-filled <topic>-plugin-prompt.md (Stage 2 output MUST exist). This is Stage 3 of the plugin-forge pipeline. Precondition: a filled <topic>-plugin-prompt.md is present. If the user only has docs and no filled prompt, use `forge` (full pipeline) or `build-prompt` (Stage 2) instead.

This skill should be used when the user asks to "build the plugin prompt", "fill in the plugin-creator template", "turn these docs into a builder prompt", "research this service for a plugin", or wants a ready-to-run plugin-builder prompt generated from docs (or a doc roadmap) — Stage 2 only, producing a prompt rather than the built plugin. This is Stage 2 of the plugin-forge pipeline. If the user gives a bare docs URL and wants an end-to-end docs→plugin run (not just the builder prompt), use `forge` instead.

This skill should be used when the user asks to "forge a plugin from these docs", "turn this documentation into a Claude Code plugin", "run the full plugin pipeline", "go from docs URL to plugin", or gives a documentation link and wants the entire docs→plugin workflow run end-to-end. Orchestrates the three plugin-forge stages in sequence.

This skill should be used when the user asks to "map the docs", "build a doc roadmap", "crawl this documentation site", "create a coverage map of these docs", or wants an exhaustive inventory/coverage map of a documentation website (overviews, features, guides, examples, cookbooks, API reference, and in-page headers) — Stage 1 only. This is Stage 1 of the plugin-forge pipeline. If the user gives a bare docs URL and wants an end-to-end docs→plugin run (not a roadmap specifically), use `forge` instead.