plugin-builder

Implements plugin code from development plans with evidence-based testing and review cycles.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill plugin-builder-lygolang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-builder
Source: https://github.com/LYGOLANG/fufan-cc-flow/tree/main/bundled-plugins/plugin-builder/skills/plugin-builder
Command: npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill plugin-builder-lygolang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a finished plugin specification, design, and development plan into a real, installable plugin package is error-prone: code gets written without verification, evidence is missing, and review findings pile up. This Skill executes the plan task by task, running builds, tests, and probes so every completed task is backed by machine evidence. ## Core Features & Use Cases - Plan-Driven Development: Reads PLUGIN-DEV-PLAN.md and Plugin-Project-State.md, picks the next ready task, implements it, and records evidence before marking it done. - Minimal Round-Trip First: Establishes a working UI-to-Agent-to-UI loop with state persistence before building business features. - Fix Mode: Maps reviewer or checker findings to root causes, routes design or spec issues back upstream, and re-runs the original failing scenario plus affected regressions. - Use Case: After plugin-spec-builder and the design phase produce a PLAN_READY development plan, invoke this Skill to build a Claude Code or MCP plugin end to end, generating source, contracts, tests, evidence, and the final installable package. ## Quick Start Continue developing my plugin from the current task in PLUGIN-DEV-PLAN.md and collect evidence for each completed task.

Frequently Asked Questions about plugin-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a plugin development plan into working code?▼

Provide Plugin-Spec.md, Plugin-Design.md, and a PLUGIN-DEV-PLAN.md with status PLAN_READY. The Skill picks the first ready task, implements it, runs builds and tests, stores evidence, and updates the plan and project state after each task.

What documents are required before plugin development can start?▼

Four files must exist: Plugin-Spec.md, plugin.yaml, Plugin-Design.md, and PLUGIN-DEV-PLAN.md with status PLAN_READY, plus Plugin-Project-State.md in phase PLAN_READY, BUILDING, or CHECKING. Missing or conflicting upstream contracts stop coding and route back to the earlier phase.

How are reviewer findings fixed during plugin development?▼

Each finding is mapped to its upstream ID and failing task, then routed: code defects are fixed directly, plan gaps update the plan first, design errors return to the design skill, and requirement changes return to the spec skill. The original failing scenario and affected regressions must pass again.

Does the plugin builder verify the plugin in the real host application?▼

No. Development-phase verification uses local builds, contract tests, and stdio probes only. Real host end-to-end testing is reserved for a later dedicated step, and the builder never declares BUILD_VALID, HOST_VERIFIED, or SHIPPABLE itself.

What technology stack does the plugin builder use by default?▼

Defaults apply only when the project has no existing stack: TypeScript on Node.js LTS, React with Vite for UI, the MCP SDK for servers, Zod for validation, and Vitest for tests. Existing project conventions and official documentation take priority over these defaults.